On Wed, Aug 15, 2018 at 12:13 PM, Peter Lebbing
wrote:
> Here's the catch: unless you have an on-disk copy of your private
> encryption key, you can't. [if enQsig uses 3DES]
I do have a backup of the private key, but it’s 1. out of reach at the
moment and 2. it’s a pain to restore. So far, I’m
> I've got a new Yubikey NEO that I am trying to set up for SSH authentication
> [...] PIN entry works correctly, but after this everything fails with an
> error 100663404 and returns "signing failed: agent refused operation"
For closure, this problem has been solved. I had too many PIN
On Wed, Aug 15, 2018 at 1:57 PM Peter Lebbing wrote:
> > https://gist.github.com/cipriancraciun/c8a0dfb973b586053c167fec91093d9c
>
> Hey, that systemd service file seems to basically grab cryptsetup
> handling from the clutches of systemd, enabling all sorts of operations
> not possible with
On 06/08/18 08:38, Ciprian Dorin Craciun wrote:
> My script and systemd service file can be found at the following link:
>
> https://gist.github.com/cipriancraciun/c8a0dfb973b586053c167fec91093d9c
Hey, that systemd service file seems to basically grab cryptsetup
handling from the clutches of
On 15/08/18 09:08, Felix E. Klee wrote:
> So, perhaps enQsig is using 3DES.
Good find! This sounds plausible. I myself had completely forgotten
reading about this bug.
Besides, I completely dismissed the encrypting application in this case
because it decided to encrypt the session key to your
On 03/08/18 09:16, Felix E. Klee wrote:
> As I would like to understand things a bit better, do you think it is
> possible to get some more details?
Answering this in any detail would be a lot of answer. But the basic
mechanism is --debug, --debug-level or perhaps just --debug-all and
sifting
*Update:* Yesterday, I was reading the [GnuPG wiki page on
SmartCards][1] due to another issue. At its bottom I found listed as
known bug:
* Encrypted message with 3DES can't be decrypted with OpenPGP Card
(V2.1, V3.3 without fix)
- Due to the bug, it results: Missing item in object
