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.

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.

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.

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.

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.

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.

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.

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.

Quite the contrary: StartSSL is accepted by every major browser and SSL/TLS library, and has been for years.

Well-known sites, like EFF.org, LibreOffice, and others use StartSSL-issued certs and don't have any issues. Sure, they're not Google-sized sites, but they're fairly major.

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.

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.

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.

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.

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.

You do have backups, right?

Wait, what? Where do you get the $45 per user cost? I don't see that anywhere on their website.

The "YubiCloud" (where Yubico hosts the authenticator servers) has two modes: free and premium. The free service is open to everyone, even commercial users. The premium service offers an SLA and monthly usage statistics, and costs $3/YubiKey/year (1000-unit minimum).

You can also host your own local YubiKey authentication servers and keep things entirely in-house. Yubico has reference implementations for free on their site.

For software tokens, Google Authenticator has apps for Android, iOS, and BlackBerry. They implement the TOTP standard, so any compatible code-generating software (such as the J2ME app I have on my non-smartphone) will work with it.

They also have a PAM module that works with SSH (or anything else that uses PAM). I've used it before, and it works great.

For reference, neither the apps nor the PAM module depend in any way on Google services, they don't send any data to Google, and will work perfectly happily in a totally offline environment (assuming all the servers and client apps have synchronized clocks).

I don't know about gigabit, but Steam has no problems maxing out my 150Mbps downstream link when I'm downloading games from a nearby server here in Switzerland.

The NSSF is the arms industry trade group. The private arms industry in the US is relatively small compared to, say, the oil, tobacco, alcohol, etc. industry and doesn't have anywhere near the same political clout as those industries. The largest source of income for the NRA is membership dues, and it's from their 5+ million members that they derive their political clout.