tag:blogger.com,1999:blog-34051337.post4992775308541675395..comments2023-08-23T06:16:10.566-06:00Comments on Fix Log: Recovering (or stealing) a domain registrationUnknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-34051337.post-4548938611869611932008-12-17T07:10:00.000-07:002008-12-17T07:10:00.000-07:00Dear sir,how can you register a emailadress ending...Dear sir,<BR/><BR/>how can you register a emailadress ending with @bigsky.net (or lalalala.com) if you are not the owner of www.bigsky.net?<BR/><BR/>please reply at tomasvandalen@hotmail.com if you would.<BR/><BR/>Thank you in advanceAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-34051337.post-77545670357338851812007-02-28T21:58:00.000-07:002007-02-28T21:58:00.000-07:00Guess what technique I just used :)I was moving [c...Guess what technique I just used :)<BR/><BR/>I was moving [censored].com, [censored].com, and [redacted].com over to my system (they didn't want to stay at ICS now that Blackfoot owns them), and the admin contact on the first two was [censored]@msn.com - an address that [censored] hasn't had in three<BR/>years. Blackfoot didn't have the login info on file, and wanted us to<BR/>fax a bunch of Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-34051337.post-82431428310470444622007-02-23T04:53:00.000-07:002007-02-23T04:53:00.000-07:00I think the rationale of full disclosure is much w...I think the rationale of full disclosure is much weaker here than it is on the cases discussed by Schneier. There the security lapse is in the hands of a single company, and that company has (or should have) people who are expert in the area and work full-time in that area. Public disclosure forces them to fix it, and that fixes it (for those users who install the patches). Here, the lapse is in Anonymousnoreply@blogger.com