Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] [RFC] New project: Crypto
Date: Tue, 29 Dec 2015 14:28:09
Message-Id: CAGfcS_ka7NTSSDDmJbvgqvwdMspX5T1TXa=Rt3NCCT_BzExxaw@mail.gmail.com
In Reply to: Re: [gentoo-dev] [RFC] New project: Crypto by Kristian Fiskerstrand
1 On Tue, Dec 29, 2015 at 8:58 AM, Kristian Fiskerstrand <k_f@g.o> wrote:
2 >
3 > On 12/28/2015 07:35 PM, Rich Freeman wrote:
4 >> On Mon, Dec 28, 2015 at 10:07 AM, Kristian Fiskerstrand
5 >> <k_f@g.o> wrote:
6 >>>> On 28 Dec 2015, at 15:58, James Le Cuirot <chewi@g.o>
7 >>>> wrote:
8 >>>>
9 >
10 >
11 >> That concern is hardly unique to phones. PCs suffer just as much
12 >> from this problem. The solution could potentially be the same.
13 >> For
14 >
15 > But here we already have smartcards (that everyone should and _is_
16 > using... right?)
17
18 I imagine that smartcards have about as much support on mobile as they
19 do on PCs, which is to say not much.
20
21 Sure, you can make it work, but software support for signing stuff is
22 limited in general, let alone support for doing it with smartcards.
23
24 >
25 >> signing it is a straightforward problem since there is nothing to
26 >> be kept secret except the key material itself (just send the
27 >> message to the signing device, and return the signature back). For
28 >> encryption
29 >
30 > for clarity (and what I think you already mean), the message in this
31 > case is the message to be signed (which is likely a blinded hash or
32 > something, so much shorter than the original data)
33
34 If you don't display the plaintext on the device doing the signing,
35 then you're vulnerable to a MITM unless you trust your PC, but if you
36 trusted your PC you wouldn't need the signing device.
37
38 The only thing a smartcard does is protects the private key itself.
39 It doesn't protect you from manipulation of the data to be signed, or
40 theft of plaintext, etc.
41
42 >
43 > Indeed, but at least the device won't be able to decrypt further
44 > communication as it'd only have access to the session key of the
45 > particular message. Loosing control of the private (sub)key is
46 > substantially worse, so that might actually be ok for the security
47 > parameters of the users.
48
49 I agree, there are degrees of failure.
50
51 >
52 > This already happen in several countries, including Germany and on a
53 > semi-related variant Norway (its government approved to sign
54 > electronically using BankID, where the banks does the verification).
55 > In germany there is even a CA that checks the government ID and
56 > certify OpenPGP keys based on it.
57 >
58
59 That is at least a step up. Should we require or at least recommend
60 government-signed keys for Gentoo in the few jurisdictions that
61 provide them? I guess the main concern would be if we wanted to allow
62 anonymity.
63
64 So many problems would be solved if a signature using a secure device
65 was required for every financial transaction. Just stick the PIN pad
66 on the signing device with a small display. The device is given a
67 message to sign including the date, amount to be authorized, and who
68 is getting paid. The device displays this info on its screen and
69 prompts for a PIN. For the problem of payment authorization that
70 would eliminate almost all forms of fraud that don't involve holding
71 somebody at gunpoint (and you could have a duress PIN and an encrypted
72 field in the authorization large enough to hold either a padded all
73 clear or an under-duress message with the timestamp and GPS
74 coordinates that only the bank could read).
75
76 In the US everybody seems to be afraid of big brother but big brother
77 has enough big data that he doesn't really need you to use his fancy
78 signing device anyway.
79
80 --
81 Rich

Replies

Subject Author
[gentoo-dev] Re: [RFC] New project: Crypto Duncan <1i5t5.duncan@×××.net>