89 karma · joined September 8, 2010
This article is confused from the get go.
Seems pretty clear that they could decrypt the traffic they were interested in, they also talk about 5 years of retention of all traffic that they can decrypt at anytime. Sound familiar?
Looks like they used a squid feature: https://wiki.squid-cache.org/Features/SslBump
https://github.com/thejefflarson/little-cpu
I’m four instructions away from implementing the compressed extensions, and probably next week I’ll tackle the control and status registers. It uses an open source tool chain and is formally verified using riscv-formal. My hope is to eventually be able to compile some rust and get an fpga to blink an led :)
https://github.com/thejefflarson/getpasswd
It accesses the OS keychain to get the right password. I don't use offlineimap -- I use mbsync instead which has a PassCmd option where you can pass in a shell command (e.g. getpasswd <imap-server> <imap-user>). And another tool to add passwords to the GNOME Keychain:
https://github.com/thejefflarson/setpasswd
Adding passwords to the OSX keychain is easy enough, but I found it fiddly in Gnome's GUI. YMMV.
https://www.fbi.gov/news/testimony/facilitating-an-enhanced-...
As to the point about selectors, if a selector has an even remotely domestic terrorism related component, and is authorized by the FISA court, the FBI can and does see that information.
Edit: added qualifier about terrorism
http://www.nytimes.com/interactive/2015/04/25/us/25stellarwi...
A key part of the FBI's mission is "to protect and defend the United States against terrorist and foreign intelligence threats" after all:
http://projects.propublica.org/nyc-flood/
If your data is inherently 3 dimensional I'd say it is worth the effort to dive in, but the majority of visualizations that we do are charts and plots which don't really need to be 3D.
ftp://ftp2.census.gov/
My point being that the census data is independent of factfinder.
https://github.com/propublica/simple-tiles
Documentation here:
nasty: https://github.com/mirrors/gcc/blob/master/gcc/c-family/c-co...
nasty: https://github.com/mirrors/gcc/blob/master/gcc/c-family/c-le...
But you get the idea. I'm merely pointing out that compilers are tricky and complicated beasts. And especially in the rewriter CS has to jump through hoops to disambiguate.
EDIT: We haven't had any contact with Wolfram|Alpha but maybe we should reach out.
We've been using it pretty much daily for about 5 months now and cleaning messy government data used to be time consuming and destructive, with google Refine it's so easy and fast to join, cleanup and do rudimentary analysis on said data.
It especially shines when you have to merge many disparate data sets into one. My colleague, Dan Nguyen, did just that for our Dollars for Doctors app:
http://projects.propublica.org/docdollars/
and he scraped the data from reports like this:
http://www.pfizer.com/responsibility/working_with_hcp/paymen...
(one company even put the disclosures up as a flash movie).
Of course we could write scripts, use grep/awk/sed or import it into a database, but Refine is really it. I encourage you to give it a try if you have questionable data you'll need to clean.
http://www.propublica.org/nerds/item/the-rainbow-connection-...