2 ms·
At work I connect to old embedded hardware running ancient versions of dropbear. I already have to whitelist some deprecated algorithms to connect to them succe
by simias 9y ago
At work I connect to old embedded hardware running ancient versions of dropbear. I already have to whitelist some deprecated algorithms to connect to them successfully (most notably SHA1 HMAC) so I'll probably struggle even more with this newer version. I guess it's time to build a newer version of dropbear.
Not that I don't support their decision to drop support for these deprecated algorithms, it's our fault for running outdated software.
Actually the only thing that annoys me in these release notes is:
>Please note that the SHA256 signatures are base64 encoded and not hexadecimal (which is the default for most checksum tools).
Then why not use hex? Neither GNU coreutil's sha256sum nor FreeBSD's sha256 supports outputting in base64. OpenBSD's sha256 has a '-b' switch for base64 but by default it's in hex as well. Is it really worth adding this pain on the user just to save 20 bytes?