Is that a bipod under the G36?
Slightly over the top, isn´t it? At least in combination with the tiny standard optics. (otoh, what do I know, I´m more an SVDS kind of person, so ymmv)
A hackathon next week will see 'net developers get to work consigning more insecure cryptography to the /dev/null of history. The Internet Engineering Task Force's 103rd meeting kicks off in Thailand with the customary hackathon starting on 3 November, and one of the agenda items is getting the RC4 cipher out of SSH (secure …
There have to be some old devices out there that support ssh but would need RC4 since newer stuff is too computationally intense (plus you wouldn't be able to upgrade its firmware)
Should leave them in, with some sort of a setting in the config file to enable insecure stuff on a per host basis...
It isn't the public facing ones that are the real issue, it is all the stuff hidden away with automated scripts that will be a real pain to find and update.
My toolbox includes a copy of the last openssh to support ssh protocol 1 with all the bad ciphers because sometimes it is needed.
While the authors seems to treat ssh as a interactive utility, there is a massive amount of data that is slung around automatically with it. The scripts used tend not to be too robust with even simple things like server key types being updated.
Yep, I've written scripts using scp that specified options for older encryption options because that's what the server had available. Might have even been RC4, this was back in 2009/2010.
Hopefully those devices running older SSH versions have been upgraded by now, but if those scripts are still operational and the script server they are running on gets updated to a RHEL version with the latest SSH stuff is going to break and cause someone heartache...