1 |
On Tue, Jan 19, 2016 at 6:26 PM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> |
3 |
> You can use apache client authentication with SSL certificates only. Of |
4 |
> course you will need to create a self-signed CA, which you will use to create |
5 |
> the web server public/private key pair and also sign each client's certificate |
6 |
> and upload it along with your CA certificate to the user's browser. This |
7 |
> explains the principle: |
8 |
> |
9 |
> If a user certificate is lost of feared compromised, you revoke it with your |
10 |
> CA and upload the CRL to the server. |
11 |
|
12 |
The problem is, how would you know? In a traditional browser |
13 |
(including Mozilla and Chrome on anything but a Chromebook) the key |
14 |
associated with the certificate is stored in a file on disk. Sure, it |
15 |
might be encrypted with a hand-typed password, but those passwords are |
16 |
not hard to brute force, and susceptible to keyloggers anyway. Those |
17 |
keys also are unencrypted in RAM while in use. If something stole a |
18 |
copy of your key, you'd likely never know. |
19 |
|
20 |
But, I agree they can be revoked if you discover the issue. |
21 |
|
22 |
Now, a solution a more traditional desktop is to use an SSL key stored |
23 |
on a smartcard, which I'm sure Diego has blogged about on |
24 |
planet.gentoo.org as he is into those. That has all the advantage of |
25 |
the TPM as far as key security goes. However, you're still vulnerable |
26 |
to xss and keyloggers and such. |
27 |
|
28 |
Sorry to nitpick. I'd love to see more linux-based options for an |
29 |
ultra-secure platform. It is impressive that Google managed to |
30 |
commercialize one - you can accomplish quite a lot with FOSS tools if |
31 |
you put the time into it. |
32 |
|
33 |
-- |
34 |
Rich |