PRESIDENT BUSH: ... I mean, there's a lot we can do together and achieve the objective, which a lot of people want, which is the reduction of greenhouse gases, and at the same time, have viable economic growth.

TONIGHT: And because, sir, America remains the biggest polluter.

PRESIDENT BUSH: America is the largest investor in the technologies necessary to be able to say to people, 'You can grow your economy so people's standard of living can improve, and at the same time be good stewards of the environment'.

TONIGHT: But pollution in this country has increased amazingly since 1992.

PRESIDENT BUSH: That is a totally inaccurate statement.

TONIGHT: It's a UN figure.

PRESIDENT BUSH: Well, I just beg to differ with every figure you've got. The environment has - the quality of the environment has improved, in spite of the fact that we've grown our economy.

Excellent interview of Bush on a variety of topics. Lots of the same old same old on Iraq: "I never had doubts" blah blah lbah. I wonder how many sons and daughters of the US have to die before doubts do begin.

His position in farm subsidies surprised me, especially after his stand on Steel tariffs.

I was most interested in his energy policy. My favorite quote?

BUSH: I believe we're going to be able to have coal-fired plants that have zero emissions.

[waits for Janelane, resident energy chick...]

UK Bush Interview: Enviroment, Trade, Africa, Iraq

The NISR team have produced a variety of detailed papers exploring technical skills development and threat dissection. These papers are provided free of charge as an addendum to our other published materials.

Mainly Application layer stuff. Some good papers, especially the Best Practices papers. I find some many banks and commerce sites that don't properly lay out their site, allowing for easy exploitation.

NGS Research: Whitepapers

Ran across this today. Its a website that has old Soviet archives, photos, and reports about WWII from the Eastern front. Most of what we know about the Eastern Front comes from German records, as the Russians didn't want to give any intelligence about their milirary strengths, etc, to the Allies.

Cool stuff

Our Victory Day by Day

URLParser is a Java class to parse out the different fields of a URL. The parser included in Java's URL class is painfully bad. Not only does it not allow access to all the different URL fields, but does not return the proper information for getPath() or getFile()!
URLParser allows access to the following fields:

* Protocol
* Username
* Password
* Hostname
* Port number
* Path
* Filename
* Query String
* Fragment

Here is a screen shot showing the differences between Java's parser and mine.

Most Significat Bit Labs :: URLParser

Table giving the average cost of a 2200 ft^2 4 bedrrom 2.5 bath house with a 2 card garage.

US Average is: $354,000
Atlanta average is: $283,090

Most expensive housing markets

Having spent a good 1/2 hour reading this, I am not convinced we need it. The basic idea is we need a single place to put domain names for all these VoIP and other communications devices.

I'm more interested in allocation of address space to these devices instead of domain names. These devices *must* have globally unique addresses. CIDR, NAT and other technologies that have slowed the consumption of IPv4 address won't help you here.

.tel sTLD RFP Application

RFC 1738, 1808, 2396... FUCK!

The wording about what are valid or reserved characters in various parts of the URL contradicts itself multiple times across RFCs.

Do you have any idea how complex the grammar is to parse a URL?

[proto]:[maybe //][user]:[maybe pass but only if user is there][@ and remember empty user,pass is different than no user pass][host]:[maybe port who the hell knows]/[path which can have all sorts of fucked up characters]/[file, or maybe they are just screwing with you]?[doesn't have to have anything even with a ?, regardless these can be completely different reserved characters than those reserved in the path!]#[maybe nothing, maybe something]

That man is a sadist! From RFC1738:

For resiliency, programs interpreting URLs should treat upper case letters as equivalent to lower case in scheme names (e.g., allow "HTTP" as well as "http").

Yep, schemes are case insensitive, so are hostnames. Then he throws a curveball, because path names are case sensitive (because, as TBL reasons some schemes translate that to a file heirarchy). query strings? Well hell, those can be case insensitive. Can be? WTF is can be? Who would ever want to code an application with case sensitive searches hmmmmmm?

Of course, it never says that # isn't a valid path character. But it is!

I've got a state machine with 6 states, and that just gets me to the path!

[grinds teeth].... happythoughtshappythoughtshappythoughts

Giant CSV file of 55000+ IP ranges and the countries that control them.

The IP-to-Country Handbook

I talked to Dolemite today and will be speaking at Phreaknic 9. I won't tell you the topic just yet, but it involves live demos against:

-A well known news agency
-A national bank
-A major search engine
-A goverment website
-Several commerce companies

As well a code launch. And no, I won't be violating any (US) laws.

I just wanted to say that I passed my second qualification exam (oral exam) on Tuesday, and am now officially a PhD candidate. Yay!

So we're partying this weekend or what?

w00t!