On Wed, 25 Feb 2015 10:49, pe...@digitalbrains.com said:
> something. It should be:
>
> S2K specifier 110
Well, it is 101. I just updated doc/DETAILS> It now reads:
* GNU extensions to the S2K algorithm
1 octet - S2K Usage: either 254 or 255.
1 octet - S2K Cipher Algo: 0
1 octet - S2
Oops, I realised I made a mistake.
On 24/02/15 19:49, Peter Lebbing wrote:
>> - [Optional] If string-to-key usage octet was 255 or 254, a
>>string-to-key specifier. The length of the string-to-key
>>specifier is implied by its type, as described above.
>
> specifier 110
> ha
On 24/02/15 17:52, Werner Koch wrote:
> for everything else you need to look at the code (parse-packet.c)
RFC 4880 specifies that for a string-to-key usage octet of 255, the final two
bytes are a checksum, but it /is/ part of the encrypted data for v4 keys. I was
curious and also had a look at the
On Tue, 24 Feb 2015 15:55, leonard.dal...@taztag.com said:
> I have tried to find a description of this S2K format, but I haven't
> found one. Does anyone know where I can find a description of this
> "experimental" S2K ?
doc/DETAILS shows this
* GNU extensions to the S2K algorithm
S2K mode 1
Hello,
I am trying to write a program that read GPG privates keys that have
been exported to a GPG smartcard using GPG. Those keys are encoded
unsing a S2K Specifier that is described in RFC 4880 as
"experimental" (Tag 101). GPG (using gpg --list-packets) describes this
as "gnu-divert-to-card S2K"
