Slashdot videos: Now with more Slashdot!

Lets hope that that gets funded, as I really have way too many passwords!

Source code for hardware and software is on github: https://github.com/limpkin/moo...

Thus making it a truly Open Source project.

Nitrox is used so that you can dive longer....

What about Circle of 6:

http://www.circleof6app.com/

http://appsagainstabuse.challengepost.com/submissions/4900-circle-of-6

Can we change that at first to just start with the very simple:

Organisations transferring IP packets should be kicked off the Internet if they do not implement BCP38.

That would make al kind of spoofed attacks already impossible, that being the DNS, NTP, Quake-alike and many many others...

But, as there is no money to be earned with this, ISPs do not enforce it.

(and yes, it does cost some cash to implement as not all routers support it unfortunately..... )

Instead of shoving a list of addresses into a DNS server (dnsmasq) in this case, it would be better to use RPZ (http://en.wikipedia.org/wiki/Response_policy_zone)....

Next to that:

> Open the file with sudo nano /etc/resolv.conf and replace the contents with the following:
> nameserver 192.168.42.49
> nameserver 8.8.8.8
> nameserver 4.4.4.4

192.168.42.49 = apparently the address of the fake webserver (would be great if they configured that somewhere before making test queries....)
8.8.8.8 = Google Public DNS, no ads maybe but running all your DNS queries through Google is not helping much now does it.
4.4.4.4 = is not a valid DNS server, likely they meant 8.8.4.4 which is the secondary Google Public DNS address.

If you have a DNSmasq anyway, just let it recurse and play caching resolver, much better idea.

> iface wlan0 inet static
> address 192.168.42.1
> netmask 255.255.255.0
> post-up ip addr add dev wlan0 192.168.42.49/24

One just has to wonder which IP the box will be using for outgoing queries, depends a lot on the kernel....
Now if that was 192.168.42.49/32 the .1 would always be chosen, but as a /24 magical things will happen

Etoomanypitholes and lots of people will be bitten.

Strange, this "article" does not even mention the official Tor Project Cloud effort: https://cloud.torproject.org/

From the github page: "Written by @hubert3 / . Presented at Blackhat USA July 2012, code published on Github 2012-08-31"

Slashdot, News of Last year, today! ;)

But yes, it is a rather cool hack that still works....

Related links for this article:
DTN Research Group: http://www.dtnrg.org/wiki
lots of docs: http://www.dtnrg.org/wiki/Docs
overview presentation: http://jeroen.massar.ch/presentations/files/CCC2007-DTN-Upgrading-Martian-Carrier-Pigeons.ppt

The book: http://www.amazon.com/dp/1596930632
Wikipedia: http://en.wikipedia.org/wiki/Delay-tolerant_networking

Source code: http://dtn.dsg.cs.tcd.ie/sft/ltplib/

Oh and yes, theoretically this extends the Internet in the same way that various other protocols do, eg 6lowpan etc.
And yes, as it is store-and-forward it looks an awful lot like SMTP.

Enjoy ;)

"The 1980's are calling for their foreign policy back" -- Barack Obama :)

There are actually only few out of the 30.000+ people who signed up with a proper essay, and the ones that did always earn quite a few extra credits for when they actually do write something more than just "I need IPv6".

If you where not able to get a SixXS account you likely just did not read the text on the signup page, most likely then proceeded by providing garbage details which is definitely not accepted and any such request simply gets rejected.

But if you are unable or willing to read the signup page, most likely you won't get IPv6 working either as you'll be doing all kinds of things that will break the configuration, thus reading is essential.

We (SixXS) have tried to make it as easy as possible by bringing AICCU into the world and working together with various vendors though so that they support IPv6 tunnels out of the box, but even then some problems need reading for a bit to get them resolved. Thus if you can't read at signup you likely won't pass for the rest either.

Indeed SixXS never required a LinkedIn/XING/etc account.

Those links where only requested at the time so that one would get extra credits (ISK) donated to the person when they signed up, they got the credits because they proved a little bit more that they where real (as we, that is SixXS, could check the trust-graph in those websites) and more importantly as the people who did that actually read the signup page, which is something a lot of people clearly do not do even with colorful indicators.

This solved a small catch-22 with people who got flashy new IPv6 enabled routers (read: AVM Fritz!Box at the time) and thus for whom a tunnel alone was not enough. As since the beginning of 2012 the new sixxsd v4 software was deployed, this was not needed anymore as one then automatically has a routed /64 next to the tunnel space.

It's good that Planetary Annihlation will have support for modding and Linux :)
So give them your voice and some of your cash by funding them on Kickstarter and then next year we'll all happily be destroying planets!

> Win7 requires me to kill ipv6, because there's no good way to tell the system to prefer ipv6.

If you have tunneled connectivity, thus non-native being announced on an Ethernet interface you will likely have to set in the registry:

SYSTEM\CurrentControlSet\services\Dnscache\Parameters\AddrConfigControl = 0 (DWORD)

That way AAAA lookups are always performed and also preferred. Though it still depends on the application if it actually uses getaddrinfo() at all and does not resort addresses itself, which some applications do and some others do not.

> Let me easily set priority of v4 vs. v6.

With Lion Apple has implemented a variant (quite unrelated to the IETF drafts) of Happy Eyeballs in their systems. As such, depending on previous connection history, latency and other factors you might get IPv4 or IPv6 connections at random. And nope, there is no knob at all to turn off that behavior. Right back at you.

(oh and yes, I have a Mac too, which is why it kinda annoys me, but if you just slow down IPv4 a bit on the outbound router you always get IPv6 as the Mac thinks that IPv4 is "slower" than IPv6... still a knob would be useful, yes, bug reported a long time ago)