To check whether a server is using the weak ssh-rsa public key algorithm, for host authentication, try to connect to it after removing the ssh-rsa algorithm from ssh(1)'s allowed list:
ssh -oHostKeyAlgorithms=-ssh-rsa user@host
If the host key verification fails and no other supported host key types are available, the server software on that host should be upgraded.
We then tell git bisect to run the command lein test on each commit until the command exits with a 0 exit code, indicating that we’ve found the first broken commit.
According to git-bisect(1), "the script should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad."
Detangle is now open-source. You can specify a list of "internal sites" to be opened in your main browser, while other sites get opened in contained / separate profiles (or Incognito mode). Great for added protection against UXSS and other threats.
The number has 128 digits, which could indicate a (big)
mistake from the malware author, who wanted to generate
a 128 bytes key.
Finally, we simply deal with RSA-464 encryption, which
can easily be broken on a standard PC in a matter of hours.
I think there's more here than what can be fixed with tape. Your computer has computers in it that can be re-programmed in ways that the OS doesn't tell you about. From the pdf:
The same technique that allows us to disable the LED, namely
reprogramming the firmware that runs on the iSight, enables
a virtual machine escape whereby malware running inside a
virtual machine reprograms the camera to act as a USB Human
Interface Device (HID) keyboard which executes code in the host
operating system.