Page MenuHome GnuPG

glr (Gavin L. Rebeiro)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Aug 24 2020, 12:05 PM (59 w, 6 d)
Availability
Available

Recent Activity

Dec 7 2020

glr added a comment to T5169: gpg: Clarify output.

Although the output of --list-packets should not be parsed and is subject to change with each versions we know that ppl do it anyway and things start to break.

Dec 7 2020, 8:33 PM · Bug Report
glr created T5169: gpg: Clarify output.
Dec 7 2020, 1:34 PM · Bug Report

Oct 16 2020

glr added a comment to T5103: GPG4Win Executes through Personal (having admin rights ) account only.

@werner , if you would like some help moderating this bug tracker, I don't mind volunteering to do it.

Oct 16 2020, 2:32 PM · Support, gpg4win

Sep 16 2020

glr created T5071: Doc fix: simple typos.
Sep 16 2020, 1:19 PM · Documentation, Bug Report

Sep 15 2020

glr created T5067: Documentation: adopt RFC 2119 terminology. in the S1 Public space.
Sep 15 2020, 12:03 PM · Documentation

Aug 31 2020

glr added a comment to T3362: Prevent Smartcard from caching PIN when cache-ttl is set accordingly.

There is not a lot of demand for this, thus we have not continued to think about it.

@gniibe: We could implement this on the card by extending our ugly hacks on the login-data DO, which are currently:

Everything up to a LF is considered a mailbox or account name.  If
the first LF is followed by DC4 (0x14) control sequence are
expected up to the next LF.  Control sequences are separated by FS
(0x18) and consist of key=value pairs.  There are two keys defined:

 F=<flags>

 Where FLAGS is a plain hexadecimal number representing flag values.
 The lsb is here the rightmost bit.  Defined flags bits are:

   Bit 0 = CHV1 and CHV2 are not synchronized
   Bit 1 = CHV2 has been set to the default PIN of "123456"
           (this implies that bit 0 is also set).

 P=<pinpad-request>

 Where PINPAD_REQUEST is in the format of: <n> or <n>,<m>.
 N for user PIN, M for admin PIN.  If M is missing it means M=N.
 0 means to force not to use pinpad.

A new 'C' flag maybe?

Aug 31 2020, 5:10 PM · Feature Request
glr added a comment to T3362: Prevent Smartcard from caching PIN when cache-ttl is set accordingly.

@werner , I understand your poiont.

So, the best approach would be:
(1) Define some DO (Data-Object) or attribute/flag per key to control timeout or "force" by the card itself.
(2) Modify scdaemon so that it always ask authentication state to the card before doing crypto operation.
(3) Modify gpg frontend so that it shows those attribute/flag and setup.

Then, it is the card itself to control timeout or "force".

Aug 31 2020, 1:00 PM · Feature Request

Aug 25 2020

glr created T5035: Doc fix: simple typos.
Aug 25 2020, 1:13 PM · Bug Report