Comment Re:WTF? (Score 1) 114
Why in the world would you add a device's public host key to the authorized key file?
Why in the world would you add a device's public host key to the authorized key file?
The host key pairs are NOT used to authenticate the incoming user.
They're used to prevent MITM attacks (by uniquely identifying the endpoint), so this statement
"It’s hard to say if the key errors means that a remote attacker could log into all of the devices, as it would depend on how the routers are configured for remote authentication."
It's complete bull; the article is written by a clueless moron.
Attackers would have to use the keypairs to setup MITM attacks for EVERY machine they wish to compromise.
Revision controlling machine generated xml (or any other machine generated code) with the assumption that it is human readable (because of the format) is a bad idea, just like keeping compiled binaries under revision control is a bad idea. It is just as non-human readable.
You want to keep the actual human generated source under revision control... which you obviously can't do for any document generated by a GUI.
Sure, you can use revision control to simply keep a history of versions, but that doesn't do anything for any of the multitudes of other reasons to use a RCS.... hell, you can keep a history by just timestamping every revision of file in their filenames.
Unless they can be bothered to learn something like docbook, they deserve any and all pain arising from the drawbacks of whatever idiotic workflow their uninformed, incompetent, clueless PHB imposes on them.
How about something simple then?
3-way merge? Interactive merge?
And that can be tied in to svn or git hooks w/o a windows machine?
All the more reason not to use opaque binary formats at all.
That functionality belongs in the revision control system, not hidden away in some app someplace.
LOL @ binary formats and revision control.
Why doesn't the summary mention to look for
Wouldn't that be the single most important piece of information to convay? Oh. No. The single most important piece of information seems to be to plug some AV garbage.
How about IMAP support that doesn't completely suck?
o365 is such a huge POS.
I'm not sure you know what rent-seeking is.
Has any law enforcement agency ever maintained that they need a warrant for anything?
Don't forget avahi, which reliably causes shutdown to take o^n time (vs number of network interfaces and ipaliases) to shut down
TSA trying oh so very hard to appear effective.
The system was down for backups from 5am to 10am last Saturday.