Encryption & authentication methods¶
fastd supports various combinations of ciphers and authentication schemes using different method providers. All ciphers, message authentication codes (MACs) and method providers can be disabled during compilation to reduce the binary size.
See Benchmarks for an overview of the performance of the different methods.
salsa2012+umac is recommended for authenticated encyption.
null+salsa2012+umac is the
recommended method for authenticated-only operation.
Salsa20/12 is a stream cipher with very high speed and a very comfortable security margin. It has been chosed for the software profile in the eSTREAM project in 2008.
UMAC is an extremely fast message authentication code which is provably secure and optimized for software implementations.
Too keep the binary as small as possible, only the following methods are enabled on OpenWrt by default:
Of these, the GMAC-based methods may be dropped in the future to further reduce the binary size, as UMAC is the superior authentication scheme (it is faster than GMAC, provably secure and its software implementation isn’t suspect to timing side channels).
List of methods¶
||generic-poly1305||aes128-ctr||none ||, |
This list is not exhaustive. It is possible to combine different ciphers for data and authentication tag encryption using the composed-gmac and composed-umac method providers; these methods aren’t listed here as this is not very useful.
Since fastd v11
salsa20+poly1305should be used instead (or even better a more performant method like salsa2012+gmac);
xsalsa20-poly1305will be removed eventually.
|||(1, 2, 3) The MAC is integrated in the method provider.|
|||(1, 2, 3, 4, 5) AES is very slow without OpenSSL support. OpenSSL’s AES implementation may be suspect to cache timing side channels when no hardware support like AES-NI is available.|
|||(1, 2, 3) Poly1305 is very slow on embedded systems.|
|||(1, 2, 3, 4, 5, 6) The cipher is used to encrypt the authentication tag only, the actual data is transmitted unencrypted.|
|||Only authentication of peers’ IP addresses, but no encryption or authentication of any data is provided.|
|||Both the cipher and the MAC are integrated in the method provider.|