Cabinet open source, only a file manager, actively developed.

No, millions of small business just buy computers with Windows Professional installed and join them to a small domain. Only big companies pay again for the Enterprise edition. Those small business are being f...ed removing this policy.

and by the way, the lawsuit has something to do with why I am talking. Twitter is shorting URLs on direct messages. The lawsuit want that stopped. Sending a private long URL using a direct message is being shortened, do you see the relation now?

Well, if you send a long URL, that by being long is very difficult to guess, and Twitter convert it to something so small that can be crawled, It is some kind of sharing. They should not be shorting URLs sent as direct messages, as this vulnerability shows, they are breaking the security of the long URL by shortening it.

I am not saying the Google is sharing anything. They give you a long URL that you can send to people you trust, then Twitter shorten it and that short URL can be crawled easily, au contraire of Google URL that is long enough to be treated like a password like authentication.

Exactly. I know people that send long URLs generated to privately share, like Google photos and send them using Twitter direct messages, believing they are not being shared with the world and they are wrong. Those long URLs know to be relatively secure even by Bruce Schneier are being converted to short ones, and accessible to the public. There is or was a lawsuit related to that

Follow the link, there is Public-Key Authentication now

NTP authentication

There could be a little truth in that, but no OS make the same mistake of letting the sender of a file decides what is executable or not (sender call it .exe or .scr and it is executable). Only Windows allow the sender to define what icon will be show for a file (sender embed a Word document icon to an executable and that is shown).

There are many ways to make phishing at non Windows users, but then some kind of vulnerability must be used (when opening a document), not a simple stupid trick of sending an executable and people confusing it for other thing. I think the most common one

Trust automatically only the devices detected at boot time. If someone had physical access to replace them before booting then you have worse problems. If your mouse/keyboard break at the same time when plugged (less probable) just press the power button and restart with the new devices. If only one broke then use the other to authorize the replacement

If they are only using the could providers servers as storage, probably true, but if they use them to run applications, keys are on memory to be able to read the data and process it.

I am on a Nexus device, a properly patched Android, but still I removed the MMS configuration from the cellular network AP configurations. I don't use or receive MMS, so there is no need for it. It is another good option.

There was one many years ago. They probably realized that people just used the packaged PostgreSQL and there was no reason for a separate product

It is not an OpenSSL exclusive problem, Is a protocol one. If you have SSLv2 enabled, you are vulnerable

true, but is is better that a fracking systray icon, for a normal user is just a system update

Your problem then is not the deprecation of the plugin, your applications will not run either with today browsers and Java 8. I am talking about people using current Java and the plugin. An extension can generate a JNLP file with the applet-desc element and make your applet run outside the browser. Hey current plugin allows you to use JNLP already to describe the applet and when running move the applet outside the browser window, on a different process.

If the applet is interacting with the HTML document, there you are out of luck, but many applets used to manage devices, are just a full page applet, and many of them can run as a JNLP applet.