Live data from Hacker News

Master Foo and the Script Kiddie (2003)

soda.privatevoid.net

11–20 of 44 posts

Re: Master Foo and the Script Kiddie (2003)

#11
post #7
post #5

Earlier quoted context omitted.

The whole story, or the 3x7r3m3 13375p34k 0f 7h3 5k1dd13?

The whole story, the vibe of the story, the moral of the story, the use of the word "crack"; it comes off pungently as if written by a professional Unix systems administrator.

The moral of the story is not about cracking or getting arrested. It is a metaphor for the danger of taking shortcuts, just like certain other shortcuts in programming that are currently popular and also come with their own version of 1337 language.

And about the tools that enable ScriptKiddies or their modern equivalents to achieve some fast results, for which they have to pay later.

Re: Master Foo and the Script Kiddie (2003)

#12
post #7
post #5

Earlier quoted context omitted.

The whole story, or the 3x7r3m3 13375p34k 0f 7h3 5k1dd13?

The whole story, the vibe of the story, the moral of the story, the use of the word "crack"; it comes off pungently as if written by a professional Unix systems administrator.

As a former UNIX administrator (now cloud/devops/SRE/whatever), I can attest that when seasoned professionals are tasked to maintain systems that often run critical code (for finance, government, healthcare, etc) where we are often at the mercy of other groups (accountants, management, etc) treating us like a "cost centre" where proper investment can be hard will result in a very jaded and cynical outlook.

This is as much a defence mechanism as it is a calling card.

Re: Master Foo and the Script Kiddie (2003)

#14
The day after the stranger from Woot departed once more, a new student approached Master Foo as he was pruning the plum trees.

“I have heard of your reputation,” the student said, bowing low. “They say you teach the Way of Unix, not for power, but for understanding. May I learn at your feet?”

Master Foo nodded. “What is it you seek?”

“I wish to master the system,” the student said, “to understand every process, every socket, every thread of the great Net. I seek elegance, not exploits.”

“You speak wisely,” said Master Foo. Then he scribbled an IP address on a small bamboo slip. “Crack this machine. Its defenses are trivial. Return and tell me what you learn.”

The student departed.

The next morning, he returned, his robes slightly rumpled but his eyes alight with triumph.

“Master,” he said, “the machine was a decoy for an abandoned cryptocurrency exchange node. I rewrote a dormant smart contract and siphoned off forgotten tokens. The wallet had a bug, my code fixed it. I now possess wealth beyond imagining.”

“You have reported this to the rightful owners?” asked Master Foo.

“There are none,” said the student. “The domain expired, the company dissolved, and the blockchain is immutable. I wrote no logs, touched no traceable endpoints, and masked every call behind a thousand proxies. I am free and unseen.”

“Then you are a thief,” said Master Foo.

“I am not caught,” replied the student. “What I took, no one missed. What I altered, no one saw. And what I gained, no one can take from me.”

Master Foo was silent for a time.

At last, he said, “The first student broke the law and found caution. You have broken nothing and found profit.”

He bowed low to the student.

“Here,” said Master Foo, “is the end of my teaching. Today, you have taught me.”

On hearing this, the student was puzzled.

But Master Foo was enlightened.

Re: Master Foo and the Script Kiddie (2003)

#15
post #7

Earlier quoted context omitted.

The whole story, the vibe of the story, the moral of the story, the use of the word "crack"; it comes off pungently as if written by a professional Unix systems administrator.

The moral of the story is not about cracking or getting arrested. It is a metaphor for the danger of taking shortcuts, just like certain other shortcuts in programming that are currently popular and also come with their own version of 1337 language. And about the tools that enable ScriptKiddies or their modern equivalents to achieve some fast results, for which they have to pay later.

Yeah, no, I get that, it's just not how anybody who actually broke into computers would think about this.

Re: Master Foo and the Script Kiddie (2003)

#16
post #7

Earlier quoted context omitted.

The whole story, the vibe of the story, the moral of the story, the use of the word "crack"; it comes off pungently as if written by a professional Unix systems administrator.

What’s wrong with professional sysadmins? (It’s sysadmin appreciation day this Friday btw)

Nothing at all.

Re: Master Foo and the Script Kiddie (2003)

#18
post #15

Earlier quoted context omitted.

The moral of the story is not about cracking or getting arrested. It is a metaphor for the danger of taking shortcuts, just like certain other shortcuts in programming that are currently popular and also come with their own version of 1337 language. And about the tools that enable ScriptKiddies or their modern equivalents to achieve some fast results, for which they have to pay later.

Yeah, no, I get that, it's just not how anybody who actually broke into computers would think about this.

And it's not about those people. It's "Master Foo and the Script Kiddie", not "Master Foo and the Professional Red-Teamer".

It's about a fictional archetype, and the story isn't meant to be taken literally, it's illustrative for the sake of a lesson.

Re: Master Foo and the Script Kiddie (2003)

#20

The day after the stranger from Woot departed once more, a new student approached Master Foo as he was pruning the plum trees. “I have heard of your reputation,” the student said, bowing low. “They say you teach the Way of Unix, not for power, but for understanding. May I learn at your feet?” Master Foo nodded. “What is it you seek?” “I wish to master the system,” the student said, “to understand every process, every…

I’m curious what was the intended lesson to crack that machine.
Post reply on HN