Slashdot Mirror
OpenBSD 3.0 Honeypot Whitepaper
Tortured Potato writes "This white paper, by Michael Anuzis, details how he set up an OpenBSD 3.0 honeypot, watched it get cracked and then analyzed it -- all within 28 hours. Fascinating stuff...this is the first OpenBSD honeypot I've heard of."
Honey and pot... a perfect combination!
I can't believe I stooped to a fp!
I hope that's love-honey.
Surprised by Unicide! (fuck this shit)
OPEN SOURCE MISCONCEPTIONS
By Serial Troller
Myth: Open Source is written by heterosexuals.
Fact: All Open Source development is done by raging homosexuals. The more flaming examples include Anal Cox, Linus Turdballs, Eric Ass-Reaming Raymond, and the entire Slashdot crew. The ringleader of the slashdotters, a man named CmdrTaco, engages in a practice known as Taco-snotting, along with his faggot-buddies Jeff Homos Bates and CowBoiKneel.
Myth: Open Source is written for heterosexuals.
Fact: Using Open Source software can cause suppressed homosexual fantasies to surface, leading to all out flaming faggotry within 6-8 weeks. Anecdotes of otherwise hetero men turning queer are far too numerous to count, but a few examples stand out. In one case, a man was arrested loitering outside an elementary school and making sexual overtures to several children: he quickly confessed that shortly after installing the Mozilla browser on his computer, he began to have uncontrollable urges to, to put it simply, have his cock sucked off by little boys. He soon met several other like-minded men through discussions on the Bugger Zilla mailing list (all already homosexuals), who together kidnapped a total of seven children whom they brought back to their apartment and sodomized. The other two men are still at large and believed to still be using Mozilla.
Myth: Open Source is multicultural.
Fact: Open Source is openly racist.
Myth: Open Source is democratic.
Fact: Open Source is controlled by a few narrow-minded zealots (mentioned throughout this post), most of whom are either Communists, Stalinists, Nazis, or Fascists. Additionally, Open Source supports terrorism.
Myth: Open Source is tolerant of religious preferences.
Fact: Open Source developers regularly engage in holy wars over the superiority of various Open Source projects, such as the Emacs program (preferred by Christians) versus vi (used mostly by neo-pagans and Satanists); or the KDE desktop (a favorite among Muslims) versus the GNOME project (particularly favored by Jews). Posts initiating crusades or jihads against other developers can be found regularly throughout the newsgroups and mailing lists.
Myth: Open Source is tolerant of sexual preference.
Fact: See above. Either you are a homo, you become a homo, or you never visit Richard Stallman alone in his office and hope to God you never meet him on the street at night.
Myth: Open Source is tolerant of political differences.
Fact: Open Source is an anarcho-communist philosophy bent on the destruction of capitalism. The very same Richard Stallman, a man whose name is disturbingly reminiscent of Stalin, has stated several times in public that his vision includes the subjugation of all who own intellectual properties under the jackboot of the GPL. The GPL is a pernicious piece of literature lifted straight from Karl Marxs Communist Manifesto, and is fortunately banned in many democratic nations.
* * * * * UPDATE * * * * *
Myth: Open Source programming is a harlmess, healthy activity.
Fact: Open Source programming has been known to lead to massive obesity, violent tendencies with an obsession with handguns, paranoid-delusional ranting, and in severe cases, complete insanity. If anyone you know is thinking about going Open Source, stop them before its too late!
* * * * * UPDATE * * * * *
____________________
2002 Serial Troller. Permission to reproduce this document is granted provided that you send all the bukkake porn you can find to serialtroller@hotmail.com.
- poopbot: for all your crapflooding needs
Of just how much you need a firewall these days.
Especially if you run windows.
Michael
There is no cryptographic solution to the problem where the intended receiver and the attacker are the same entity.
Oooh, dems fightin' words! (runs into the General Store and closes the curtains, peeking out)
Vintage computer games and RPG books available. Email me if you're interested.
I think I'm not the only one who's reading this article and asking himself what a honeypot is. Could anyone please explain what it is? Thank you in advance.
http://www.google.ca/search?q=cache:b3jn4bU41cYC:w ww.omegapunx.org/+muffinface+band&hl=en&ie=UTF -8
This is not possible we all know that oBSD can't be hacked, only redhat Linux and Windows.
This white paper, by Michael Anuzis, details how he set up an OpenBSD 3.0 honeypot, watched it get cracked and then analyzed it -- all within 28 hours
You can do it with a default install in 30 minutes.
Windows doesn't come with shitty, insecure services like Apache2 and OpenSSH.
Surprised by Unicide! (fuck this shit)
Jessica Alba
Natalie Portman
Jessica Alba
Natalie Portman
Jessica Alba
Natalie Portman
The Harken Tale: Harken Energy purchased Bushboy's worthless oil company Spectrum7 for $2 million (bailing Bushboy out of big debts) in the late 80s and put Bushboy on their board and paid him a $120,000/year "consulting fee." Harken then lent Bushboy $180,000 so he could buy Harken stock. Bushboy was on their Board and was a member of their 3 man "Audit group" which was privy to the companies financial woes in 1990. After being briefed about Harken's cash flow problems in April, 1990, Bushboy sells his stock in June, 1990, when some mystery investor pays him $848,000 based on a "cold call" made by some stock broker (this is what the Bushboy people really say). In August, 1990 the poor financial condition of Harken becomes known and the stock drops like a rock to 1/4 its value when Bushboy sold it. Bushboy fails to report the sale of the stock by the 10th day of the month following the sale as required by law. He doesn't file the necessary SEC documents until 36 weeks later! The SEC head was appointed by Bushdaddy who is now president. Although the head of the SEC, Mr. Doty, was Bushboy's personal attorney, he doesn't recuse himself from any judgement of Bushboy and although the SEC refuses to exonerate Bushboy's criminal conduct it chooses not to investigate or prosecute (surprise!). The whole Bushboy/Harken deal stinks to high heaven and makes Whitewater seem like the jaywalking that it was in comparison, but Bushboy and the GOPers will block any attempt to investigate and hire a Special Prosecutor as they were so quick to do in Whitewater. Harken will be Whitewashed, as is everything else in Bushboy's sleazy past.
see also: komanduh tahoe's NEXT employer
Which is not very surprising for an OS that has had "One remote hole in the default install, in nearly 6 years!". An interesting read 'though.
By the way, there is a slashbox for OpenBSD Journal, which can be enabled here. It featured this story yesterday.
karma capped
If anyones interested, the website for the 'hacker' is omegapunx.org, his msn name is omegakidd@hotmail.com
E-Mail: omegakidd@tfz.net
E-Mail2: omegakidd@cheguevara.zzn.com
aim: eromlenosam
aim2: shoogy maple
aim3: satan the killer
msn: omegakidd@hotmail.com
yahoo: omegakidd
irc@efnet: omegakidd
Why the consistent use of "he/she"? I'm sorry but I've yet to see anyone of the female persuasion who is enough of a lowlife to become a script kiddie.
I took a honetpot to Prom, and it took me 28 hours to crack her and analyze it too....
Muffinface Google search
obligatory link to omegapunx's google-cached website is here
the best entry is certainly May 31st, when this gem appeared:
It seems to me that the Americans are actually the terrorists. I would elaborate right now but I am too lazy to type that much right now.
9:30PM: I had some fun with smoke bombs. I lit like 5 in my back yard and there was this pretty big smoke could going into my front yard. Sense it looked so cool I searched for some more smoke bombs, and all I could find was like 3. But then I lit them in the feild and that was cool. There was this cloud of blue smoke like 4 and a half feet from the ground. It was soo cool.
-- "Ignorance more frequently begets confidence than does knowledge." (Charles Darwin)
"its a reminder or just how much you need a firewall these days" and left it at that.
My brother's girlfriend Danyel gave me this purply long skirt thingy. It is soo cool. I would wear it to school tommorow, but there are these kids in the loccer room who hate gay people. They say things like "Man, if you are gay I am going to kick your ass." And stuff like that. So, they would probably think I am gay or something and kick my ass. Welp, what are you going to do in this world these days.
Well, there isn't really such a thing like a secure system.
So all this pro-OpenBSD propaganda by Theo de Rat saying "OpenBSD is secure, really, always" is rather a bad thing. I lulls sysadms into the belief that their system is save, making them unaware of the fact that a system is never secure at all.
Of course, the sources of every OS should be explicitly checked for security holes. But this shouldn't be the single feature of an OS. In fact claiming an OS "secure" just due to these checks is serving security rather badly.
I sometimes wonder if the OpenBSD project hasn't excatly the opposite effects than intended by it's maintainers for these very reasons. On the other hand there are some cynical commentators out there, who claim that the main intend of OpenBSD is to boost Theo's ego.
Owner of a Mensa membership card.
This makes me wonder what's the proportion of cracked to uncracked machines. I know I've had a box cracked from underneath me and I've found a set of other cracked boxes, but I wonder how many I've missed. Granted, I probably wouldn't have missed MuffinFace and his posse, but man.
I think it may be time to knuckle down and write a *good* set of iptable rules instead of the wacky mash I've got now.
Why is it that BSD users always feel the need to knock Linux? This article kicks off with "Most honeypots out there tend to be Redhat Linux as it's has the worst record for security out of pretty much every OS out there". RH is pretty damn secure compared with Windows, which seems to have a major security alert almost every day.
HH
After Theo lost his precious "no remote hole" boast he has started up another project named SecureBSD.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
I think you are greatly mistaken. There is no need to chose. Have both! Set up a nice threesome, between miss Portman, and miss Alba.
Or aren't you man enough to keep up with 2 hot young babes? (I don't know who Jessica Alba is, but I assume she is young and hot).
Signing out,
--wonder-boy, technoslut.
(Yeah, I am probably bi-sexual or something, but I think that is sufficient to be a slashdot gay boy. Well, I hope it is. Where else can I get daily gay porn??)
Do you have an I?. Then we can all be leet haxors and see if we can break into his box. My bet is that there is at least someone on slashdot that could break in(I am pretty darn sure there are quite a large number of highly skilled black hats that read slashdot.).
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
Registrant:
OmegaPunx
5233 Welcome Ave N.
Crystal, Minnesota 55429
US
Registrar: Dotster (http://www.dotster.com)
Domain Name: OMEGAPUNX.ORG
Created on: 03-MAY-02
Expires on: 03-MAY-03
Last Updated on: 03-MAY-02
Administrative, Technical Contact:
Elmore, Mason omegakidd@tfz.net
OmegaPunx
5233 Welcome Ave N.
Crystal, Minnesota 55429
US
(763)531-0637
I tried calling the number, but no one answered (at 9:30AM EST) let me know if
Title: "OpenBSD 3.0 Honeypot Whitepaper"
What's a white paper? In this case it isn't paper.
Are there other colors? Could he have written a gray paper? Why not go all the way and call it a purple paper?
This article is valuable not so much for how to set up a honeypot (and no doubt this discussion will ventilate that issue) but, to a security newbie (me), it shows how the analysis of the logs proceeded.
Nice one. One question though - why not publish the IP of the hackers? Why protect their anonymity?
Backward%20compatibility%20is%20over-rated
"It is not the job of Linux advocates to promote BSD" when the topic was Open Source, what makes YOU think a BSD advocate should spend any time defending GNU/Linux?
You are seeing the reaping of what 'the leaders of Linux' sow.
Comment removed based on user account deletion
I thought this had something to do with Winnie the Pooh using BSD. Oh well.
He's a Windows honeypot, in case anyone wants to practice (note: please be nice, you are beign watched :)
200.49.83.130
Well for one thing the IP may be dynamic. Some other person may have been assigned that IP. Another thing is that they might have been working from a compromised system (though I doubt that in this case.)
In any case the anonymity of at least one of them was not really too well protected as several of the posts above indicate.
From the article:
Firstly, assuming they used a tool like "nmap" to do the portscan they would already know that some of the ports are forwarded - nmap states which ones are in the results of the scan (I believe it can tell by the differences in TCP sequence numbers.)
Secondly, why would this detract from the realism of the situation? Not everyone who wants to provide limited services on the internet buys additional IPs. I know I don't have the money to!
Julian
A quick serach for the band NAME "Muffinface"in the article and viola
:-)
Please be gentle
Friday May 10th, 2002
At this moment I am uploading all of my music to this comp so it can go on this web page. Tommorow the band that I am in, Muffinface, will be playing at my friends house. So that is cool. That is all for today. Oh yeah, and also for the music. If you want ftp access, when it is up. The username and password will be music. And the FTP is just omegapunx.org port 21.
Now, how secure is this network? You've got a firewall, so you're secure, right? Just two minor little flaws: the security holes mentioned in the article are in Apache and SSH. Your firewall didn't add any security at all! You're just as exposed as the next guy with no firewall.
Sticking a firewall in front of your network and thinking you're secure can be very dangerous, if it lulls you into thinking that the machines behind the firewall are now secure. Most exploitable holes are not on the thousands of unused ports that a firewall blocks - they're on the ports that the firewall lets through.
I should mention that with a stateful firewall, you can get greater security, since it monitors the actual content of the connection and may be able to detect hack attempts. However, stateful firewalls tend to be more expensive, less transparent (require more maintenance), and if they're commercial, more expensive. And many hacks can't even be detected by a stateful firewall, and there are all sorts of tunneling tricks that can be used to circumvent this kind of security. Ultimately, the only way to be secure is to make sure that every box that can be accessed from the outside is completely secure.
Along those lines, one of my favorite firewall-related quotes came from a sysadmin whose mail server and entire internal 70-station LAN had been infected by NIMDA: "But we have a firewall! How did it get through??"My brother's girlfriend Danyel gave me this purply long skirt thingy. It is soo cool. I would wear it to school tommorow, but there are these kids in the loccer room who hate gay people.
This guy has a lot going for him. He can crack any kid's computer that tried to beat him up.
For some interesting reading related to this article, take a look at the text files that come with the exploit that was used to crack this honeypot.
> Most honeypots out there tend to be Redhat Linux as it's has the worst record for security out of pretty much every OS out there, and so it makes for a good honeypot since the goal is to get hacked.
Obviously, he's never heard of Windows.
this is getting old and so are you
blog
Contact
e-mail: omegakidd@tfz.net
e-mail2: omegakidd@cheguevara.zzn.com
e-mail3: omegakidd@omegapunx.org - Not sure if working
aim: eromlenosam
aim2: shoogy maple
aim3: satan the killer
msn: omegakidd@hotmail.com
yahoo: omegakidd
irc@efnet: omegakidd in #omegapunx
Elmore, Mason omegakidd@tfz.net
OmegaPunx
5233 Welcome Ave N.
Crystal, Minnesota 55429
US
(763)531-0637
Have fun people!
Link to newsgroups provides clues of information sources used by this script kiddy. No direct references to this exploit though.
Wow... most of us feel good about getting a story we've written posted on Slashdot. You got a story written about you! Kudos man... now if only it wasn't a story about something you did that was incredibly stupid!
SIG: HUP
28 hours without a hole!
Ok, so we have info on "Hacker 1" but what about his litte friend "Hacker 2"? Who is he? Maybe omegakidd can help us out with that one...
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is mortally sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
1"M GL4D TH1$ GUY H4$ TH3 GUT$ 2 C4LL MY FR13NDZ ''HACKER'', 1N$T34D 0F TH4T ST00P1D ''SCRIPT KIDDIE'' N4M3 WH1CH 1 N3V3R L1K3D. W3 R H4CK3RZ!!!!!11
1T"S L0N6 P4$T T1M3 W3 G0T TH3 R3$P3CT W3 D3$RV3!!!!!!!!!11
:WQ
------ ------ ------
ALL HA1L B1FF, TH3 M05T 31337 D00D!!!!!1
------ ------ -
Clothing doesn't make people gay. Try reading this book and see if you look at the world in the same way ever again.
~~~LXT~~~
Life is like a computer program: anything that can't happen, will.
...that BSD is dying. It can't even keep up with today's script kiddies. So sad.
I've got a dollar bill with www.omegapunx.org written on it. Do I win something?
First, my apologies to the Honeynet Project (http://project.honeynet.org), the Distibuted Honeypot Project (http://www.lucidic.net), and everyone else who does research in the field of honeynets for releasing a paper which revealed the identity of the hackers involves, as this clearly doesn't fall into the scope of releasing a good whitepaper on the topic. Second, my sincerest apologies to the two hackers who compromised my honeypot. I went through and tried to conceal the identity of the two hackers involved, but it's true I knew they could still be traced by searching google's cache for pretty much any sentence on the cached page I displayed. I had no intention of revealing their identities, and it's clear I thoroughly overestimated the level of maturity of my target audience. To be completely honest, I would rather have never had this article featured on deadly.org and /. if I had known ahead of time how badly the two hackers personal information would be exploited.
To those people who read this, please stop bugging the hackers involved. They appear to be nothing more than innocent (and slightly unwise) kids. Let's grow up for a minute here for their sake.
It can't be all bad, because after all they did hack a honeypot... so I guess there's a moral to be learned with this story, but please don't take their humiliation any farther than it's already gone.
I'm honored my whitepaper was featured on these great websites, and I hate to feel like I'm crashing the party... but I can't help but feel bad for the poor hackers involved.
With utmost sincerity, Michael Anuzis
Note that this user has only posted one message, and has no information linking them to the actual author of the article. The legitimacy of the message should be IN QUESTION.
(Off topic: How did this posting get +1 without any other comments to get karma from?)
TANSTAAFI: There Ain't No Such Thing As A Free iPod.
http://www.omegapunx.org/pics/me/Pict0003.JPG
The purpose of a honeypot is to get knowledge from the hacker. In this case, I think the sysadmin should pay the hacker for the knowledge gained.
As of the 13th of July, our script kid friend wants to hide his screenshots section for some reason.
Too bad Google has it cached.
War crimes, torture, lies, illegal spying... Would someone give Bush a blowjob, already, so he can be impeached?
It hurts and stuff.
*BSD is dead
Time for a reminder that BSD is dead:
BSD is dead and has been for a long time.
Join us again at 3:58 for another reminder. Coming up next: traffic and weather together.
For those interested the site the whitepaper was on has been temporarily disabled by the web hosting company due to too much traffic.
Another copy of the whitepaper is available at:
http://www.anuzisnetworking.com/whitepapers/
And to verify, yes it was in fact me who posted the above apology. --Michael Anuzis
Just an interesting note that the whitepaper in question has been removed from the web site. Started reading it yesterday and was unable to finish reading it. Slashdot effect? Anyone have it saved, could ya send it to me at robert.fleming@rogers.com
Time for another reminder that BSD is dead:
BSD has more holes than Swiss cheese! No wonder it can't be used in any type of business environment.
Coming up next, traffic and weather together.
I'm sorry I have to tell you this, but I think it's dead ma'am.
Time of death: 5 years ago.