zbar

That's the repo Trail of Bits was working with; the PR they ended up submitting is at https://github.com/mchehab/zbar/pull/294.

It appears to have been forked: https://github.com/mchehab/zbar

Mauro is really nice. I worked briefly with him when I contributed a patch for the ZBar barcode reader. It was the best experience I had contributing to free and open source software. I'm really thankful for his work. https://github.com/mchehab/zbar/pull/64

I implemented ISBN-13 support in þe Olden Days, and Bookland always struck me as a neat solution to an annoying problem. The whole evolution is quite elegant from SBNs right through to ISBN-13. SBNs are upgradable to ISBN-10(even maintaining their check digit), and those SBNs were then upgradeable to ISBN-13 via Bookland(this time with a check digit change). However, I also remember being annoyed at the transition. Prior to ISBN-13 checksums were a little more robust at simple transposition erorrs, which from my experience is by far the most common error on manual input. Presumably the rationale is that people wouldn't manually input EANs, and re-thinking it now I agree. In 2007 I had to rely on a hand to hold the book and hand to whack at the numpad, whereas now I use my phone and zbar¹ to scan a barcode. I suspect I even spent some

For the reverse, see zbar (https://github.com/mchehab/zbar) [edit] Updated link

Some sites only display the QR code. For those I found ZBar Barcode Tools helpful for converting an image/screenshot to alphanumeric seed: https://github.com/mchehab/zbar

Video games in QR codes? That's interesting. Do you have the link to the video? Is it this one? https://youtu.be/ExwqNreocpg https://github.com/mchehab/zbar/commit/5bc323849569a629aa0d1... If so, then the patch he submitted builds upon my work! He fixed a line feed conversion bug that was present in Windows. I use Linux so I did not experience this issue. I remember seeing that patch get merged but I didn't know about the whole video game context. This is amazing. I wrote the patch because I was trying to print a 4096 bit RSA secret key as a QR code. Awesome to see it getting used for something even more awesome. Here are the links to my contributions and related pages: https://github.com/mchehab/zbar/pull/64 https://github.com/mchehab/zbar/issues/55 https://github.com/mchehab/zbar/issues/82 https://bugs.debian.org/cgi-bin/bugreport.cgi?b

hot tip: zbarimg You can store the TOTP seeds in more compact form by converting QR code screenshots to alphanumeric using zbar barcode tools. In my experience it has difficulty parsing some QR codes created using CSS due to tiny borders between blocks. Those can be fixed by applying a small gaussian blur followed by sharpening (use imagemagick for maximum automation) to fill out the borders. Edit: packages available in Ubuntu (zbar-tools) & Fedora (zbar), source code at https://github.com/mchehab/zbar

> Every time you force-push, GitHub keeps and provides direct links to the old commit, the new commit and the diff between the two commits. Not in my experience. Here's one of my pull requests: https://github.com/mchehab/zbar/pull/64 The maintainer reviewed some of the changes and I revised my commits as a result. The review is correctly marked as outdated. Clicking on the file name tells me the commit cannot be found. > We went looking everywhere, but couldn’t find those commits. > Sometimes commits can disappear after a force-push. Head back to the latest changes here.

Are you using 8 bit encoding? An alphanumeric mode QR code containing base 64 encoded data provides less capacity. In binary mode even a 4096 bit RSA secret key fits while ECC keys produce smaller codes. The qrencode tool has an 8 bit mode but not all decoders can handle binary data. For example, my phone shows me mangled results and I can't redirect them to a file. Like structured append, it doesn't seem to have much support. I've sent patches to ZBar improving this: https://github.com/mchehab/zbar/pull/64 Hopefully it will make QR codes more useful for storing keys and other small files.

Hardware tokens usually have three slots for keys. That's enough for a full set of signing, encryption and authentication keys. It is not wise to keep the primary certification key there, though. Hardware tokens can fail or be lost or stolen. Subkeys are expendable but the primary key is important enough for special treatment. The best way to keep it offline is to make a paper backup with the paperkey tool and store it in a safe: http://www.jabberwocky.com/software/paperkey/ In addition to this, it's a good idea to QR encode the key. QR codes are quickly and easily restored with a laptop camera and they support even 4096 bit RSA keys. The zbarcam program can be used for this purpose but current versions have binary data decoding problems and aren't easy to interface with. I sent some patches to that fix these problems but they haven't bee