Hi!
My boss just asked me to make up some ideas about implementations of
X.509 and OpenPGP - which should be introduced in our company later then.
I'm just hacking together a presentation and I'm looking for ideas.
Have you seen a comparison of several implementations for different MUAs
yet?
An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werewolf wrote:
> I have gotten signature faults between messages from Firefox/firegpg and
> Thunderbird/enigmail with clear signing. Guess cause I was using inline
> PGP and not mime.
Try one of the nightly builds of Engimail. The stock Enigmail has
Joe Korn wrote:
> echo "B!g C^t"| gpg --passphrase -fd 0 --decrypt-files "c:\somefile.gpg"
C:\> echo ^bla
bla
C:\> echo ^^bla
^bla
Would that help?
Alex.
signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@g
I didn't investigate too much, but your question for "--no-agent" did
the trick. I used "--use-agent" on the commandline and guess what
happend: A QT-windows in X11 popped up, asking for my passphrase.
It all seems to be related to graphical passphrase-dialogue-foo, cause
when I try to do the same
First: I somehow screwed up my automatic From:-foo... That's why I ended
up in the moderation-queue. I promise to fix it! :)
Werner Koch wrote:
> On Tue, 23 Sep 2008 20:25, [EMAIL PROTECTED] said:
>
>> I migrated from Debian to Fedora Core 8 a while ago. I'm generally using
>> my OpenGPG Smartcar
Hi!
I migrated from Debian to Fedora Core 8 a while ago. I'm generally using
my OpenGPG Smartcard only with Thunderbird/Enigmail, but any now and
then I want to use plain ol' gpg.
However, doesn't work.
Example:
[EMAIL PROTECTED] ~]$ gpg --card-status
gpg: detected reader `SCM SPR 532 (212507092
I just found this on the NCSA-ticker:
http://security.ncsa.uiuc.edu/wiki/NCSA_makes_secure_group_email_services_available
Interesting!
Did anyone try this yet?
Alex.
signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
G
David SMITH wrote:
> On Fri, Aug 08, 2008 at 05:12:49PM +0200, Alexander W. Janssen wrote:
>> Don't tell me there are actually real attacks by recording the sound of
>> the keyboard...?! What does that mean, every key clicks differently?
>
> Sounds like an i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch wrote:
> Further,
> entering the passphrase is subject to side channel atatcks like should
> surfing or recording the sound of the keyboard.
Don't tell me there are actually real attacks by recording the sound of
the keyboard...?! What doe
andrea giovannoni wrote:
> Hi,
Hi,
> I have a problem with my default key.
>
> gpg --default-key 0x12345578 gpg: Go ahead and type your message ...
>
> Can you help me?
What's your exact question? That's the default behaviour if you omit all
other parameters. It automatically starts reading fr
reynt0 wrote:
> On Mon, 21 Jul 2008, kurt c wrote:
> . . .
>> My name is Lawrence, by the way. I created this email account on a whim
>> to test Enigmail, that's why it has this kurt c stuff on it. And now
> . . .
>
> FWIW,
> Do you know that, as I understand things, Google saves
> and records
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John B wrote:
> Throw it away and get one that does things correctly?
Unfortunately many people are stuck with inconvenient solution where
they have no influence in getting something better.
Ha. Me and my Outlook at work. Bargh.
Alex.
-BEGIN
Andrew Berg wrote:
> Alexander W. Janssen wrote:
>> Andrew Berg wrote:
>>> On a side note, is there any reason I didn't see the last message
>>> I sent to the list?
>>
>> You're using Gmail... And probably IMAP? Common problem. Google
>&g
Andrew Berg wrote:
> On a side note, is there any reason I didn't see the last message I sent
> to the list?
You're using Gmail... And probably IMAP? Common problem. Google calls it
a "feature". You need to open the "All Mail" folder instead of the inbox.
Cheers,
Alex.
signature.asc
Descript
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Berg wrote:
> James P. Howard, II wrote:
>> A minor vent: the problem now is the proliferation of mobile devices
>> which make it too difficult to not top post. Users, at this point,
>> are fooled into thinking this is the correct form due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(forwarded this message)
michael graffam schrieb:
> It's easy to solve the problem: all you need is a trusted strcmp() (i.e
> one linked directly w/ main() )..
>
> Before you do anything else, main() checks the environment pointer with
> the trusted s
n't think
it's up to gnupg to solve that problem.
It can't even - except static linking with puts you straight into
dependency-hell.
Alex.
[1] - some simple LD_PRELOAD tests: https://pastebin.ynfonatic.de/152
> On 6/11/08, Alexander W. Janssen <[EMAIL PROTECTED]> wrote:
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
michael graffam schrieb:
> Not a real solution, because if LD_PRELOAD is already set, then the
> shell you type unset into might be overloaded as we'll, already.
Now that's very true; but still my opinion is that if you can't trust
the system on which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
michael graffam schrieb:
> Thoughts?
Run "unset LD_PRELOAD" before running gnupg if you don't trust the system?
It's an inherent feature of the loader. Compiling everthing statically
only works around this inherent feature/problem, however you call i
Faramir wrote:
> I figure it is a good idea to export the private and public keyrings
> before doing any change... I mean, upgrades are good things, but
> sometimes can cause unexpected effects. With a backup, if everything
> goes wrong, you can always reimport the keys.
I learned that the hard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Had some very odd message from the MTA... sorry if this is a repost.
Not sure if my original posting made it to the list.)
Werner Koch schrieb:
> On Sun, 4 May 2008 04:00, [EMAIL PROTECTED] said:
>
>> The smartcard can store 3 1024-bit RSA keys. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch schrieb:
> On Sun, 4 May 2008 04:00, [EMAIL PROTECTED] said:
>
>> The smartcard can store 3 1024-bit RSA keys. It cannot store a 2048-
>> bit key.
>
> That depends on the actual card. GnuPG implements a specification and
> allows all k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Berg wrote:
> Alexander W. Janssen wrote:
>> Or chown() the gnupg.conf to some other user. Not sure if gpg will read
>> the file then though.
> If the user has read access (and gpg is being run with that user's
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Berg wrote:
> Why can't they take away write privileges of gpg.conf (and the gpg
> executables for that matter) from normal users? AFAIK, that would be
> pretty simple (at least on a *nix system).
You'd need to take away write-rights from the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander W. Janssen wrote:
> Enigmail has some known and dodgy errors, especially when it comes to
> verifying signatures. I upgraded to the latest Enigmail nightly build
> which worked for me.
...on a related note you can just export the E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch schrieb:
> [... IDEA/GPL woes ...]
Though I recently had a valid reason; I was in posession of a very old
legacy RSA-keypair which I created quite a long time ago with PGP
2.something.
I just wanted to revoke that key, but in order to cre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Hempen wrote:
> But when I checked on my laptop, where I created the key pairs I get an
> "Error - signature verification failed".
>
> Did anyone ever encounter something like this or has any idea how to fix
> it?
Enigmail has some known and d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Woody schrieb:
> hi,
[...]
> I like to hear what the method you used.
Burned onto CD and printed out in someone else's safe (someone I trust).
> thanks.
Alex.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iQCVAwUBR5iqEBY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Crittenden wrote:
| I fixed it, perhaps not the proper fix but it now works. I made a link
| from /usr/local/lib/libgcc... to /usr/lib/libgcc...
If it's a Linux-system add /usr/local/lib to the file /etc/ld.so.conf
and run the command ldconfig o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I know how to set my Proxy in the appropriate config-files, but is there
also a possibility to set the proxy on the command-line?
Background: I'm using Thunderbird/Enigmail in different
network-environments and it'd be neat if Enigmail could tak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this is a more generic question. I use Thunderbird + Enigmail on several
machines. I never touched any of the advanced features and never got
problems with someone until now.
I've sent an encrypted email - as inline PGP - and my buddy's Mutt
coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remco Post schrieb:
> If this is true, an openpgp smartcard could do 2048 bits, but would cost
> a bit more, I'd be very intrested. Speed is not really an issue, unless
> of course signing or decryption would take more than say 5 seconds.
Well, I hear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I know this is offtopic, but I ask nonetheless, maybe someone has an idea.
The BSI recently announced that it finds RSA/1024 bits not to be
considered secure enough from the 1st of January on[1].
Now I have this really cool RSA-Smartcard (based
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I found the problem. It's not gpg's fault but apparently
Thunderbird/Enigmail truncates attachments every now and then. Haven't
found out under what circumstances yet...
Thanks anyway ;-)
Alex.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch wrote:
> On Thu, 29 Nov 2007 16:24, [EMAIL PROTECTED] said:
>
>> gpg: block_filter 00B36A38: read error (size=9277,a->size=9277)
>> gpg: Problem reading source (16560 bytes remaining)
>> gpg: handle plaintext failed: file read error
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I noticed a strange problem which occurred now three or maybe four
times, all under different circumstances.
I was using my Openpgp Smartcard to encrypt a file (size about 1.4 MB)
to someone else and to my key as well.
When I wanted to acces
On 11/2/07, Werner Koch <[EMAIL PROTECTED]> wrote:
> I am going to celebrate that now with some pints of Füchschen at the
> Cafe Modigliani[1]. Feel free to join.
Why didn't you say that like an hour ago?
Now I'm stuck with my wife, cleaning the house... :-)
> Salam-Shalom,
Next time... Cheers!
On 11/2/07, Robert J. Hansen <[EMAIL PROTECTED]> wrote:
> Alexander W. Janssen wrote:
> >> Factoring prime numbers is most definitely in P.
> >
> > Hold on. Earlier you say "Factoring is known to be in NP". P is much
> > smaller. I'm not familiar
On 11/2/07, Robert J. Hansen <[EMAIL PROTECTED]> wrote:
> A good first-order approximation for the number of primes with a certain
> number of bits is given by the formula:
>
> X = 2**number of bits
> Y = 2**(number of bits - 1)
>
> (X ln Y - Y ln X) / ((X ln Y) * (Y ln X))
Thanks. Though I
On 11/2/07, Robert J. Hansen <[EMAIL PROTECTED]> wrote:
> Alexander W. Janssen wrote:
> > A P-problem? Really?! Factoring primes is a polynomal problem nowadays?
> > Are you SURE about that?
>
> Factoring is known to be in NP. Therefore, it is perfectly fair to s
On 11/2/07, Sven Radde <[EMAIL PROTECTED]> wrote:
> Alexander W. Janssen schrieb:
> >> In fact, some mathematician has proven that factoring is a polynomial
> >> problem, IIRC.
> >
> > A P-problem? Really?! Factoring primes is a polynomal problem nowadays?
&g
On 11/2/07, Sven Radde <[EMAIL PROTECTED]> wrote:
[...]
> As mentioned above, the difficulty does not scale exponentially: The
> 663-bit number took 55 CPU-years on a 2,2GHz Opteron, the 640-bit number
> 30 CPU-years. The actual computations were apparrently carried out by a
> cluster with 80 mach
On 11/2/07, Robert J. Hansen <[EMAIL PROTECTED]> wrote:
> Alexander W. Janssen wrote:
> > How do you come to that figure? A keyspace of 1024 is the double
> > amount of 1023 bit, so I'm curious how you come to that figures.
>
> A keyspace of 1024 bits is double t
On 11/2/07, Robert J. Hansen <[EMAIL PROTECTED]> wrote:
> RSA has never lived up to people's grand expectations. Advances in
> computers and algorithms cause the sorts of RSA keys we can attack to
> creep ever so gradually upwards. It's reasonable to think that within a
> decade an attacker with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just subsribed to the list. I'm using the gpg-smartcard and it just
works for me.
However, I have a couple of maybe really simple questions which
weren't answered by the documentation I've read so far - yet.
1) Once I created my keypair on
45 matches
Mail list logo
