-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12.06.17 20:51, Stefan Claas wrote:
> On 12.06.17 20:18, Ludwig Hügelschäfer wrote:
>> Hi,
>>
>> On 12.06.17 14:52, Stefan Claas wrote:
>>
>>> Hi Ludwig,
>>>
>>> I just checked again. On m
Hi,
On 12.06.17 14:52, Stefan Claas wrote:
> Hi Ludwig,
>
> I just checked again. On my Mac and on my Windows Notebook i get a
> green bar , from a blue "Untrusted" key when i go into Enigmails
> Key Management and set the trust of that key to Ultimate...
Well, ultimate ownertrust is the wrong
Hi Stefan,
On 06.06.17 22:19, Stefan Claas wrote:
> On 06.06.17 20:46, Charlie Jonas wrote:
>> On 2017-06-06 19:12, Stefan Claas wrote:
>>> I tried also with Enigmail under OS X but when checking the
>>> signatures here from the list members i always get the blue
>>> "Untrusted Good Signature".
On 04.06.17 12:39, Stefan Claas wrote:
> On 04.06.17 11:50, Ben McGinnes wrote:
(...)
>> then add "keyid-format 0xLONG" to your gpg.conf file.
>>
> I did that, but Enigmail still shows me the short key-id. :-(
The next major version of Enigmail will show long keyIds everywhere.
Ludwig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30.01.17 18:22, Werner Koch wrote:
> Hope that helps the Sierras
It does :-) Thanks!
Ludwig
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE4WAgb7FA4aaVxJnYOtv6bQCh5v4FAliPiF8ACgkQOtv6bQCh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02.09.16 11:13, Gabriel Philippe wrote:
> Hi,
>
> A friend sends me signed messages wich signature is said correct
> by GnuPG: "good signature from...".
"Good signature" _always_ means it is "good" in the cryptographical
technical sense: Your
On 28.05.16 20:30, Bjoern Kahl wrote:
> Which leaves me with the other option, teach mailvelop /
> openpgp.js to read v2 keys.
>
> Looking at the RFC-4880, it seems V3 and V2 keys share the same
> structure (section 5.5.2, page 41). Openpgp.js does handle V3
> keys, but not V2. Which makes me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21.03.16 20:30, Viktor Dick wrote:
(...)
> I know that Enigmail has the option to save draft messages
> encrypted to oneself, but I am not sure what it does with encrypted
> sent messages.
Default is, that it also encrypts with the senders
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29.01.16 19:32, Bjarni Runar Einarsson wrote:
> (...) Using --hidden-recipient is more efficient and easier to
> implement, but I wonder how this is handled on the receiving end?
> If the user only has one public/private key pair, I assume the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28.07.15 16:46, Ingo Klöcker wrote:
On Monday 27 July 2015 21:05:26 Ludwig Hügelschäfer wrote:
Hi Ingo,
On 27.07.15 16:31, Ingo Klöcker wrote:
(...)
Why should there not be a similar community approach for setting
up a (smaller) network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Ingo,
On 27.07.15 16:31, Ingo Klöcker wrote:
This whole concept of a whitelist of trusted validation servers
included in the email clients sounds a lot like the CA certificate
bundles included in browsers and/or OSes. Who is going to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22.07.15 16:36, flapflap wrote:
Should I be worried by the warning or is this normal behaviour?
You should set ultimate ownertrust on your own key after
(re-)importing. Then it will become valid again.
Ludwig
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18.07.15 16:11, Philip Neukom wrote:
On 17.07.2015 19:36, Robert J. Hansen wrote:
I'd suggest generating a new certificate -- after 20 years you're
due for one. :)
Thank you, Robert. I'll revoke the old one and create a new.
I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.03.15 17:31, Marco Zehe wrote:
Hi Patrick,
Am 01.03.2015 um 15:41 schrieb Patrick Brunschwig
patr...@enigmail.net:
The idea I have in mind is roughly as follows: if you upload a
key to a keyserver, the keyserver would send an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Anthony,
On 22.02.15 01:32, Anthony Papillion wrote:
Thanks for your quick response. It looks like I may have fixed the
problem. Basically, when I use Enigmail for the group line, it
needs it in the form of
group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14.02.15 23:05, Stephan Beck wrote:
Well, it's rather a precautionary measure than an actual security
measure, , reminding me of not trusting the key owner's ability to
handle and verify signatures correctly, if he/she uses a signature
no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15.02.15 16:30, Stephan Beck wrote:
OK, I give you that, strictly speaking, it might not be the same,
but at the moment I had no other measure at hand to remind me of
being careful with that kind of event. And a bad signature event is
not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15.02.15 17:11, Damien Goutte-Gattat wrote:
Error - signature verification failed Public key DE2FFC869AFA5165
needed to verify signature
^^
This is a bug in Enigmail 1.7.2. The sentence should be: Public
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16.02.15 00:07, Robert J. Hansen wrote:
A bad signature _only shows one thing_: The message was
modified along the way from the signing process (at the senders
computer) to the verification process (at your computer).
It doesn't even show
under 2.1.1 (new keybox storage enabled).
pub rsa2048/2D561BB4
created: 2015-01-18 expires: 2015-02-15 usage: SC
trust: ultimate validity: ultimate
sub rsa2048/1675A825
created: 2015-01-18 expires: 2015-02-15 usage: E
[ultimate] (1). Ludwig Hügelschäfer (Test Validity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On 07.12.14 21:36, Lucas Verney wrote:
Le 07/12/2014 21:25, Ludwig Hügelschäfer a écrit :
Hi,
On 07.12.14 21:09, Lucas Verney wrote:
In Arch, with Thunderbird 31.2 and Enigmail 1.7.2, I can't get
Enigmail to use Seahorse instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.12.14 13:13, Dave English wrote:
I have though what looks like the same problem trying to build
1.4.18 from source on Mac OS X 10.10, according to the howto
Version 4.26 (1 July 2014):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.12.14 11:33, gnupgpack wrote:
Hello,
I suggest that you stop deleting the In-reply-to and the
References header.
Ok, i'll give it a try ;)
Now it works. Thank you, this improves reading your posts in context
much easier!
Ludwig
On 12.10.14 12:36, Ben McGinnes wrote:
(...) /usr/include/inttypes.h:235:8: error: unknown type name
'intmax_t' extern intmax_t ^ /usr/include/inttypes.h:236:9: error:
unknown type name 'intmax_t' imaxabs(intmax_t j); ^
/usr/include/inttypes.h:240:2: error: unknown type name 'intmax_t'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03.10.14 19:47, Peter Lebbing wrote:
It is most definitely Staatssicherheit as in die Sicherheit des
Staat(e)s. It's a genetive, just like it's People's Republic of
China and not People Republic of China.
Perfect explanation!
In my mind,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 19.08.14 20:17, Ville Määttä wrote:
Yeah. Ok. Assuming the Mac guys / fork referred to here are
GPGTools / MacGPG2 I can see a couple bigger issues there than just
patching in support for bigger keys.
Ack. Nevertheless, I don't like some of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12.08.14 10:33, da...@gbenet.com wrote:
gpg: WARNING: unsafe enclosing directory permissions on
configuration file `/home/david/.gnupg/gpg.conf'
Check the access permissions of .gnupg directory! It should only be
read and writable for you, no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Philip,
On 05.10.13 18:56, Philip Neukom wrote:
Charly, did you compile with Xcode 5?
I just tried and get an error:
Undefined symbols for architecture x86_64: _iconv, referenced
from:
(...)
Any suggestions to fix would be appreciated.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
you should type
--sign
using a double dash, not
-sign
HTH
Ludwig
On 18.08.13 05:04, Tiwari, Ashish wrote:
Still not working.
Saying Inavlid OPtion -sign.
Regards, Ashish Tiwari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On 25.01.13 12:16, Jochen Wuttke wrote:
I found this question asked as far back as 2010 on various forums
an user groups, but I could never find an answer to what causes
this and how to resolve it. Any hints?
You may want to look into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On 20.12.12 21:20, Werner Koch wrote:
Hello!
15 years after the first release we are now pleased to announce
the availability of a new stable GnuPG-1 release: Version 1.4.13.
Thanks!
I'm having linker errors on Mac OS 10.8.2 regarding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On 23.12.12 15:01, Ludwig Hgelsch￤fer wrote:
Undefined symbols for architecture x86_64: _iconv (...)
Temporarily moving /opt out of the way did solve the issue. Not sure
what gpg configure script found there which was not usable as
On 23.11.12 11:20, Mathias Koerber wrote:
I am using GNUPG Keychain Access on Mountain Lion
and am trying to sign keys.
The popup offers my available private keys in the dropdown only by the
email address/comment text,
but since I have several keys with the same email address, it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Laurent Jumet wrote on 25.08.12 07:35:
Hello Faramir !
On your message below, my GPG gives this warning:
=== Begin Windows Clipboard === gpg: armor: BEGIN PGP SIGNED
MESSAGE gpg: armor header: Hash: SHA256 :packet 63: length 11 - gpg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jerry wrote on 28.10.11 16:36:
On Fri, 28 Oct 2011 14:07:53 +0100 (BST) Phil Brooke articulated:
Nothing relating to encrypted data, but I've seen an MS Exchange
system rewrite signed emails (both PGP/MIME and S/MIME) with the
obvious effect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Robert,
Robert J. Hansen wrote on 24.07.11 23:57:
I'm looking into picking up an OpenPGP smartcard and reader for an OS
X system. The card itself can be picked up from KernelConcepts, but
there seem to be an awful lot of different readers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Heinz Diehl wrote on 11.12.10 09:17:
On 10.12.2010, David Shaw wrote:
Here's some analysis of Skein: http://eprint.iacr.org/2010/623
I can only see 10 pages full of statements without any discussion or
proof, which doesn't even meet the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
David Shaw wrote on 27.09.10 15:57:
Dreadfully is a difficult thing to enumerate anyway. For me, FWIW, it
would be over 1-2 seconds.
Ack. 1.5 seconds is about the limit where a good GUI should issue a
reaction. This is where the human mind is
wegwe...@gmx.de wrote on 08.08.10 18:47:
Just a repetition of my question, in a different way:
Does anybody out there know of any script to brute force a
list of passphrases?
nasty. http://www.vanheusden.com/nasty/
Ludwig
___
Gnupg-users mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
His Steveness wrote on 18.06.10 20:40:
for a Test i installed GPG on MacOsX 5.8,
so far so good, works fine, thank you Guys btw. for that nice Work.
But now i hang there and im not able to uninstall the hole thing.
Can someone tell me a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jason French wrote on 05.01.10 21:45:
Despite having near identical configurations between my work and home
iMacs, I've noticed that at home it's not unusual to see 15 to 30
instances of gpg-agent processes open. I've been unable to remedy the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Sean Wilson wrote on 11.10.09 15:37:
Why is it when I sign an email and someone replies to it I sometimes get
the following error:
Part of the message signed; click on 'Details' button for more information
in the details it says:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thomas Bohn wrote on 21.06.2009 18:08 Uhr:
On Jun 21, 2009, at 7:28 AM, Joel C. Salomon wrote:
On some messages (e.g., this recent one from Thomas Bohn:
ae944322-4d68-40ba-b501-6589512b8...@bohnomat.de) I get the message,
“Error - signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thomas Bohn wrote on 21.06.2009 19:33 Uhr:
On Jun 21, 2009, at 6:31 PM, Ludwig Hügelschäfer wrote:
This one provides a good signature here. Maybe you should turn off
format=flowed. Don't know how to do that in Apple Mail, though.
My last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Allen Schultz wrote on 29.04.2009 6:49 Uhr:
(...) If I take my current subkey and edit it and
try to upload the same subkey with the new expiration, will the
server accept an expiration after one is posted for no
expiration?
Yes. One can even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ingo Klöcker wrote on 25.04.2009 23:50 Uhr:
How does Thunderbird/Enigmail handle bcc'd recipients? Does it create
several differently encrypted copies of the message in case of bcc'd
recipients, i.e. one copy of the message encrypted with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
David Shaw wrote on 26.04.2009 18:51 Uhr:
I'm not sure if Enigmail has sufficient control here (due to the
Thunderbird restrictions),
Yes, Enigmail is aware of BCC recipients (see my response to Ingo)
but if possible, it might be wise to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Joel Rees wrote on 07.02.2009 9:35 Uhr:
Anybody got any idea why my non-root admin user's ~/.gnupg directory is
or should be owned by root?
No idea. This is what I have:
drwx-- 85 luddwich staff 2890 7 Feb 12:27 .gnupg
This is on
Robert J. Hansen wrote on 23.09.2008 11:50 Uhr:
Werner Koch wrote:
No, it was not Robert who flooded us with mails.
Over the last day, I have received a large number of emails related to
this. Some of them were nice. Some of them were not.
It strikes me that people dealing with such an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Lawrence Chin wrote on 30.08.2008 6:23 Uhr:
Hi everyone.
I've been confused about one thing. Several days ago when I typed in the
url http://pool.sks-keyservers.net into my browser, this website called
www.kim-minh.com kept popping up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ludwig Hügelschäfer wrote on 09.08.2008 13:14 Uhr:
Hello,
the last weeks, when importing public keys I sometimes get:
Öffentlicher Schlüssel %s ist %lu Sekunden jünger als die Unterschrift
in english:
public key %s is %lu second newer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
the last weeks, when importing public keys I sometimes get:
Öffentlicher Schlüssel %s ist %lu Sekunden jünger als die Unterschrift
in english:
public key %s is %lu second newer than the signature
The indicated time interval is very
Robert J. Hansen wrote on 26.04.2008 9:20 Uhr:
(...)
I'd like to see GPG remain the name for only 1.4.
GnuPG 2.x introduces a lot of new crypto support that is not related to
OpenPGP. The original metonymy is no longer appropriate.
Call it GnuPS, for the GNU Privacy Suite. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[EMAIL PROTECTED] wrote on 02.04.2008 20:47 Uhr:
Hi,
I can see that 1.4.9 binaries are available at
ftp://ftp.gnupg.org/gcrypt/binary/
But it looks like 1.4.8 is at http://www.gnupg.org/download/
I have tended to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Robert D. wrote on 17.02.2008 15:33 Uhr:
I was reading traffic from Daigle, on PGP-Basics and noticed a lack of
ability to verify his signed email. In fact, I thought I'd already had his
imported and verified.
The GPG window pop-up was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
David Shaw wrote on 07.07.2007 1:37 Uhr:
On Fri, Jul 06, 2007 at 11:12:53PM +0200, Ludwig Hügelschäfer wrote:
Hi,
did sombody succeed in cross compiling gnupg 1.4-series on a PPC-Mac for
an Intel Mac? (both run Mac OS X 10.4.10)?
If yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
did sombody succeed in cross compiling gnupg 1.4-series on a PPC-Mac for
an Intel Mac? (both run Mac OS X 10.4.10)?
If yes, what would I have to consider? Any specific configure-switches?
TIA
Ludwig
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Charly Avital wrote on 14.04.2007 15:18 Uhr:
I can't qualify whether it works or not, nor can I qualify whether the
key ID is incorrect.
GnuPG recognizes 17CACAE3 (in both processors) as the key ID.
Perhaps I may help here:
Using gnupg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
(resent message after the original didn't make it through yet)
Charly Avital wrote on 14.04.2007 15:18 Uhr:
I can't qualify whether it works or not, nor can I qualify whether the
key ID is incorrect.
GnuPG recognizes 17CACAE3 (in both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi victor,
Victor Escobar wrote on 08.12.2006 23:15 Uhr:
Hi all,
I get this error when trying to do a make for gnupg-2.0.1:
/usr/bin/ld: Undefined symbols:
_gpg_error_from_syserror
collect2: ld returned 1 exit status
make[2]: *** [kbxutil]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Malte Gell wrote on 08.12.2006 14:19 Uhr:
Hm, GnuPG 1.4.5 (unpatched)/KMail 1.8.2 reports invalid signed
message... Maybe my gpg.conf is messed or is this due to changes in
gpg
1.4.5? Thanx.
Enigmail didn't even indicate a signed message
-BEGIN PGP MESSAGE-
Charset: ISO-8859-1
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
hIwDjwsYiWKxLx0BBAC83AgzLgfvAsUpd4m+YpHxRLS6j9jkpSs/rzhDHk4Au3uD
vEylbC9FmEOpWyWvAy5T27dJANAy9dCsz79YlHSImNKFYUJ071bTQd4gLH2bINFy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
itsec.info wrote on 21.10.2006 13:54 Uhr:
Hi
I have encrypted a large file (280MB) with gpg v1.4.2 on suse 10.0.
By decrypting the file I get the following error message:
gpg: Problem reading source (10429120 bytes remaining)
gpg: handle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bo Berglund wrote on 19.08.2006 11:01 Uhr:
I found one strange glitch though, old emails containing Swedish
characters decrypt to cleartext but are missing the Swedish chars. So
the words look really strange when there are supposed to be one of
Hi together,
I'm trying to compile gpg 1.4.4 on ubuntu-Linux 5.1
running ./configure produces:
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
and checking config.log yields:
configure:2881: gcc
Hi,
Graham schrieb:
Just a thought. Have you installed build-essential?
(...)
But if you want to compile from scratch you will still have to install
build-essential
Well, that did the job for now, at least make is running right now.
Thanksalot!
Ludwig, going to look into the other
Hi,
On 09.06.2006 6:18 Uhr, John W. Moore III wrote:
Word of Caution: If you have any Files encrypted using the Old/Original
Key; Decrypt them first.
Generally: Decryption works fine even with a revoked key. However, if
there's only the slightest possibility that the private key is not
Hi,
On 02.05.2006 18:15 Uhr, Alphax wrote:
How does one get keys from a keyserver when only the v3 fingerprint is
known? I recovered the fingerprints from a trustdb (they had
appended), but I can't work out how to get them off a keyserver...
The last 4 bytes of the fingerprint are
Hi,
On 02.05.2006 20:11 Uhr, David Shaw wrote:
On Tue, May 02, 2006 at 07:44:53PM +0200, Ludwig Hügelschäfer wrote:
The last 4 bytes of the fingerprint are identical to the key ID for V3 keys.
No, they are not. That's V4 keys.
I always mix V3 and V4 up... Sorry.
Ludwig
Hi Julia,
On 17.04.2006 19:25 Uhr, Julia Dashkevich wrote:
Hi,
I have just installed GnuPG to use it with Enigmail
extension for Thunderbird 1.5.
Having gone through the setup and key generation, it
was necessary to make my public key available on the
web keyserver. Is it true that if i
Hi,
On 07.02.2006 20:05 Uhr, Oskar L. wrote:
This is of course only true if the attacker knows it is exactly 15
characters long. If not, then it should be calculated like this: 95^1 +
95^2 + 95^3 + ... + 95^15.
Right, this gives exactly 95^16 - 1. This is not a dramatic improvement
compared
On 22.12.2005 10:35 Uhr, Johan Wevers wrote:
Christoph Anton Mitterer wrote:
- And even from a cryptographic point of view this wouldn't make sense
(as far as I know), as currently hashfunctions are the weak point of the
whole system.
That depends on what you consider important. Hash
Hi Holger,
On 21.12.2005 12:18 Uhr, Holger Schuettel wrote:
Hi
I've any questions. How can i generate a keypair with size more than
4096 bits? I've a RSA key from my friend in my keyring with 16384 bits.
How is that possible? I've to try it with gnupg to generate a key over
4096 bits and
Hi,
On 22.12.2005 17:06 Uhr, Atom Smasher wrote:
On Thu, 22 Dec 2005, Ludwig Hügelschäfer wrote:
That's true. Even considering a brute force attack, 1025 bits is in
average only sqrt(2) better as 1024 bits.
===
so, does that mean that a 2048 bit asymmetric key is (only
74 matches
Mail list logo
