Comment Re:StartSSL (Score 1) 320
I assume there's some repository-like mechanism analog to apt-get/pacman/yum for server edition, right? Or do you actually need a graphica environment to maintain a SERVER?
I assume there's some repository-like mechanism analog to apt-get/pacman/yum for server edition, right? Or do you actually need a graphica environment to maintain a SERVER?
But some other sector might gain a lot with his addition, who knows!
Doesn't windows have windows update? Doesn't the server edition have remote installation mechanism analog to ssh+apt-get or something? Do you NEED a browser to maintain it?
So the browser on server is keeping you from upgrading your SSL stack? Why on earth would you use a browser on a server? If you REALLY must, why not just pick another browser; if you're (for some reason) using a browser on a server, you might as well download another, it's not like you're computer-illiterate.
Because reading code can be just as fun and useful as writing it for some people.
VLC's terrible for music. Ever noticed the pitch bending?
Nope.
Bad playlist controls?
Not everybody uses this, you know. Anyway, What's wrong with the controls?
Long initialization times?
Are you MAD?
I get 25ms initialization time (13ms userspace). What sort of hardware are you using?
Lack of seamless transition?
Care to elaborate? I've had no isues on this terrain either.
The only thing that VLC lacks is media library. And that's why I use mocp when I intend to open more than 2 or 3 files. But that's just about it.
Or just get a free cert from startssl.com.
People using tor can use self-signed certificates, since tor user won't be strongly alarmed by unusual security warnings.
There's no real need for wildcard certificates; just use SNI.
There's already plenty of SNI websites out these; your clients are already having issues visiting some sites out there, and the amout of sites will only grow and grow as XP is reaching it's EOL.
Actually, it's just IE on XP. Support for those end in april, so, it's not really an issue if IE+XP interferes with adoption to HTTP/2.0. It shouldn't be around long enough.
You need to use DNSSEC for this to be safe, and requires a sort-of-CA (the one that signs your domain). Otherwise, you're vulnerable to MITM.
I'm staying away from holidays with trojans or any other kind of malware, thank you very much.
Actually, the real problem is that people trust unknown third parties with all their bitcoins.
If banks were unregulated, unsafe and even maybe anonymous, would you still trust them with all your money?
Corporate clients buy Office N because Office N-1 is no longer supported and/or doesn't run in MS Windows-Latest. Simple as that.
They can share a torrent link in their own website, no need to go to a "torrent website". Debian, Fedora and OpenBSD do this; they just share the torrent file/magnet URL on their own websites.
It is easier to write an incorrect program than understand a correct one.