Forgot your password?
typodupeerror

Comment: Re:Does it matter? (Score 1) 63

by heypete (#47698601) Attached to: Plan Would Give Government Virtual Veto Over Internet Governance

Of course this is about power shifting towards governments in general. This is to be expected - after all, we can't just have random people running the internet and governments happen to be the very things that represent their countries internationally

(Emphasis mine.)

Why not? That's basically what Jon Postel did: he basically singlehandedly administered the DNS root and was IANA.

Sure, things are different now, but we certainly have had random people running the internet. It worked then, why not now?

Comment: Re:https is useless (Score 1) 166

by heypete (#47681719) Attached to: Watch a Cat Video, Get Hacked: the Death of Clear-Text

If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots. That's basically a death sentence to companies like VeriSign (rather, their cert-issuing division).

I wouldn't be too sure of that.

Of all the companies that have aided the NSA, how many are out of business or even really hurting?

Companies like what? The ones making network-tapping hardware and whatnot cater toward a limited market, not the general public. Certificate authorities directly transact with server administrators, but their primary audience are end-users and they have wide public exposure. If a CA was found to be doing shady things, browsers would remove their roots. That'd basically kill off the offending CA.

Comment: Re:https is useless (Score 1) 166

by heypete (#47681699) Attached to: Watch a Cat Video, Get Hacked: the Death of Clear-Text

>If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots.

HAHAHAHAno. Thanks to the demon that is backwards compatibility browser vendors have implicitly or explicitly confirmed that they cannot actually revoke root certs. Or, more specifically, that many websites rely on that particular root to verify their identity and would break horribly if a root cert got revoked. i.e. revoking a misbehaving root will break the web.

Why not? There have been roots that have been revoked due to being compromised and which have issued bogus certs (e.g. DigiNotar). That's caused some chaos, but people adapted.

Sure, VeriSign is large and commands (either directly or through its subsidiaries) a substantial fraction of the CA market. Nuking it would be a Very Big Deal that browsers wouldn't take lightly, but I have no doubt that if it were shown that VeriSign (or Comodo, or other CAs) were found to be issuing bogus certs for the government to compromise people, they'd get their roots pulled by browsers. That's a death sentence for a CA, hence my skepticism in response to the proposal that they're actively assisting governments.

A better solution would be the ability to provide multiple root certs, which is not technically feasible today, and won't be for a while - even things like SSL vhosts are considered unreliable due to the prevalence of legacy browsers that don't know how to use the proper TLS extensions for hostname identification. So maybe in 10 years we can start telling site operators that they can turn on multiple certs, and 10 years after that browser vendors will have enough data to determine if it's safe to actually revoke a root cert or not. In the meantime you will have to convince HTTPS services that it's worth paying n times as much in certification costs to avoid a hypothetical root revocation.

Agreed. That would be nice.

Comment: Re:https is useless (Score 4, Informative) 166

by heypete (#47681287) Attached to: Watch a Cat Video, Get Hacked: the Death of Clear-Text

What good is https going to be against the state? You think they can not coerce Verisign et al to hand over a copy of the root keys?

Sure, they could, but I doubt they are.

If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots. That's basically a death sentence to companies like VeriSign (rather, their cert-issuing division).

While typical users won't notice, there's still plenty of risk to getting caught, particularly when targeting anyone using major web properties: Chrome, for example, has a bunch of high-profile sites "pinned" and will report back to Google if bogus certs are being used (they identified a bunch of MITMing with compromised certs in Iran in this way). Other add-ons like Perspectives make it easier to detect if unexpected certs are showing up.

Could they get away with issuing infrequently-used certs for highly-targeted, one-off uses? Possibly, but each time they do the risk to their entire business increases.

I suspect the government would much prefer to do things sneakily in the shadows, rather than involving major CAs in such a risky role.

Comment: Re:Fiber to the Home (Score 2) 98

by heypete (#47638299) Attached to: For Fast Internet in the US, Virginia Tops the Charts

Compared to what you can get in Europe or Asia, those "decent prices" are in fact insanely expensive.

Perhaps. Depends on the location and provider. Here in Bern, Switzerland, the cable company offers 250/15 internet for CHF 89/month ($98 USD). That's only $10 more than the 200/200 for $89.95 offering. Not unreasonable. For CHF 105/month they package a bunch of cable TV channels (including European and American sports) and 250/15 internet.

Swisscom, the incumbent phone company, has fiber-to-the-home. 300/60 internet with even more TV channels costs CHF 154/month. They offer up to 1000/100 connection if you're willing to pay and extra CHF 80/month above the CHF 154 rate. That's USD $258, only $8 more than the 1000/1000 plan offered in Clarksville (though the Swisscom offering does include TV. Phone is an extra CHF 15).

Then again, Switzerland does tend to be expensive. You may get cheaper service in other countries, but it is quite comparable in terms of cost here.

Comment: Re: Great step! (Score 1) 148

by heypete (#47636461) Attached to: Google Will Give a Search Edge To Websites That Use Encryption

While I wish they allowed free reissuance of certs at any time, I don't really see why requiring revocation is a showstopper.

It's not a showstopper, per se, but they do charge a revocation fee ($25, I think?), so that makes it decidedly less than free.

True, but how often does one need to revoke a certificate? Other than Heartbleed, I think I've only revoked one certificate in the last 10 years or so. Amortized over that timeframe, the costs are negligible. That said, I would like it if StartSSL would offer free revocations in the case of something like Heartbleed, where certs are compromised through no fault of the customer, but I understand the business reasons for not doing so (CRL/OCSP isn't free).

Of course, I've abandoned several certs where I deleted a VM hosting a site I no longer needed, but since the cert was not compromised and the private key was deleted, I just let the expiration timer run out. No big deal.

Comment: Re: Great step! (Score 1) 148

by heypete (#47636445) Attached to: Google Will Give a Search Edge To Websites That Use Encryption

To clarify I fully understand why startSSL do this, they are a buisness and they need to make money and they are certainly the best value widely recognised CA I have found.

I just don't think using startSSLs limited free certs as a rebuttal to claims that SSL increases costs for website operators is reasonable. Either you pay to get the wildcard certs or you pay to get extra IPv4 addresses or some combination of the two.

Why not just use SNI? I have multiple SSL-enabled virtualhosts running on a single server, and other than Internet Explorer on Windows XP and Android 2.x (neither of which I care about, as the former is EOL while the latter is effectively EOL) every browser on desktop and mobile devices works properly. I spend more money every two weeks on caffeinated beverages than my entire annual budget for SSL certs, and I have more than most. My cert budget is dwarfed by hosting costs (which I pay regardless of SSL support or not).

If you don't care about those systems (and I don't), SNI is perfectly satisfactory. If you need to support those old systems for some reason, you're probably a commercial enterprise who can afford IP-based SSL or wildcard certs. For typical individuals or small/medium-sized organizations using SNI, adding SSL support to your sites will essentially be a non-issue in terms of cost.

If anything, Google adding a small boost to SSL-enabled sites should encourage and improve support for SNI and hopefully sweep away the few older browsers that don't support it. I'm all for it.

Comment: Re:Avoid the Asus RT-N66U .. overpriced (Score 3, Informative) 427

by heypete (#47634643) Attached to: Ask Slashdot: Life Beyond the WRT54G Series?

Gotta agree. My RT-N66U(Shibby 121) is running a crap load of stuff with zero downtime. VLAN, IPTV, VoIP, OpenVPN server and client, Print server, etc etc etc.

I've got an RT-AC68U as my access point. Not as mature firmware wise, and hard to test to it's full potential, but rock solid none the less.

ASUS can shut up and take my money.

Seconded in regards to the N66U. It's a fantastic router. I've been running Tomato Shibby for years (most recently v121) and it's been rock-solid, reliable, and stable.

There's only one downside: Tomato doesn't include the necessary kernel module for hardware accelerated WAN-to-LAN NAT/routing. This only matters if your downstream WAN bandwidth is greater than ~120Mbps. If your downstream bandwidth is less, the software routing can keep up and you'll run at full speed. If your downstream bandwidth is greater, you will be limited to ~120-130Mbps, as that's as fast as the N66U can route in software. LAN-to-LAN bandwidth will run entirely in hardware regardless of what firmware you have.

My ISP just upgraded me to a 250Mbps downstream link, so I reluctantly went back to the factory firmware to take advantage of the hardware acceleration. It's clunky and annoying compared to the elegance of the Tomato web interface, but it works. The Merlin firmware maintains the look-and-feel of the factory firmware, includes support for hardware acceleration, fixes a few bug and adds a few features (but not as many as Tomato) that makes it suck less.

I highly recommend the N66U.

Comment: Re: Great step! (Score 3, Informative) 148

by heypete (#47625537) Attached to: Google Will Give a Search Edge To Websites That Use Encryption

2: they make the expiry artifically short (the CA industry as a whole does this but startSSLs free certs are epecially bad),

A validity time of one year is pretty standard for SSL certs (paid certs often charge per year). Could they issue them for 20 years? Sure, but a one year validity is not unusual. Class 2 certs are good for two years.

3: they refuse to renew certs until just before they expire and refuse to reissue certs without revoking the old one.

I get renewal notices two weeks prior to expiration. That's pretty reasonable. If I recall correctly, I can generate a new cert for my site any time in that two-week period, so I don't need to wait for the cert to expire before replacing it.

While I wish they allowed free reissuance of certs at any time, I don't really see why requiring revocation is a showstopper.

4: each free cert only covers a domain and one hostname under that domain (e.g. bar.com and foo.bar.com). This effectively means you end up needing one IP per hostname you want SSL on (until IE on XP becomes insignificant anyway).

That's also the case for pretty much any of the inexpensive paid certs too. You can always get a wildcard cert but most CAs charge at least $100/year for a single wildcard cert. StartSSL charges $60 for Class 2 validation, and you can issue unlimited certs (wildcard or not). Organizations can get Class 2 certified for $120 ($60 for identity verification, $60 for organization verification) and can issue unlimited certs. For a company needing more than one cert, StartSSL is still cheaper.

It's nice that there is a free (as in beer) option for some people but it's also clearly got a number of artificial restrictions on it to push people towards their paid options.

Considering their paid certs are often cheaper than comparable offerings from other CAs, it doesn't really seem unreasonable to me. Doubly so because they're run by competent people who respond promptly to inquiries, even from free users. I've been a StartSSL customer for years (and also used other CAs like GoDaddy, Comodo, Thawte, etc.) and the customer service from StartSSL has always been excellent.

If you don't want to get a StartSSL cert or they don't meet your needs, that's fine. NameCheap and others sell single-domain Comodo certs for $9/year. RapidSSL certs are a buck or two more per year. That costs less than a single beer at the local bar. Hardly a massive expense.

Comment: Re:No towers in range? (Score 2) 127

by heypete (#47612695) Attached to: T-Mobile Smartphones Outlast Competitors' Identical Models

That doesn't jive with my results though. At work, if I'm in the building in the center all day without appreciable service my phone doesn't last the day. If I'm at an outside wall, my phone barely makes it through the day without any significant usage, barely getting one bar. If I'm out and about I've had service work on standby for couple of days when I've forgotten to charge it overnight.

That seems to match with what I'm saying: when the phone is constantly searching for signals it has the receiver enabled all the time and the gain turned up to maximum, using more power. When it is in an area of low-but-there signal, the receiver isn't powered up as often, but the gain is still high, so it uses a medium amount of power. When you're out in the open and there's lots of signal, the receiver isn't powered up as often and the gain is low, so it uses the least amount of power.

I apologize if I wasn't clear before.

Comment: Re:No towers in range? (Score 2) 127

by heypete (#47609865) Attached to: T-Mobile Smartphones Outlast Competitors' Identical Models

Usually, a terrestrial phone doesn't need to do anything much to "look" for a tower, besides keeping its receiver turned on. Towers emit beacons, and if you don't hear the beacon, there's no point in you sending anything - you won't receive a reply because you don't even hear the tower's beacon.

Indeed, many (most? all?) phones won't transmit at all unless they hear the tower's beacon, since it's possible they could have been moved to a jurisdiction where it is not allowed for them to transmit on certain frequencies they would otherwise use.

Of course, keeping the receiver powered to listen for the beacon does use a not-inconsiderable amount of power, so searching for signal will use more power than a phone that is connected to the network and idle.

Comment: Re:Nuke it from orbit, then restore from backups. (Score 1) 150

by heypete (#47608893) Attached to: Synolocker 0-Day Ransomware Puts NAS Files At Risk

If the keys are stored on the box in any way then they are compromised because the box is. The synology box is rooted, any information stored on that box is compromised. If for example your root key for S3 is backed up on the NAS then it's compromised.

Agreed. That's why you shouldn't use the root S3 access key for anything (in fact, don't generate one at all). Use service-limited, least-access keys for AWS accounts: there's no reason a NAS should have an access key capable of creating EC2 instances. It should have list+write access only to S3 (and/or Glacier). If users want to delete files from S3, they should have to log in with a different user (perhaps to the AWS console) and specifically do that.

Amazon provides good options in this regard, and it's too bad if users aren't taking advantage of them.

People are glossing over this, if the box is rooted everything it knows and stores is compromised, that's how people need to be analyzing this instead of blowing it off as no big deal.

In this specific case, the malware does not seem to want to steal user data, only to encrypt it and ransom it back to users. Sure, it could steal data, but it doesn't seem to do so. It's a big deal to those who are unprepared and don't have proper backups, but it could definitely be worse.

Comment: Re:Nuke it from orbit, then restore from backups. (Score 2) 150

by heypete (#47607873) Attached to: Synolocker 0-Day Ransomware Puts NAS Files At Risk

You do realize that for the S3 backup to work Synology or the NAS (and the NAS has you Synology login info) has your login information for S3, and that if this thing is owning the NAS there is a pretty damn good chance the malware has owned your S3 instance as well right? The only way it wouldn't is if the S3 backup is totally manual.

Amazon has a very extensive authentication system -- you can easily configure the Synology with an S3 access key that only has "List Files" and "Upload Files" permissions, but not "Delete Files" or "Overwrite Files". This way, even if the Synology box gets owned or a user fat-fingers something, the files on S3 aren't at risk. You don't (and shouldn't) need to use your AWS root access keys for S3.

I have a similar setup with Amazon's Glacier: my standard access key has only list, upload, and retrieve permissions. A separate access key is required to delete files (I've configured my Glacier client, FastGlacier, to prompt me for a password when I switch to the "delete" key) so that I don't accidentally end up deleting important backups.

Man is the best computer we can put aboard a spacecraft ... and the only one that can be mass produced with unskilled labor. -- Wernher von Braun

Working...