Re: [Enigmail] Keys disappeared and documentation error

2019-05-08 Thread Olav Seyfarth
Hi Lupa,

in order to avoid trouble due to different key ring files, we recommend
to only install 2.x (current).
In my opinion, there is no need for 1.4 on a system that can run 2.x.
(There may be pecial server/embedded cases where 1.4 is much easier to
handle.)
So, yes, I recommend to uninstall GnuPG 1.4. Not sure if this solves
your issue though.

Olav


smime.p7s
Description: S/MIME Cryptographic Signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-29 Thread Olav Seyfarth
Hi Lupa,

> You are saying that maybe thar reference to a key ended in 142C8283 is
> sele subkey.
I can't tell since I don't have his key. But you can, examining his key
details (using Enigmail key manager or gpg --edit-key0x9DBFEC4B).

> In that case, why am I having an error and how to solve it ?
Don't know, but let's find the cause first, then speculate how you got
there, then solve it.

> Do you read the attachment? I'm having "Invalid recipient, can't trust
> or can't find" error.
No, I overlooked the PNG on your last message, sorry. That message says
that you don't have a key that matches his e-mail address in your
keyring. You should double-check that there IS a VALID key that matches
the EXACT email address.

You mal also check whether you ended up with two GnuPG versions (1.4 and
2.x) - in that case you may have two keyrings that contain partly the
same and partly different keys.

Olav



smime.p7s
Description: S/MIME Cryptographic Signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-28 Thread lupa
Hello Olav,

You are saying that maybe thar reference to a key ended in 142C8283 is
sele subkey. In that case, why am I having an error and how to solve it ?

Do you read the attachment? I'm having "Invalid recipient, can't trust
or can't find" error.

thanks in advance


El 24/4/19 a las 17:26, Olav Seyfarth escribió:
> Hi Lupa,
>
> the LongKeyIDs you see in the log/console are those of the keys the
> message is encrypted to, so in case of sele that's a subkey the KeyID
> is NOT listed in your GPG output snippet. For my key, this would be
>
> sec  rsa3072/A197DF6B6AE1EF56  <-- mainKeyID, that's the one a key
> pair is identified with
> ssb  rsa3072/E71712DF47BBCC40  <-- subKeyID, that's the one Enigmail
> tells to encrypt-to (with -r)
>
> Olav

-- 
Lupa
-
Diaspora*: https://diasp.org/u/lupa18
Mastodon: https://mastodon.social/@lupa18
Telegram: @lupa18
Riot/matrix: @lupa18:matrix.org (no uso)
openPGP ID: 45ED76E0
openPGP key: https://pgp.mit.edu/pks/lookup?op=get&search=0x58A5DBC345ED76E0
-
Declaracion de Confidencialidad

El contenido de este mensaje de correo electrónico y de sus archivos adjuntos 
está(n) dirigido(s) exclusivamente a el(los) destinatario(s) del mismo.  Si 
usted no es el destinatario indicado, o si este mensaje le ha sido enviado por 
error, queda advertido en el sentido de no leer, divulgar, reproducir, 
distribuir, diseminar o utilizar este mensaje en forma alguna.

Statement of Confidentiality

The contents of this e-mail message and its attachments are intended solely for 
the addressee(s) hereof.  If you are not the named addressee, or if this 
message has been addressed to you in error, you are directed not to read, 
disclose, reproduce, distribute, disseminate or otherwise use this e-mail.  




signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-24 Thread Olav Seyfarth
Hi Lupa,

the LongKeyIDs you see in the log/console are those of the keys the
message is encrypted to, so in case of sele that's a subkey the KeyID is
NOT listed in your GPG output snippet. For my key, this would be

sec  rsa3072/A197DF6B6AE1EF56  <-- mainKeyID, that's the one a key pair
is identified with
ssb  rsa3072/E71712DF47BBCC40  <-- subKeyID, that's the one Enigmail
tells to encrypt-to (with -r)

Olav


signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-10 Thread lupa
Hi Olav,

so we don't need that log anymore, because since I recovered private
keys, the error disappeared.

Now I must go ahead with some forensics and other bugtrackers.


thanks!!

El 10/4/19 a las 16:31, Olav Seyfarth escribió:
>
> Hi Lupa,
>
>> I used these tools for several years, working without problems.
>> The only recent change was the TB updade from 60.5.1 to 60.6.1
>> I realize that some files in .gnupg folder had root ownership
> THAT is not normal, and no EM issue AFAIK.
>> I realize that EM was updated to a newer version.
> Yes, that's default TB AddOn AutoUpdate.
> Since EM now is JS only, it doesn't even require a TB restart any longer.
>
>> I created a debug log (12K lines) with lots of personal information.
>> Is there any way to reduce or anonymize that?
> No automated one. But usually, you don't need that much lines.
> End TB, delete the log, start TB, only trigger the error, save log.
>
> But in your case, I'd recommend to fix the file access rights first.
> I expect the error be gone then.
>
>> I think I should open an issue on gnupg. 
> Maybe. Or a Mint/Ubuntu TB package upgrade issue.
>
> Olav
>
-- 
Lupa
-
Diaspora*: https://diasp.org/u/lupa18
Mastodon: https://mastodon.social/@lupa18
Telegram: @lupa18
Riot/matrix: @lupa18:matrix.org (no uso)
openPGP ID: 45ED76E0
openPGP key: https://pgp.mit.edu/pks/lookup?op=get&search=0x58A5DBC345ED76E0
-
Declaracion de Confidencialidad

El contenido de este mensaje de correo electrónico y de sus archivos adjuntos 
está(n) dirigido(s) exclusivamente a el(los) destinatario(s) del mismo.  Si 
usted no es el destinatario indicado, o si este mensaje le ha sido enviado por 
error, queda advertido en el sentido de no leer, divulgar, reproducir, 
distribuir, diseminar o utilizar este mensaje en forma alguna.

Statement of Confidentiality

The contents of this e-mail message and its attachments are intended solely for 
the addressee(s) hereof.  If you are not the named addressee, or if this 
message has been addressed to you in error, you are directed not to read, 
disclose, reproduce, distribute, disseminate or otherwise use this e-mail.  




signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-10 Thread Olav Seyfarth

  
  
Hi Lupa,

I used these tools for several years,
  working without problems. 
  The only recent change was the TB updade from 60.5.1 to 60.6.1
  I realize that some files in .gnupg folder had root ownership
THAT is not normal, and no EM issue AFAIK.
I realize that EM was updated to a newer
  version.

Yes, that's default TB AddOn AutoUpdate.
Since EM now is JS only, it doesn't even require a TB restart any
longer.
 
I created a debug log (12K lines) with lots
  of personal information.
  Is there any way to reduce or anonymize that?
No automated one. But usually, you don't need that much lines.
End TB, delete the log, start TB, only trigger the error, save log.
But in your case, I'd recommend to fix the file access rights
  first.
  I expect the error be gone then.
 
I think I should open an issue on gnupg. 
Maybe. Or a Mint/Ubuntu TB package upgrade issue.
Olav

  




signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-09 Thread lupa
El 9/4/19 a las 17:32, Olav Seyfarth escribió:
>
>
> Hi Lupa,
Hi Olav !
>
> > Is my first message here
> Welcome!
thanks !! and thanks for your time !
>
> According reporting quality: Please first state what the situation was
> before (incl. OS, versions, etc.), what you did, what you expected to
> happen and what did (not) work.

what you did: Write new email

what you expected to happen: the emails goes signed or encrypted as usual

what did (not) work: now I have a warning (attached sent in previous email)

>
> > *A. Empty keyring*
> Yes. But it's not an enigmail but a dirmngr (part of GnuPG) issue.

Yes, I realized there was an gnupg problem after sending that email :-/

> But you DO have a proper backup of your keyring, don't you?!

I had my private keys backed up :D

what the recommended method to doing a complete keyring backup ?

> > Thunderbird version: 60.6.1 (updated from 60.5.1 in 3/29/2019)
> > Enigmail version: 2.0.10, GnuPG version: 2.2.4-1ubuntu1.2
> OK, "1ubuntu1.2" means you're on Ubuntu. Which Ubuntu flavor/version?

Linux Mint 19 (Ubuntu Bionic)

>
> Does "updated" mean that you did have a working TB+EM+GPG config incl.
> private keys that you could sign/decrypt with?
Exactly. I used these great tools for several years, working without
problems.
>
> What DID change? Did you do a system software update (including TB)?
exactly... I checked logs and the only recent change was the TB updade
from 60.5.1 to 60.6.1
>
> Was EM installed manually from our website or as package?
Manually from your website, using a xpi file, several months ago, and I
realize that its updated to a newer version.
> Did you try to create a debug trace yet? Please see
> https://enigmail.net/index.php/en/faq?view=topic&id=15#faqLink_6
> -> click/open "How can I create a debugging log file"

I did it yesterday, and today I did it again and now I have a 12K lines
and 1.5Mb size file with lot of personal information (names and emails).
Is there any way to reduce or anonymize that?

Anyway I think I should open an issue on gnupg.

I also realize that some files in .gnupg folder had root owner and I
think that is no normal. Maybe an update or another program write
something there?  It's scaring!!!

>
> > *B. Documentation error*
> > When I clicked "report a defect" then "Create an execution trace",
> > the link sent me to FAQ's "Usage", but no "execution trace" there.
> No, documentation works as is should (see above). But you need
> JavaScript enabled to "open" the 2nd FAQ link there. It then reads

Ok, I was confused because the difference between "execution trace" and
"debugging log". Now know that are the same.

thanks again!

> --
Lupa


signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error (2nd try since 1st message was garbled)

2019-04-09 Thread Olav Seyfarth

  
  
Hi Lupa,


  Is my first message here

Welcome!
According reporting quality: Please first state what the
situation was
before (incl. OS, versions, etc.), what you did, what you
expected to
happen and what did (not) work.

A. Empty keyring
  1. Today I tried to send an email but got private key
error:
     "Can't find your key in keychain" (something like
this)
  2. So I opened my Enigmail keychain and realized that
it's empty.
     All keys gone included my private key.
  3. Then, I found some dirmngr errors in syslog:
     resolving 'pgp.mit.edu' failed: Connection closed in
DNS
     can't connect to 'pgp.mit.edu': host not found
     error connecting to 'https://pgp.mit.edu:443': Conn.
closed in DNS
     command 'KS_GET' failed: Connection closed in DNS
     error accessing
'http://pgp.mit.edu:11371/pks/lookup?op=get&
   options=mr&search=0x': http
status 502

  It seems that I can't connect to pgp.mit
Yes. But it's not an enigmail but a dirmngr (part of GnuPG)
issue.
It seems that Enigmail deleted the keys?
  
Probably not, Enigmail will only instruct GnuPG to delete
keys if you
explicitely consent to. More likely your keyring was corrupted
by other
means or that you did not set it up correctly in the first
place.
Or Enigmail was set to usi a different path / GPG home.
  
But you DO have a proper backup of your keyring, don't you?!


I did not delete a folder or changed
settings at all.
  
Well, that's what everybody says, right? ;-) Sorry ...

Thunderbird version: 60.6.1 (updated
from 60.5.1 in 3/29/2019)
  Enigmail version: 2.0.10, GnuPG version: 2.2.4-1ubuntu1.2
  
OK, "1ubuntu1.2" means you're on Ubuntu. Which Ubuntu
flavor/version?
Does "updated" mean that you did have a working TB+EM+GPG
config incl.
private keys that you could sign/decrypt with?
What DID change? Did you do a system software update
(including TB)?
Was EM installed manually from our website or as package?
Did you try to create a debug trace yet? Please see
https://enigmail.net/index.php/en/faq?view=topic&id=15#faqLink_6
-> click/open "How can I create a debugging log file"

B. Documentation error
  When I clicked "report a defect" then "Create an
execution trace",
  the link sent me to FAQ's "Usage", but no "execution
trace" there.
No, documentation works as is should (see above). But you
need
_javascript_ enabled to "open" the 2nd FAQ link there. It then
reads:


  In order to support our users, and especially for fixing
  defects, we often require a debug log file. Enigmail
  contains
  a function that creates such a log file if needed.
  
Open the Enigmail Preferences panel (menu Enigmail ->
Preferences)
Activate the checkbox Display Expert Options and close
the dialog
Open the menu Enigmail > Debugging Options > View
Log
Click the Save Log to File ... button to save the log
  

Olav
  




signature.asc
Description: OpenPGP digital signature
___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


Re: [Enigmail] Keys disappeared and documentation error

2019-04-09 Thread Olav Seyfarth

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


Hi Lupa,

> Is my first message here Welcome!

According reporting quality: Please first state what the situation was
before (incl. OS, versions, etc.), what you did, what you expected to
happen and what did (not) work.

> *A. Empty keyring* > 1. Today I tried to send an email but got private key 
> error: > "Can't
find your key in keychain" (something like this) > 2. So I opened my
Enigmail keychain and realized that it's empty. > All keys gone included
my private key. > 3. Then, I found some dirmngr errors in syslog: >
resolving 'pgp.mit.edu' failed: Connection closed in DNS > can't connect
to 'pgp.mit.edu': host not found > error connecting to
'https://pgp.mit.edu:443': Conn. closed in DNS > command 'KS_GET'
failed: Connection closed in DNS > error accessing
'http://pgp.mit.edu:11371/pks/lookup?op=get&; >
options=mr&search=0x': http status 502 > It seems that I
can't connect to pgp.mit Yes. But it's not an enigmail but a dirmngr
(part of GnuPG) issue.

> It seems that Enigmail deleted the keys? Probably not, Enigmail will only 
> instruct GnuPG to delete keys if you
explicitely consent to. More likely your keyring was corrupted by other
means or that you did not set it up correctly in the first place.
Or Enigmail was set to usi a different path / GPG home.

But you DO have a proper backup of your keyring, don't you?!

> I did not delete a folder or changed settings at all. Well, that's what 
> everybody says, right? ;-) Sorry ...

> Thunderbird version: 60.6.1 (updated from 60.5.1 in 3/29/2019) > Enigmail 
> version: 2.0.10, GnuPG version: 2.2.4-1ubuntu1.2 OK,
"1ubuntu1.2" means you're on Ubuntu. Which Ubuntu flavor/version?

Does "updated" mean that you did have a working TB+EM+GPG config incl.
private keys that you could sign/decrypt with?

What DID change? Did you do a system software update (including TB)?

Was EM installed manually from our website or as package?

Did you try to create a debug trace yet? Please see
https://enigmail.net/index.php/en/faq?view=topic&id=15#faqLink_6
- -> click/open "How can I create a debugging log file"

> *B. Documentation error* > When I clicked "report a defect" then "Create an 
> execution trace", >
the link sent me to FAQ's "Usage", but no "execution trace" there. No,
documentation works as is should (see above). But you need
JavaScript enabled to "open" the 2nd FAQ link there. It then reads:

In order to support our users, and especially for fixing defects, we
often require a debug log file. Enigmail contains a function that
creates such a log file if needed.

- - Open the Enigmail Preferences panel (menu Enigmail -> Preferences)
- - Activate the checkbox Display Expert Options and close the dialog
- - Open the menu Enigmail > Debugging Options > View Log.
- - Click the Save Log to File ... button to save the log.

Olav

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEELI5D2uuyOz5mivRZoZffa2rh71YFAlytD0cACgkQoZffa2rh
71aHwgv9HtUUoJktBbZrk1jKnavP8IOrtoBJD9hlTCmUOYuuatqDgysX6EYMErsc
tBgGQ/aGfy6UhU4/VHxkR3lTDc7dzEDDEOOqJiUVvYvUQ9w3sajdl7Doa4YPGUp8
rmHpm+Li/3KIbGkiLohe5LyxTdlVft5fzo+iycp91LlBv0jkLaZHtOH+yo+au34A
66W42hxhUUFlJ8nhbBY3qZjEPjWWiK3flaIDq7NWUB+S32FY70+ge08mvx3l5SbL
DodnvvbLdoATOAr/oKw3YHH/sz8+eXKYrl/LJ0S3cBcX29omz05l49xegsiEavqG
zR656pbOdNtoQC04ummKp2miHws6UGAp0ZwuFn8KC3kXRj8oO7w/2I03+e48f9Hx
/Yx6MKMcDlcvNAPAqhtm3TR3wEXysaFHtc2l3PGhxG9kFpZswKCnmcNLYLct8lwY
zMYrdx1+MtefcPcoOjGVJnUzE0/RyLiiTf3kElPZmOR8qWfy7yRWtGsmpo7PIaiN
AAJkm8bc
=RJav
-END PGP SIGNATURE-

___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net


[Enigmail] Keys disappeared and documentation error

2019-04-08 Thread lupa
Hello folks,

Is my first message here, I will try to do it well. I have 2 issues:

A. Empty Keyring

1. Today I tried to send an email but got private key error: "Can't find
your key in keychain" (something like this)

2. So I opened my Enigmail kaychain and realized that it's empty. All
keys gone included my private key.

3. Then, I found some errors in syslog:
https://bin.disroot.org/?bf03738a8d25d6c9#LguB1cYvBPsSvmkIZKVKIWQC4cKp2/lo+r5/M8f5bLg=

So it seems that can't connect to pgp.mit and then Enigmail deleted the
keys? Maybe is another problem... I'm note sure. 

Something important is that I double checked my behavior, and I did
nothing weird, nor deleted a folder nor changed settings at all.

Software versions:

* Thunderbird version: 60.6.1 (updated from 60.5.1 in 3/29/2019)

* Enigmail version: 2.0.10

* GnuPG version: 2.2.4-1ubuntu1.2

Let me know if I must do another thing or send another log or whatever
is needed.

B. Documentation error

When I clicked "report a defect":
https://www.enigmail.net/index.php/en/support/reporting-defects and then
"Create an execution trace", the link sent me to FAQ's "Usage"
questions, but nothing similar to "execution trace".


thanks in advance,

best,

Lupa



-- 
Lupa
-
Diaspora*: https://diasp.org/u/lupa18
Mastodon: https://mastodon.social/@lupa18
Telegram: @lupa18
Riot/matrix: @lupa18:matrix.org (no uso)
openPGP ID: 45ED76E0
openPGP key: https://pgp.mit.edu/pks/lookup?op=get&search=0x58A5DBC345ED76E0
-
Declaracion de Confidencialidad

El contenido de este mensaje de correo electrónico y de sus archivos adjuntos 
está(n) dirigido(s) exclusivamente a el(los) destinatario(s) del mismo.  Si 
usted no es el destinatario indicado, o si este mensaje le ha sido enviado por 
error, queda advertido en el sentido de no leer, divulgar, reproducir, 
distribuir, diseminar o utilizar este mensaje en forma alguna.

Statement of Confidentiality

The contents of this e-mail message and its attachments are intended solely for 
the addressee(s) hereof.  If you are not the named addressee, or if this 
message has been addressed to you in error, you are directed not to read, 
disclose, reproduce, distribute, disseminate or otherwise use this e-mail.  

___
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net