gt; *Tue Feb 21 15:34:17 CET 2017*
> >
> >- Previous message (by thread): Problems with cert validation via CRL
> ><https://lists.gnupg.org/pipermail/gnupg-users/2017-February/057787.html>
> >- Next message (by thread): Announcing paperbackup.py
Stefan Claas wrote:
> Hi,
>
> while I can't help you with your issue, I like to suggest to take a look
> at Fraunhofer SIT's modern JAB-Code, which compiles nicely under Linux,
> Windows and macOS. It has also the advantage that it can carry much more
> data than QR code. The color barcode withst
On Mon, 2020-09-14 at 08:16 -0400, bexnews--- via Gnupg-users wrote:
> import qrencode
> ImportError: No module named qrencode
You may need something like the python3-qrencode package.
Regards, K.
--
~~~
Karl Auer (ka...@bi
t; apt
> > install qrencode" and seems installed (qrencode version 3.4.4 Copyright (C)
> > 2006-2012 Kentaro Fukuchi), but no change in the ImportError in #2. Is there
> > some other way to "hook" qrencode into paperbackup.py? I tried putting it
> > all
> >
bexnews--- via Gnupg-users wrote:
Hi,
while I can't help you with your issue, I like to suggest to take a look
at Fraunhofer SIT's modern JAB-Code, which compiles nicely under Linux,
Windows and macOS. It has also the advantage that it can carry much more
data than QR code. The color barcode with
hi), but no change in the ImportError in #2. Is there
> some other way to "hook" qrencode into paperbackup.py? I tried putting it all
> into the same folder but it doesn't seem to help.
>
> danke schoen!
> - bexnews
>
> Announcing paperbackup.py to backup keys a
utting it all into the same folder but it doesn't seem to help.
danke schoen!
- bexnews
> Announcing paperbackup.py to backup keys as QR codes on paper *Gerd v.
> Egidy* gerd.von.egidy at intra2net.com
>
> *Tue Feb 21 15:34:17 CET 2017*
>
>- Previous message (by thread): P
Hi Peter,
> So I think the three initial bytes of an MD5 would work well to detect
> typing errors.
I just implemented the line checksums as discussed.
Kind regards,
Gerd
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mail
On 27/02/17 11:50, Gerd v. Egidy wrote:
> echo -n "line content to check" | md5sum | cut -c -6
Yes, that should work just as well in practice, I think. 24 bits of
checksum is slightly weaker than 32, but I don't think it matters.
> But I think a collision at the first 3 bytes is less likely with
Hi Peter,
thank you very much for helping with paperbackup.py and sending your python
code.
> > Ideally it is a tool or combination of tools already deployed widely, like
> > sed and sort I used in paperrestore. This would make the checksums still
> > usable even when the source to paperbackup.p
By the way, don't worry about the license. I just slapped it on there
because you need /something/. (I didn't even look at paperbackup.py's
license, which was dumb, I would have put an MIT license on it otherwise.)
If you're going to use it, I assume you're just going to embed the few
lines of cod
Crap, silly me... why do I always notice these things only after I've
hit send?
On 24/02/17 17:17, Peter Lebbing wrote:
> The following Python:
>
from posixcksum import PosixCkSum
from base64 import b64encode
crc, _ = PosixCkSum.sum_whole(bytearray(b'123456789'))
b64encode(crc
On 23/02/17 13:36, Gerd v. Egidy wrote:
> So I think that this would move the bar for a possible user of paperbackup.py
> higher than I want to.
Yes, it should be easy to use. In fact, I've sometimes heard the
complaint that "paperkey is not easy to install and/or use". That's
really too bad th
On 23/02/17 11:00, Gerd v. Egidy wrote:
> Seems you are trusted by much more people than me ;)
More people trust that that key is mine, they don't trust me as a
person, my actions or my certifications. dkg already answered that bit
:-). These are mostly people I've met at a keysigning party. They
[ not on-topic for this thread, hence the subject change ]
On Thu 2017-02-23 05:00:54 -0500, Gerd v. Egidy wrote:
>> The certificate (aka public key) includes all signatures, all the data
>> on the keyserver. It's data you don't really need to back up since it is
>> public, and it can be huge. My
On Thu 2017-02-23 03:54:12 -0500, Thomas Jarosch wrote:
> In the interest of humanity and the cause of science, I've just tried again
> with a throwaway key :) This time it worked just fine. The "only" thing
> that's
> changed is that I've upgraded from Fedora 22 to Fedora 25 since I last tried.
Il 23/02/2017 11:00, Gerd v. Egidy ha scritto:
> If we are talking centuries, I'd worry about the availability of gnupg as
> much
> as qrcodes. Both are publicly available standards, but I don't know if they
> are still available and understandable by then. I'd recommend going to
> plaintext o
> You might consider using a font designed for OCR rather than the current
> font.
I tried to change to OCR-B or Inconsolata
http://stackoverflow.com/questions/316068/what-is-the-ideal-font-for-ocr
but getting that to work with enscript is not easy, as you have to find and
install afm and pfb i
Hi Daniel,
On Wednesday, 22 February 2017 15:50:21 CET Daniel Kahn Gillmor wrote:
> On Wed 2017-02-22 10:10:51 -0500, Thomas Jarosch wrote:
> > I've tried paperkey with Gnupg 2.1.13 and it had trouble parsing the
> > secret
> > key data. May be the internal packet format changed or needs adaption.
> I'm a little
> surprised that your code is as large as it is, too: using an alternate
> pipeline you might be able to significantly reduce code size.
>
> (a) use Python 3's gpg module to export the secret key
> (b) paperkey --output-type raw --secret-key key.gpg --output key.raw
I want paperbac
Hi Peter,
> The certificate (aka public key) includes all signatures, all the data
> on the keyserver. It's data you don't really need to back up since it is
> public, and it can be huge. My key.asc file is 137,424 bytes following
> your instructions.
Seems you are trusted by much more people tha
On February 21, 2017 9:34:17 AM EST, "Gerd v. Egidy"
wrote:
>Hi,
>
>I'd like to announce a program I wrote to backup GnuPG and SSH keys as
>qrcodes on paper:
>
>paperbackup.py
>https://github.com/intra2net/paperbackup
>
Just wanted to say thanks for sharing your work. As for paperkey, I have a
On 22/02/17 16:10, Thomas Jarosch wrote:
> May be the internal packet format changed or needs adaption.
It is not an internal packet format by the way, it is defined in RFC
4880 (OpenPGP Message Format). And all GnuPG versions output their keys
formatted according to OpenPGP, so the problem you're
On 22/02/17 16:10, Thomas Jarosch wrote:
> When I think about long term storage, I'd rather rely on the full data
> instead of a snippet of the openpgp packets.
I understand that. However, let me point out that any errors parsing
will only occur while *creating* a backup with paperkey. Once it
suc
Hi Peter,
On Wednesday, 22 February 2017 13:56:22 CET Peter Lebbing wrote:
> Oh, as an aside, the advantage of paperkey is that it is
> self-describing.
I've tried paperkey with Gnupg 2.1.13 and it had trouble parsing the secret
key data. May be the internal packet format changed or needs adapt
> Oh, as an aside, the advantage of paperkey is that it is
> self-describing.
I'll chime in with another recommendation for Paperkey. I'm a little
surprised that your code is as large as it is, too: using an alternate
pipeline you might be able to significantly reduce code size.
(a) use Python 3
On 22/02/17 13:56, Peter Lebbing wrote:
> Leaving aside this bug, export-minimal will achieve your goal: it will
> only include the currently valid parts of the key without any
> certifications by other keys.
Whoops! I made a mistake here.
export-minimal does not remove "parts of the key that are
Hello Gerd!
Thank you for sharing your program with the world! I'm sure it will be
useful.
On 22/02/17 09:38, Gerd v. Egidy wrote:
> You are right that this is probably more than strictly neccessary. But if you
> look at my example output on github, a regular public and private key in
> qrcodes
Hi Daniel,
> > gpg2 --armor --export "User Name" >key.asc
> > gpg2 --armor --export-secret-key "User Name" >>key.asc
> > paperbackup.py key.asc
>
> this is a cool idea. however, it seems like you might be backing up
> more than most people would need. For most folks, their OpenPGP
> certificate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Gerd--
On Tue 2017-02-21 09:34:17 -0500, Gerd v. Egidy wrote:
> I'd like to announce a program I wrote to backup GnuPG and SSH keys as
> qrcodes on paper:
>
> paperbackup.py
> https://github.com/intra2net/paperbackup
>
> This is designed as fal
Hi,
I'd like to announce a program I wrote to backup GnuPG and SSH keys as
qrcodes on paper:
paperbackup.py
https://github.com/intra2net/paperbackup
This is designed as fallback if all your regular backups failed to restore or
were lost.
Usage is like this:
gpg2 --armor --export "User Name"
31 matches
Mail list logo
