On Thu, 3 Jan 2013 23:42:07 -0500
David Shaw ds...@jabberwocky.com wrote:
Paperkey 1.3 is released. This adds ECC key support (both ECDH and
ECDSA) as well as a few more minor tweaks.
Source and Win32 binaries are available at:
http://www.jabberwocky.com/software/paperkey/
Curious piece
Thank you all!
So, a bare email is also legally binding, but it can be hard to proove who
sent it. Same for hellosign.com, it can be hard to proove who really signed
a document there, and it was that fact that confused me, I made legally
binding and proove who signed the same thing.
/Morten
On
Hi,
This is an important issue for me. I would really appreciate, if any one
can help.
Server 1:
I have a server with Red Hat Enterprise Linux AS release 4 (Nahant Update
5) and having gnupg version 1.2.6.
When I am trying to import a key, I am getting below problem and the key is
not getting
On 1/3/2013 2:37 PM, Anilkumar Padmaraju wrote:
This is an important issue for me. I would really appreciate, if any
one can help.
The fix is easy: upgrade GnuPG.
Version 1.2.6 is old, really old. The certificate you're trying to
import uses an algorithm (DSA2) which is relatively new.
I don't know, but I must say that I'm wary of dealing with unknown
people who are collecting signature samples from all over Europe,
offering a service which seems to accomplish very little and making
disputed claims about its legal effect.
--
Mark H. Wood, Lead System Programmer
On Jan 3, 2013, at 2:37 PM, Anilkumar Padmaraju apadmar...@prounlimited.com
wrote:
Hi,
This is an important issue for me. I would really appreciate, if any one can
help.
Server 1:
I have a server with Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
and having gnupg version
On 04-01-2013 5:42, David Shaw wrote:
Paperkey 1.3 is released.
You might want to update the website, it reads a bit outdated.
CD/DVD-ROMs are going the way of the floppy disc; flash memory is much
more reliable than either. Future support of USB ports or memory card
readers seems the biggest
Somebody claiming to be David Shaw wrote:
On Jan 3, 2013, at 9:53 PM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
tell gpg or gpg2 to produce new packet length headers for output?
No. GPG automatically uses the old packet headers for those packets that
can be described that way
Hi,
I'm playing a bit with a fsfe card and trying to find a way to use smartcard
for xscreensaver I've stumbled on poldi references, but the sources seems
untouched since long time.
before starting to work on a updated ebuild (I'm on gentoo installation), is
poldi still alive or do we have
On Fri, 4 Jan 2013 15:27, joh...@vulcan.xs4all.nl said:
CD/DVD-ROMs are going the way of the floppy disc; flash memory is much
more reliable than either. Future support of USB ports or memory card
FWIW: Some time ago I copied a bunch of ~25 years old 5.25 floppies to a
disk. I had only
On Jan 4, 2013, at 9:39 AM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
Somebody claiming to be David Shaw wrote:
On Jan 3, 2013, at 9:53 PM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
tell gpg or gpg2 to produce new packet length headers for output?
No. GPG
You may want to check out my blog post about key backup[1]. In it I
mention two bar-code style backup solutions:
* PaperBack [2]
* Twibright Optar [3]
I also investigated QR codes and other 2D bar codes.. however they did
not seem to scale well to large amounts of data...
I found that
Somebody claiming to be David Shaw wrote:
On Jan 4, 2013, at 9:39 AM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
Somebody claiming to be David Shaw wrote:
On Jan 3, 2013, at 9:53 PM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
tell gpg or gpg2 to produce new packet length
On Jan 4, 2013, at 4:01 AM, Branko Majic bra...@majic.rs wrote:
On Thu, 3 Jan 2013 23:42:07 -0500
David Shaw ds...@jabberwocky.com wrote:
Paperkey 1.3 is released. This adds ECC key support (both ECDH and
ECDSA) as well as a few more minor tweaks.
Source and Win32 binaries are available
My scanner is broken (lamp problem) and the multifunction printer hasn't
arrived yet ;-( so I can't test this myself.
Has anyone tested Paperkey by scanning it in, having the OCR recognize it
without error, and then successfully import it into a keyring ?
If so, what is the recommended font
On 01/04/2013 06:27 AM, Johan Wevers wrote:
On 04-01-2013 5:42, David Shaw wrote:
Paperkey 1.3 is released.
You might want to update the website, it reads a bit outdated.
CD/DVD-ROMs are going the way of the floppy disc; flash memory is much
more reliable than either. Future support of
On Jan 4, 2013, at 9:27 AM, Johan Wevers joh...@vulcan.xs4all.nl wrote:
On 04-01-2013 5:42, David Shaw wrote:
Paperkey 1.3 is released.
You might want to update the website, it reads a bit outdated.
CD/DVD-ROMs are going the way of the floppy disc; flash memory is much
more reliable than
Thank you very much, David.
Our other server is having 1.4.5 and to be consistent want to go from 1.2.6
to 1.4.5.
Can I go ahead and update gnupg from 1.2.6 to 1.4.5 on Red Hat Enterprise
Linux AS release 4 (Nahant Update 5)? Is 1.4.5 compatible with this Linux
version? I did not find any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am I the only having trouble both the key for this message and the one
with the binaries? My installation tells me it is not Key ID:
0x99242560 but key 0xA1BC4FA4 which is not found on any server that I use.
David Shaw made the following
On Jan 4, 2013, at 12:16 PM, I.V. Frost ivfrost2-m...@yahoo.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am I the only having trouble both the key for this message and the one with
the binaries? My installation tells me it is not Key ID: 0x99242560 but key
0xA1BC4FA4
On Fri, 4 Jan 2013 17:34, singpol...@singpolyma.net said:
headers. Such implementations' ouput can be read by gpg, but there's
currently no way to convince gpg to talk to them :)
I just checked the RFC and it says:
If interoperability [with PGP 2] is not an issue, the new packet
On Fri, 4 Jan 2013 18:34, apadmar...@prounlimited.com said:
Can I go ahead and update gnupg from 1.2.6 to 1.4.5 on Red Hat Enterprise
Linux AS release 4 (Nahant Update 5)? Is 1.4.5 compatible with this Linux
version? I did not find any information regarding this compatibility.
GnuPG is
Thank you, David and Werner.
This is first time I am upgrading gnupg. Are there any steps or document
to download source, compile, and upgrade? I did some search in google, but
could not find detailed one.
After upgrading do I have to do gpg --gen-key or it is only needed when we
install for
On Jan 4, 2013, at 12:34 PM, Anilkumar Padmaraju apadmar...@prounlimited.com
wrote:
Thank you very much, David.
Our other server is having 1.4.5 and to be consistent want to go from 1.2.6
to 1.4.5.
Can I go ahead and update gnupg from 1.2.6 to 1.4.5 on Red Hat Enterprise
Linux AS
The manpage for gpg sez:
Secret keys are integrity protected by using a SHA-1 checksum. This
method is part of the upcoming enhanced OpenPGP specification but GnuPG
already uses it as a countermeasure against certain attacks. Old
applications don't under‐ stand this new format, so
On Jan 4, 2013, at 4:37 PM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
The manpage for gpg sez:
Secret keys are integrity protected by using a SHA-1 checksum. This
method is part of the upcoming enhanced OpenPGP specification but GnuPG
already uses it as a countermeasure
Somebody claiming to be David Shaw wrote:
On Jan 4, 2013, at 4:37 PM, Stephen Paul Weber singpol...@singpolyma.net
wrote:
Does anyone know what the actual security risk is? Using a weaker
checksum obviously makes it easier to forge data, but in this case the
data being forged is just the
I am using http://www.faqs.org/docs/securing/chap19sec152.html to do the
upgrade. Please let me know, if I have to do any additional steps.
Since I am already using gpg on this server, do I have to do gpg
--gen-key after the upgrade?
Thank you,
Anil.
On Fri, Jan 4, 2013 at 1:09 PM, Anilkumar
On Jan 4, 2013, at 1:06 PM, ved...@nym.hush.com wrote:
My scanner is broken (lamp problem) and the multifunction printer hasn't
arrived yet ;-( so I can't test this myself.
Has anyone tested Paperkey by scanning it in, having the OCR recognize it
without error, and then successfully
On 1/4/2013 7:17 PM, David Shaw wrote:
I've done this, with regular old Courier.
My experiences are similar. One additional thing: the larger the font
the easier it is for OCR to recognize it (up to a point: I doubt there's
much difference between 48- and 72-point recognition). So try using
30 matches
Mail list logo
