WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Hardware Security Token
@ 2020-07-15  8:29 Marjan Olesch
  2020-07-29 18:27 ` Jeffrey Walton
  0 siblings, 1 reply; 4+ messages in thread
From: Marjan Olesch @ 2020-07-15  8:29 UTC (permalink / raw)
  To: wireguard

[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]


I'm a student in computer science and currently writing my master 
thesis. It's about an STM32F103 based security token, that is 
specifically designed for the WireGuard authentication. For now, it has 
more like a proof-of-concept character, and I'm aware of the possible 
security flaws, which also have been discussed here before 

Nevertheless I want to briefly present my team's concept, as well as our 

The Noise IK pattern shows clearly, that it is not enough to just 
outsource DH(SiPriv, SrPub) to the token, since this part would be 
static, as long as the private static key or the peer’s public key does 
not change. Considering chapter 5.4 in the wireguard paper (initiation 
scenario), at least the operation (Ci, k) := Kdf2( Ci, DH(SiPriv, SrPub) 
) needs to be ported to the token, since it is the Ci that is based on 
ephemeral keys. Furthermore, the k, resulting from the KDF2 is a secret, 
that is needed to create the AEAD. This means, that the k is kept on the 
device, while the AEAD is also calculated on the token. Because the AEAD 
calculation requires a timestamp, the device needs to run an RTC. 
Considering all this, an attacker that intercepts the communication 
between token and computer cannot replay the handshake with the 
information transceived, since he is not able to alter neither the time 
stamp, nor the k.

Unfortunately, the STM32F103 can - from our findings - only run the 
time, not the date, while powered off (with backup battery connected). 
So for now the date has to be delivered once a day in our 
implementation. The delivery can be protected by a password and/or a 
hardware button for better security. The most important algorithms 
Blakse2s, curve25519 and chacha20-poly1305 run on the STM32 and we were 
able to reconstruct the operations needed, in order to source out the 
particular parts from the handshake initiation. The communication to the 
(virtual COM) device runs via USB and a really simple rpc protocol. We 
used wireguard-rs for the development and everything stated above works 
at the moment.

I don’t want to bother you with too much information. Please let me 
know, if you have thoughts about this idea and/or the implementation. I 
would be pleased to present you everything in more detail.

Code can be found on https://gitlab.gwdg.de/uenigma

Best Regards,


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5406 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-15  8:29 Hardware Security Token Marjan Olesch
2020-07-29 18:27 ` Jeffrey Walton
2020-07-29 18:37   ` Phil Hofer
2020-07-29 18:42     ` Jeffrey Walton

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git