And, for what it's worth, I once had to write an HTTP fetch utility using nothing but SYSVR4 bourne shell, and stuff that shipped stock with a bare-naked install of Solaris 2.5.1.
Why? I needed stuff. NOW. I couldn't wait for next week for an 'admin' to install a web browser, I would have missed my go-live date.
Oh, yes, the box also had an old version of pine on it. I remember, because after HTTP fetching whatever it was, I had to de-base64-it.
I also once wrote an LR(1) parser for arithmetic expressions using nothing but native constructs in ksh (and not ((...))!). But that was just because I was bored. IIRC it was stack based, using a stack "class" implemented on top of ksh arrays and a shitload of evals.
Please, for the love God, somebody post a recipe to limit gnutella and bit-torrent traffic through a masquerading linux firewall. My home firewall just dies even though ip connection tracking seems to have WAY MORE than enough free connections.... every time two of my kids fire up a p2p client simultaneously. Bouncing the iptables kernel module DOES bring everything back to life.
This is with a 2.4 kernel and iptables 2.7.
So. Back on topic. Internet scourge? Dunno. Intranet Scourge? Yup.
Two possibilities: one password is chosen from all the letters of the alphabet, and is one character long. Another password is chosen from just the letters a, b, and c.. but is TWO letters long (twice as long).
Which is easier to guess?
Answer: The two character password has 3^2 = 9 possibilities: aa, ab, ac, ba, bb, bc, ca, cb, cc. The one character password has 26 possibilities.
Now you should know whether or not password length or alphabet size dominate brute-force password cracking.
Wow, at last, I have met my soul mate. Except you're a guy!
I got rid of my Nokia 2160 -- which is about 5 inches across, 2.5 inches deep and 8 inches tall -- to upgrade to a Nokia 6160 (TDMA). Then I got a 6160i to take advantage of mobile-originate SMS (I was also using it to control computers). The 6160i lasted a few years, then when it died I switched to the 6190 (same chassis and UI board, GSM network). The 6190 lasted a few more. Then I went with the 7190, as I had a couple of spares at work and the 6190 had gotten nearly inaudible. So far, I have phones with good battery life, excellent durability, good+consistent UI, which place calls, send/receive text messages, and that's IT. The 7190 actually had a WAP browser, but it was never configured for the network I used the phone on.
Then, a couple of years ago, I wanted a portable ssh machine. I got a Treo 600. Hated the phone, glad I kept the 7190. Then I got a Treo 650. Disliked the phone, glad I kept the 7190. Now I occasionally carry two phones -- a Nokia for making calls and Treo 650 for ssh (and m.gmail.com -- slashdot broke when the new CSS came out last year). Yes, two complete phones, with separate SIMs and call packages. Different form factor for different usage pattern.
Now I have this Nokia 3120 phone I got from a co-worker for free... still no camera, MP3 player, shoulder massager, prostate checker or kitchen sink, but it actually has a few features I really like compared to the phones I've been carrying for the last decade:
- 850 MHz radio lets it work better in the mall where I shop (previous GSM phones were 1900 only)
- Auto key-lock
- No antenna to snap off (I've gone through about 30)
- Easy to disassemble
- INCREDIBLE battery life. Really, as good as a 7190 with the HUGE battery.
- Built-in silent ringer
- small (1.75 x 6 x 0.75 inches)
- STILL works with my Nokia car charger for the 61xx phones (the 2160 had a different plug).. which can be bought locally at the dollar store
- Takes a lickin' -- keeps on tickin'
Features I don't like:
- menu 1-2-3-4 type of commands no longer works, even though the shortcuts are still written at the top of the screen
- Does not use the traditional m-bus + f-bus plug, so my desk kits don't work
- Does not have an external antenna jack, so my external antennas don't work
> [Hint: you do need a jump table for the opcode handlers.]
Hint 2: switch() statements wind up looking an awful lot like jump tables after compilation if you write 'em right (and your compiler doesn't suck).
Good half-an-iceberg tip. I've been around the block, but haven't heard that expression. It fits like a glove. And that's the technique I use for 98% of my real-world problems.
Let me also suggest that we replace the data construct with tag=data[newline]
I've been writing configuration files like that for years, and it works great. The only time I really want tags anyhow is when nesting stuff... and if you live in corporate IT land, you'll realize that doesn't actually happen because people who specify XML configuration files don't usually understand that a container is something that could hold things other than whisky and so forth.
Expired ID makes an excellent base for fake ID, as the legal holder will have a new one by now, at no cost. And will often pitch the expired one without destroying it. (Sad but true).
There was an OT thread on/. about two years ago about some guy getting carded to buy six peaches simultaneously at the grocery store. I thought it was freakin' hilarious.
I guess the HCN in a peach pit must be giving Homeland Security the willies.
He said, "Hey, I'm having a kid, so I don't expect to have much time in the future to do this shit. OH, and I'm losing my hosting Dec 15, so I guess that's when I'll officially shut it down"
> If you really never want to see your data again, just record it on a DVD-minus-R.
Scene at the Zeller's department store near my house:
Noob: What the difference between a DVD plus R and a DVD minus R? Droid: The plus R, you can read to it and write to it. The minus R, you can burn but you can't read from it. Me: So, what's the point of writing to a DVD if you can't read the data back? Droid: *drool* Noob: So what should I buy? Me: How old is your computer? Noob: Six months Me: Anything'll do. But shop at a computer store, it's cheaper.
Slashdot Mirror
Right on, brother.
And, for what it's worth, I once had to write an HTTP fetch utility using nothing but SYSVR4 bourne shell, and stuff that shipped stock with a bare-naked install of Solaris 2.5.1.
Why? I needed stuff. NOW. I couldn't wait for next week for an 'admin' to install a web browser, I would have missed my go-live date.
Oh, yes, the box also had an old version of pine on it. I remember, because after HTTP fetching whatever it was, I had to de-base64-it.
I also once wrote an LR(1) parser for arithmetic expressions using nothing but native constructs in ksh (and not ((...))!). But that was just because I was bored. IIRC it was stack based, using a stack "class" implemented on top of ksh arrays and a shitload of evals.
You were born around 1963.
Where do I claim my prize?
BTW, I heard a rumour that Van Halen is getting back together, with DLR as the front man.
Hee -- I don't know what dates you more: the reference to coal trains, or the expression "NetNews".
Does anybody actually call it that anymore?
And yes, once upon a time, nn 6.4 was my newsreader of choice... But then along came tin..
Please, for the love God, somebody post a recipe to limit gnutella and bit-torrent traffic through a masquerading linux firewall. My home firewall just dies even though ip connection tracking seems to have WAY MORE than enough free connections.... every time two of my kids fire up a p2p client simultaneously. Bouncing the iptables kernel module DOES bring everything back to life.
This is with a 2.4 kernel and iptables 2.7.
So. Back on topic. Internet scourge? Dunno. Intranet Scourge? Yup.
This is only true in the weird case where the alphabet size is an exact multiple of the machine byte size.
I know of few users using all 256 characters in their passwords.
And few computers using words shorter than eight bits long.
What do you think?
Okay, I'll make it easy.
Two possibilities: one password is chosen from all the letters of the alphabet, and is one character long. Another password is chosen from just the letters a, b, and c.. but is TWO letters long (twice as long).
Which is easier to guess?
Answer: The two character password has 3^2 = 9 possibilities: aa, ab, ac, ba, bb, bc, ca, cb, cc.
The one character password has 26 possibilities.
Now you should know whether or not password length or alphabet size dominate brute-force password cracking.
Wow, you HAVE been around for a while -- I remember 3380 drives, but not as NEW tech. :)
Do you by any chance know Mel? I heard he's a one hell of a hacker.
If more than all life is extinct -- how did you write this message?
Wow, at last, I have met my soul mate. Except you're a guy!
I got rid of my Nokia 2160 -- which is about 5 inches across, 2.5 inches deep and 8 inches tall -- to upgrade to a Nokia 6160 (TDMA). Then I got a 6160i to take advantage of mobile-originate SMS (I was also using it to control computers). The 6160i lasted a few years, then when it died I switched to the 6190 (same chassis and UI board, GSM network). The 6190 lasted a few more. Then I went with the 7190, as I had a couple of spares at work and the 6190 had gotten nearly inaudible. So far, I have phones with good battery life, excellent durability, good+consistent UI, which place calls, send/receive text messages, and that's IT. The 7190 actually had a WAP browser, but it was never configured for the network I used the phone on.
Then, a couple of years ago, I wanted a portable ssh machine. I got a Treo 600. Hated the phone, glad I kept the 7190. Then I got a Treo 650. Disliked the phone, glad I kept the 7190. Now I occasionally carry two phones -- a Nokia for making calls and Treo 650 for ssh (and m.gmail.com -- slashdot broke when the new CSS came out last year). Yes, two complete phones, with separate SIMs and call packages. Different form factor for different usage pattern.
Now I have this Nokia 3120 phone I got from a co-worker for free... still no camera, MP3 player, shoulder massager, prostate checker or kitchen sink, but it actually has a few features I really like compared to the phones I've been carrying for the last decade:
- 850 MHz radio lets it work better in the mall where I shop (previous GSM phones were 1900 only)
- Auto key-lock
- No antenna to snap off (I've gone through about 30)
- Easy to disassemble
- INCREDIBLE battery life. Really, as good as a 7190 with the HUGE battery.
- Built-in silent ringer
- small (1.75 x 6 x 0.75 inches)
- STILL works with my Nokia car charger for the 61xx phones (the 2160 had a different plug).. which can be bought locally at the dollar store
- Takes a lickin' -- keeps on tickin'
Features I don't like:
- menu 1-2-3-4 type of commands no longer works, even though the shortcuts are still written at the top of the screen
- Does not use the traditional m-bus + f-bus plug, so my desk kits don't work
- Does not have an external antenna jack, so my external antennas don't work
> [Hint: you do need a jump table for the opcode handlers.]
Hint 2: switch() statements wind up looking an awful lot like jump tables after compilation if you write 'em right (and your compiler doesn't suck).
Good half-an-iceberg tip. I've been around the block, but haven't heard that expression. It fits like a glove. And that's the technique I use for 98% of my real-world problems.
So is FreeBSD 2.x. What's your point?
Yes, before Microsoft bought it. They actually made it unusuable for several months in 1999 or so trying to make it run under NT.
Do you remember the guffaws resounding throughout /. and other geek websites when MS first tried to transition hotmail from freebsd to Windows NT?
Let me also suggest that we replace the data construct with tag=data[newline]
I've been writing configuration files like that for years, and it works great. The only time I really want tags anyhow is when nesting stuff... and if you live in corporate IT land, you'll realize that doesn't actually happen because people who specify XML configuration files don't usually understand that a container is something that could hold things other than whisky and so forth.
Riiiiight. But most people won't doctor the magstrip... Which is what this whole thread is about!
Maybe you should learn how to spell "department", then, you illiterate piece of trailer-raised scum.
You can start by studying your ID.
Expired ID makes an excellent base for fake ID, as the legal holder will have a new one by now, at no cost. And will often pitch the expired one without destroying it. (Sad but true).
> Am I really too drunk to drive if I drink an 8-ounce beer at my local restaurant?
I am.
OTOH, I know this, and wouldn't be stupid enough to ride after *any* amount of beer.
And THEREIN lies the problem with society: This ass-hat mommy state that is evolving.
I say: ban driver's side air bags and seat belts.. and let God sort it out.
There was an OT thread on /. about two years ago about some guy getting carded to buy six peaches simultaneously at the grocery store. I thought it was freakin' hilarious.
I guess the HCN in a peach pit must be giving Homeland Security the willies.
Man, you're a wacked out geek.
I have no clue WTF my neighbours look like... but I know all their wireless NIC MACs!
I'm making my copy of the Internet out of wrapping paper tubes.
It's pretty awesome.
Thank God for Christmas!
Did *you* read TFL?
He said, "Hey, I'm having a kid, so I don't expect to have much time in the future to do this shit. OH, and I'm losing my hosting Dec 15, so I guess that's when I'll officially shut it down"
Did you also send him an e-mail offering to parent his newborn?
Or did you think he would terminate it when he found out someone could host his domain?
> If you really never want to see your data again, just record it on a DVD-minus-R.
Scene at the Zeller's department store near my house:
Noob: What the difference between a DVD plus R and a DVD minus R?
Droid: The plus R, you can read to it and write to it. The minus R, you can burn but you can't read from it.
Me: So, what's the point of writing to a DVD if you can't read the data back?
Droid: *drool*
Noob: So what should I buy?
Me: How old is your computer?
Noob: Six months
Me: Anything'll do. But shop at a computer store, it's cheaper.
It's in the Pegasus Galaxy.
Duh!