On Thu, 23 Apr 2015 09:34, gni...@fsij.org said:
> If this is correct, I think that following patch fixes the problem.
I agree that this is could be the cause for the problem.
> diff --git a/po/Makefile.in.in b/po/Makefile.in.in
Changing that Makefile is not a good idea because it is a standard
On 23/04/15 00:22, Jose Castillo wrote:
> in the case of NFC, which is a big use case for the Yubikey
I hadn't considered NFC at all, it's good you brought it up. In fact, if
sniffing reveals the PIN and my threat model includes physically nearby
attackers, I wouldn't use it at all, whether it had
On 22/04/15 21:06, Werner Koch wrote:
> They probably downplay this bug because of the costs to replace all
> affected Yubikeys.
Oh wait... I somewhat assumed the things were field-upgradeable. I
thought you could pick the applications to load on a multi-application
Yubikey. In that case you can j
On 04/23/2015 11:26 AM, Ben McGinnes wrote:
> Cool. Since 2.1 is on a one month cycle, I might just wait for 2.1.4
> and try again, that'll give me the changes made from 2.1.3 and not
> trying to make a release equivalent tarball from the current repo
> (although if there's a script for that I mig
On Thu, 23 Apr 2015 03:39, gni...@fsij.org said:
> In the git repo, we have an entry of po/e...@quot.po in the .gitignore,
> so, I think that it is not maintained in the repo. When a developer
Right. It was removed in 2004!
I expect that bug reports for a certain version a done using freshly
u
