Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Hahah (Score 0) 246

Someone fucking up on a test, then having the bright idea of "hacking" a computer (when obviously having no skill whatsoever to do so), then lighting the computer on fire without either considering that this will not accomplish anything nor having the sense to know that this fire might not be limited to the computer but may spread...

If that are the actions of a rational adult, ... Ok, it's the US, I withdraw my argument.

Comment Re: Kill the entire H1B program (Score 1) 636

The H-1B program is different because H-1B workers who leave their jobs are also legally required to leave the country. This makes them captive labor, almost to the same extent that illegal immigrants are. IMO, we should make green cards easier to obtain and kill the H-1B program outright. By ensuring that foreign workers have similar employment mobility to native workers, it would reduce the ability of unscrupulous companies to bring in workers from overseas and pay them wages that are below the regional going rate. (They would still be able to do it, but they wouldn't be able to retain those employees, so they would eventually be forced to pay wages that are competitive within their geographical area.)

Comment How about sane warnings? (Score 1) 324

As it is now, you are not notified of security issues when you have no security whatsoever. HTTP sites should be given a dire, red warning because they represent the least secure position online. An SSL site with an expired certificate is far more desirable than an HTTP website.

Green should represent proper SSL certificates, as it does now.

But there's one more problem with SSL/HTTPS sites that nobody talks about: the fake SSL certificate. Your browser *probably* trust a multitude of SSL certificate vendors, and *any* of them can issue a certificate for *any* domain.

So there are literally hundreds of SSL certificate vendors that could issue a cert for google.com or whatever, and you wouldn't know. If the NSA offered a bit of $$ to a commonly trusted (but otherwise unheard of) certificate vendor to issue a few certificates to be used discreetly....

See the problem?

If I go to Thawte or RapidSSL to get a cert, I should have the ability to publish my vendor of choice, and nobody else's certificates should be considered trustworthy. Similarly, I should be able to publish revoked certificates the same way.

Why hasn't this already been done?

Slashdot Top Deals

"One lawyer can steal more than a hundred men with guns." -- The Godfather

Working...