HNHacker News
TopNewBestAskShowJobs

petejansson

96 karma · joined September 15, 2011

Currently doing information security consulting.
submissionscomments
petejansson··on New Year's Resolutions for SysAdmins
On nslookup, in particular, the program has some ambiguous behavior and can be problematic when trying to debug certain DNS issues. Dig was developed to be a reliable replacement that has predictable behavior at all times. There is a companion to dig called "host" that is a simple lookup, including looking up in-addr.arpa entries ("host 8.8.8.8"). In most cases, you will get more consistent results by using dig and host, which is why nslookup is deprecated.
petejansson··on CSS animated loading indicators
These are really very nice, but they don't really convey any more information than a static picture of a puzzled kitten. Like "security theater," this is "progress theater" and I would prefer to give my users a more useful indication of progress. I do appreciate the work that went into these, and admire the skill.
petejansson··on New TLDs have arrived
Not registrars. The delegation of new gTLDs into the root is the culmination of the first round of new gTLD expansion, an ICANN project that has been going on for quite some time, and has an extensive evaluation process -- see http://newgtlds.icann.org for lots of information on the process. It's likely that there will be a subsequent round at some point in the future. Meanwhile, there are a large number of new gTLDs that are being delegated into the root over the next few months. Soon, gTLDs will outnumber ccTLDs.
petejansson··on New TLDs have arrived
All new gTLDs are required to offer a sunrise period during which rights holders can register names corresponding to their marks. (Mostly trademark holders, but other rights may be recognized at the discretion of the registry.) During sunrise, names are not generally available, so registrar guarantees of pre-registration before sunrise should be carefully examined. If there is contention during sunrise registrations, registries generally will have a way to work it out, with auction being a frequent mechanism. Because of the extra mechanisms associated with operating the sunrise period, many registries and registrars may impose additional fees during sunrise. (As a registrant, you'll only see fees from the registrar.)

URGENT public service announcement: Many of the new gTLD registries will use the Trademark Clearinghouse (http://trademark-clearinghouse.com/) to determine who owns what rights. If you have a trademark, it's really in your interests to register it there, as it will be available to all the new gTLD registries. If you look at the new gTLD rules, it's important to register your marks before expiration of the sunrise for the first new gTLD to go live.

petejansson··on End the N.S.A. Dragnet, Now
What this editorial gets right is that the oversight regime for domestic surveillance is inadequate. What it misses, however, is that big piles of data are inevitable with the current trajectory of technology. It will not be possible to have the piles of data not collected. As others have written, the government surveillance agencies essentially saw what private industry was doing and said "I want a copy of that."

I think we need to rethink some things:

1. In the short term, one of the biggest changes that has to be addressed is the current court doctrine that privacy has not been violated if no people are actually looking at the data. Given that much of the surveillance is directed by automation, we need to recast that doctrine to include some of the automated analysis of the data. It's a thorny question, and one that will take some time and effort to get right, but there's no time like now to start.

2. We need more forceful and more transparent oversight of surveillance. There is a risk that the surveilled might change their tactics based on lessons from oversight reporting, but it seems clear at this point that the trade off is necessary. To quote the editorial: "The usefulness of the bulk collection program has been greatly exaggerated. We have yet to see any proof that it provides real, unique value in protecting national security." Trade-offs are only worth making if you get something. Time to revisit the trade-off.

3. We need to address both the big piles of data in the government's hands and those in private hands. This is going to require rethinking ownership of the data, and probably moving the US more towards an EU-style privacy directive. Again, a longer process, but one that needs to start now.

4. As a country, we need to start toward a more rational view of terrorism risk. Plenty has been written about how disproportional our response has been. Time to rebalance the scales.

In the end, we're going to continue to have big piles of surveillance data as long as we continue our technology trajectory. We need to start figuring out how to work with it, rather than try to stop it.

petejansson··on Half an operating system: The triumph and tragedy of OS/2
About 1985 IBM had a product called TopView that ran a multitasking supervisor on top of DOS and could do real multitasking with the right disk drivers. No protected memory though. TopView was really memory heavy, though -- you gave up at least 160KB just with TopView. Two guys created a TopView clone called Mondrian that ran in just 40K, and ran much faster. Those two guys were Nathan and Cameron Myhrvold. Mondrian was sold to Microsoft and those two guys went with it. Mondrian was a really clever engineering feat.
petejansson··on Amazon's short URL: http://a.co
You're right -- dk. has an A record. It's coming from the dk name servers, though, not from the root zone. (I should have run the query the first time.) You're also absolutely correct that dk and www.dk resolve to different IP addresses. So the root name servers are returning a redirect to the dk name servers, which are providing an A record. (You can see it with "dig +trace dk.") The dk name servers can return whatever they want. I believe the behavior is undefined, though -- where a zone and a parent zone have records in common, they should be consistent. So you may get different behavior from different resolver implementations. (This may help to explain why some people see something at http://dk and some don't.)
petejansson··on Amazon's short URL: http://a.co
The browser is automatically putting "www." in front of "dk" allowing it to resolve. Although the root DNS zone (the implied dot at the end of DNS names) can have A records in it, the current policy only allows A records for (some) nameservers. As a result, the new gTLD program, for example, does not currently allow "bareword domains" because you can't put an A record for the domain by itself in the root zone. (The policy doesn't allow an MX record, either, so email to someone@shop wouldn't be possible without a policy change.) The policy is aimed at keeping the root zone simple, and minimizing the volume of changes.
petejansson··on TSA Accepting Public Comments On Whole Body Airport Screening
At first I thought my opt-out would be recorded, but most of the airports through which I've flown do not record anything about the opt-out. They just pat down the subject and try to keep the lines moving. I no longer believe this is an effective way of registering my opinion.
petejansson··on How I spend my first 5 minutes on a server
Keys can be brute-forced.
petejansson··on Amazon EC2 currently down. Affecting Heroku, Reddit, Others
The reference architectures and white papers here are helpful: http://aws.amazon.com/architecture/
petejansson··on 37signals doesn’t like you sorting stuff. Are you just remaking a spreadsheet?
It's a really good idea to question the fundamentals of presentation. People, however, are really good at looking at tables and detecting patterns (at least, according to Tufte), and, since we're unlikely to anticipate all the ways people will use data, it's a good idea to make sure that, in addition to the good ideas we come up with, we give users options to muck with data to their heart's content.
petejansson··on Mozilla's secure coding guidelines for web developers
https://www.owasp.org/index.php/Category:OWASP_Guide_Project

I was actually wondering how the Mozilla guidance is different.

← PreviousPage 2 of 2