http://www.sefs.washington.edu/research.acl/Crows_and_Other_...
1,103 karma · joined October 27, 2011
http://www.sefs.washington.edu/research.acl/Crows_and_Other_...
As the Sheppey pile-up demonstrates, there's a lot of people who simply suck at driving - specifically maintaining sufficient braking distance and NOT cutting into someone else's braking distance when changing lanes (in poor conditions that space is for ME to stop in, not for YOU to slide into). As it is, I'm conscious that I need to be aware of the car behind as well as the car in front. The only way it'll work is if the car brakes for you, and then everyone has to have that technology.
I really want to crack some skulls together over the state of video compression codecs and OS support. Same thing happened with all the circle-jerking about HTML5 video - Flash had AS STANDARD a bunch of useful codecs (eg. Screen Video) for which there is no HTML5 good replacement if you want to do a lossless screencast.
Until whatever byzantine download scheduler deigns to push the patch to 4.3 to my phone, it's basically unusable.
And then there's the hardware issues (bluetooth kills WiFi if you try to use both at once), firmware issues (WiFi doesn't roam properly, ARP offload broken), straight-up bugs (wireless charging power management holds permanent wakelock preventing deep sleep)...
http://forum.xda-developers.com/showthread.php?t=2072930 really shows what Android is capable of.
Of course there's no need to rely on a central CA - it's not hard to run your own, and you can make it reasonably secure - say, a small ARM Linux board with passphrase-protected private keys on a removable SD card. Generating the keys in a secure way is perhaps a bigger problem - untrusted hardware RNGs, poor quality entropy after boot etc.
One can also keep a virtual machine CA on a hardware-encrypted USB device (IronKey, say, depending on your level of trust with Imation) - it's easy enough to bootstrap a tiny Linux distribuution from source with just OpenSSL and some utility scripts to issue & revoke certs.
You don't necessarily need a $5000 HSM solution to issue your own SSL certificates at this level.
I was reminded by a colleague today of a quote attributed to Roger Needham, something along the lines of "privacy is a transient condition in between people realising there isn't an omniscient god, and government realising there was a vacancy" (quoting second hand from memory)
As for updates, I imagine if you set up a domain you can run your own WSUS update server, MITM the connection, etc. - and then compare the behaviour with a "regular" home PC.
The problem really is how deep the hole goes - as per Ken Thompson "Reflections on Trusting Trust", 1984.
My spammers clearly haven't caught on yet...
zgrep grey /var/log/exim4/rejectlog* | rev | cut -c 2-3 | rev | sort | uniq -c | sort -rn | head
8 CA
7 IT
5 ES
4 BR
4 AR
2 TR
2 RO
2 IR
2 EC
1 PT- low-level crypto APIs (the 'DLLs' referred to obliquely in the article); these are more interesting. I imagine they could be compromised for weak session key generation or other leakage of key / plaintext, or generate the session key in such a way that the mythical 'NSAKEY' can decrypt it. Huge impact, if so, but only to certain software; AFAIK Mozilla doesn't use the Windows crypto API / certificate key store (but Chrome does).
- SSL certificate generation (built-in CA for Windows Server builds); certificates stored and replicated via Active Directory; does anyone actually use this? In fact, does anyone actually use client SSL? It is likely also used for domain peer replication, which could potentially be over an external network (but why would you not use a VPN there?)
- Encrypted File System; already contains an escrow key-recovery mechanism to allow administrators (including domain admins) to recover a lost user key. Only likely to be relevant if hard disk or backup images seized, so less impact.
- BitLocker drive encryption; similar to EFS but uses a hardware TPM and is per-machine rather than per-user. Fairly sure escrow key recovery at the domain level is possible here too. Again, only likely to be relevant if hardware or backups seized.
- Office document encryption; did anyone SERIOUSLY think this was worth using anyway? There are so many key recovery services out there for this (Elcomsoft et al)
- Communications applications (Skype et al); again, did anyone SERIOUSLY think this wasn't already being monitored, even before Skype became a Microsoft product?
- Some other OS-level 'phoning-home' behaviour. I simply don't believe that no-one has spotted this happening, if it's there - we can do traffic analysis too, and there are plenty of people running Wireshark on their own networks.
The e5c's main problem is they are SO sensitive they are completely unforgiving about the amplifier used - almost anything with a gain block after a volume control is going to have too high an intrinsic noise floor for them to not show it up.
Other bits were a Morningstar SunSaver solar regulator SS10 and a Nasa Clipper BM1 Battery Monitor (unnecessary extravagence - don't bother!). I also added a couple of 12V fluorescent lights powered from the SS10 so I didn't need the inverter running just for light.
It's a pretty simple set up, the hardest part is making up the high current battery cables - the clamps, fuse holder and connector to the inverter are pretty substantial to handle 100A.
I mounted the panel on the roof of the Apex shed with simple aluminium brackets. The wiring is pretty simple (more complicated by the battery monitor which has a 100A shunt resistor in the negative lead to monitor the load current).
I uploaded a pictorial wiring diagram at http://i.imgur.com/UX4Y29o.jpg?1 for you.
Note you can now get a 135W panel for £190, which is some indication of the falling cost over the last 24 months - the 50W Kyocera panel is now £80!
The lawnmower is the biggest drain (900W) and is really pushing the envelope - but in the summer I can cut 55 sq. metres of lawn once a week without any charge problems. In the winter the grass doesn't grow :) but I can run the other tools just fine. I was very surprised at just how well this system worked, but then I did splash out on a high end 50W Kyocera panel when I designed this. My only alternative would have been to bury an SWA cable across common ground and somehow run it to my consumer unit in a 1st floor flat, so I was prepared to spend £300 (as it was then) on the panel. They're a lot cheaper now.