It's not a bug !
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/openssh/+question/669164
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for your reply.
I'm sorry, I did not think about watching the ChangeLog. Indeed, it is not a
bug, it may be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Hi, thanks for taking the time to file a bug.
The three ciphers you listed, aes128-cbc, 3des-cbc, and des-cbc, I
believe are not considered secure anymore. While your SSH client can use
them, it may not offer them without explicitly saying you wish to use
them as you have discovered.
It may be
Here are some change log entries confirming my suspicion:
openssh (1:7.4p1-1) unstable; urgency=medium
* New upstream release (http://www.openssh.com/txt/release-7.4):
- ssh(1): Remove 3des-cbc from the client's default proposal. 64-bit
block ciphers are not safe in 2016 and we
4 matches
Mail list logo
