proctor

I help to maintain a page[0] that keeps a current list of the more powerful wireless routers that support OpenWRT and DD-WRT. This arstechnica article is about wired routers (they say an article on wireless versions will be arriving soon) but maybe it is still helpful.

[0]http://rooftopbazaar.com/routerfirmware/

I help maintain a page[0] that keeps a list of the best performing routers that support OpenWRT and DD-WRT. It allows to sort by Value, Performance or Price.

[0] http://rooftopbazaar.com/routerfirmware/

there is a page[0] that I helped put together that maintains a list of the current more powerful routers that support OpenWrt and DD-WRT. Sort by Performance, Value, or Price. Criteria for getting on the list is Performance first, and then Value.

[0] http://rooftopbazaar.com/routerfirmware/

I haven't done so personally, but they have 86-64 builds yes. http://www.instructables.com/id/Openwrt-on-a-pc/

I helped make a list[0] (which is still kept current) of OpenWrt and dd-wrt hardware a while back. You might want to give OpenWrt another chance, it may not be as outdated as it might seem.

[0]http://rooftopbazaar.com/routerfirmware/

i've found that pv is useful for this purpose. however i've never been quite clear on what the best way to use bs with pv is. is it

  dd if=/dev/sda bs=1M | pv > sda.file

or is this better

  dd if=/dev/sda bs=1M | pv | dd of=sda.file bs=1M

I find openWRT is a really useful firmware project and I use it in any situation where it is feasible. Bandwidth Throttling / QOS is often in demand. Wireless Bridging works well. A nice side effect of using openWRT is that you sidestep many of the "backdoors" that sometimes appear (intentionally or otherwise) in stock firmware. I also helped create a page that can help find the current most powerful routers that support WRT: http://rooftopbazaar.com/routerfirmware/

this page has a good overview of current routers with support for openwrt and dd-wrt http://rooftopbazaar.com/routerfirmware/

could it be "Thinking, Fast and Slow" by Daniel Kahneman? https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow

i think there are two concerns here. one is that the source is not tainted by a third party during or before the download. the second (arguably much more important in this case) concern is that the compiled binary matches the source. the second concern is addressed well by the author as far as i can tell, but i think that there is room for improvement in their concerns about the former. i assume they have thought about this and do have at least some concerns because it is mentioned that

  The PGP signature of the binary can be downloaded 
  through the button PGP Signature, which makes you 
  download TrueCrypt Setup 7.1a.exe.sig over HTTPS 
  (*although with the NSA in the middle, it might not 
  mean much*).

[emphasis mine]

cross-referencing the pgp signature with at least one other (public) source would go a long way toward allaying those concerns (that the HTTPS might not mean much).

this criticism is in no way meant to detract from the rest of the work, and i mean only to refer to pgp sig verification best practices here.

it seems to me that the relaxed gpg key verification that the author uses doesn't give us any more assurances regarding the authenticity of the source than a simple hash offered on the website would. i think in this situation, if the author did not intend to attempt more rigorous verification of the truecrypt pgp key, at least cross-checking that the key offered on the site matches the key offered on a public key server pgp.mit.edu for example would be prudent before signing the truecrypt key with your own.

  Import the .asc file in the keyring (File > Import certificates).
  Now you should mark the key as trusted: right click on the TrueCrypt Foundation public key 
  in the list under Imported Certificate tab > Change Owner Trust, and set it as I believe checks are casual.
  You should also generate your own key pair to sign this key in order to show you really trust 
  it and get a nice confirmation when verifying the binary.