bcl

Gemalto doesn't just make sim cards. They also make OTP tokens - http://www.gemalto.com/readers/tokens

Usually takes me a month to realize it's a new year :)

It would be even nicer if the mainline version of Minecraft would adopt the Python API they implemented for the Pi edition.

Previously discussed - https://hn.algolia.com/?q=facebook+unhappy#!/story/forever/0...

I saw Brian's presentation at SEAGL[1] this year, it was excellent! He's a very dynamic and expressive speaker and takes something that could be dry and boring and makes it interesting for all experience levels.

[1] http://lanyrd.com/2014/seagl/sdfgdw/

Well, it depends on your goal. In this case it is to avoid Verizon adding stuff to my http traffic.

A solution to this is to setup openvpn on a VM someplace and route all your phone's data traffic through that. I've done this using the Fedora open vpn guide (https://fedoraproject.org/wiki/Openvpn). To get it working on the iPhone I also had to add this to the server config:

push "redirect-gateway" push "dhcp-option DNS 8.8.8.8"

Read the article. Click the link. It will tell you what tracking id I got.

The Aeropress isn't exactly non-portable.

" Draper himself doesn't even know who started the fundraiser, but the money is intended to help with his medical bills"

If he doesn't know who started it, how do we know the money will actually get to him?

Instead of reinventing (and unexpectedly exposing your whole network) you should use something like shorewall to setup your firewall. http://shorewall.net/

The title needs to be updated to reflect the article date.

Works fine for me on Verizon.

The difference here is that with Tor it is me who is providing the bandwidth for them to use. I want to see Tor succeed, but I just can't get past the fact that the people running .onion directories seem to feel that since it can be used for anything that everything should be promoted equally.

All you need to do is look at the hidden services listed on any of the .onion directories. This is why I stopped running a node -- I just can't justify helping criminals, even if I have no way to know which data passes through my system.

You still need to meet the FCC specs for not causing interference (in the US at least), which can be costly. And you can be sure that a bare board with no shielding around the RF sections is going to be pretty noisy.

If you're interested in the science (and some of the problems we have in the US) read UW Professor Cliff Mass' blog - http://cliffmass.blogspot.com/

Totally unrelated, but why the heck does the cloudflare blog have some sort of facebook iframe ad popup? When it fails (blocked by AB+) it covers up part of the article.

There is no mention of Bitcoin in this document. The title should be corrected.

It forgets step 0. Write every day.

I've been using BackupPC on a Linux box for years. First with RAID5 and now with RAID1, using ssh+rsync I can backup my Linux and OSX systems and have access to older backups via the web interface. For totally irreplaceable items I also back up a subset to Glacier.

The code he pointed to is for kernel 2.6.18 which at this point could be considered ancient history. If you look at current master - https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux....

it looks like it has been re-factored somewhat, although the lock is still in there.

RHEL6 update announcement

https://rhn.redhat.com/errata/RHSA-2014-0376.html

F20 and F19 updates are on their way to the updates repo.

https://admin.fedoraproject.org/updates/openssl-1.0.1e-37.fc...

https://admin.fedoraproject.org/updates/openssl-1.0.1e-37.fc...

Linux box + motion + IP cameras.

If git pull is causing problems for you, you are not using git correctly. You shouldn't be doing work on upstream branches -- that's one of the wonderful things about git, branching is cheap.

When working with more than 0 other people you should reserve the upstream branches for merging your work and pushing. Do your actual work in a branch and you can easily commit/stash our working tree, switch to the other branch and examine their changes.

Sounds like tin (solder) whiskers:

http://nepp.nasa.gov/whisker/background/index.htm

While this is all true, there are a couple of other important considerations:

1) packagers have a history with their packages. They fetch from the same source, verify with the existing GPG key, etc. They aren't fetching from a different random source for each build. As part of the package review process the upstream source should be reviewed and confirmed.

2) Everyone in the distribution is using the same code. Unlike Windows/OSX the users get the same binaries from a single source. This allows problems to be corrected quickly for everyone at the same time.

Here are a number of asyncio examples, including Guido's web crawler - https://code.google.com/p/tulip/source/browse/examples/

If this had been Python it wouldn't have been an issue ;)

I find it hard to believe that this code had a proper peer review before being committed. A 2nd and 3rd set of eyes experienced at reading C should have spotted this. Peer review is especially important when dealing with core security components like this where simple mistakes can have huge consequences.