Re:One solution for spam in your inbox
on
As the Spam Turns
·
· Score: 1
Be careful of the spammers who try sending mail to common users at a given domain. ie. info@domain.com sales@domain.com and so on.
Re:Breaking things is not fixing the problem.
on
As the Spam Turns
·
· Score: 3, Insightful
How would you redesign SMTP? It's incredibly difficult to come up with a system that will allow one message through, that won't allow one message through that was also sent to five hundred other people on other servers without some sort of authority (be it a p2p authority, or a centralized authority).
If you're looking for checklists, Microsoft has some available. But if you've been looking, you're probably aware of them. Nevertheless, I used them when securing my network.
I never banked with Bank One, but First Chicago (which was one of the banks merged into Bank One) screwed me out of $400 or so the very same way. I withdrew $20 from an ATM, twice, to get two $10 bills. I got charged $25 for an overdraft for both withdrawls, as a check I had deposited hadn't yet cleared. Then there was a flurry of check writing for this and that. Some large checks, and some small checks. $3.50 or $5.00 or whatever. Somehow, two weeks later, I had to borrow $50 from my mother in addition to my next paycheck, just to close the account, DESPITE them agreeing to drop one of the $25 fees from my ATM overdraft, and that it wasn't fair.
I now bank with LaSalle. They're pretty good. I'm very happy with them.
Pack everything important for day to day life up by itself, and make sure you keep track of it. (toiletries, daily clothes, etc.) After that's taken care of, pack everything up by according to which room it'll end up in. When possible, pack things as tight as possible, to minimize breakage and shifting.
Yes, what he said. Also, read the Jargon File. Anything it recommends is a good read. See the entries for Dragon Book for compiler design, for example.
I checked both the terms & conditions linked at the bottom of the page, and the privacy policty just above it. I didn't see any reference to advertisements of any sort.
From what I've heard, don't live in Tokyo. The people of Tokyo itself are extremely xenophobic, and there are many places where foreigners are "not allowed". I also have heard that things become much better once you leave the city, and go out into the country, or to other cities. (This is all secondhand, but I've heard the same thing from multiple sources.)
I still find it extremely hard to believe that any nontrivial sequence of bits can be incompressible. (nontrivial because individual bits can't be compressed.) But I'm going to do some research.
Have you got a reference? This definition of random does not seem right.
(Assuming your definition), Assuming there is no upper bound on random numbers, Then any generalized test on whether a number is random takes an infinite number of bits. Therefore any generalized test on whether a number is random is impossible. QED.
Then, going back to your first premise that they produced these random numbers using this system, how did they know?
Also, in my prior algo, you can change the test from "is the number random" to "is the number not provably non-random". Namely, testing the number with some compression schemes designed to fit in a small number of bits.
This doesn't make sense to me. Here's an algo optimized for storing random numbers according to your definition. Basically, it compresses based on the premise that not all numbers are random, and a number can be tested as being random or not.
Assuming your definition of random numbers Assume not all numbers are random.
a = 0 for n = 0 to 2^32
If n is a random number, then
store n as a
a = a + 1
If your random number generator is incapable of generating a string of 256 0's in a row, there is something wrong with it.
True randomness is defined by the fact that knowing all of the previous results gives you zero knowledge of the next result. Being difficult to compress is often a side effect of this, but is not a defining characteristic.
In other news, Newark International Airport was shut down, because planes create excessive G-Force pressure on take-off. And accelerating your car too quickly? That's a no-no too.
It's easy to remain undetected with a custom patch cord, (no transmit). IIRC, 10BaseT, you simply didn't set up the TX wires, and 100BaseT, you untwisted one of the twisted pairs.
It's even possible to remain undetected with software only, but you *really* need to know what you're doing. Stuff can be detected on the ethernet layer that most people aren't aware of.
I did something similar recently. Touched a very hot heat sink. The CPU fan had semi-died.
After telling my father, who is an EE, about it, he proceeded to tell me about why it is a bad idea to touch a heat sink. Some heatsinks are hot, as in electricity hot, at extremely high voltage. And some of them get extremely hot (temperature), with no obvious way of telling, (which I had already discovered by way of removing a fingerprint).
Slashdot Mirror
Be careful of the spammers who try sending mail to common users at a given domain. ie. info@domain.com sales@domain.com and so on.
How would you redesign SMTP? It's incredibly difficult to come up with a system that will allow one message through, that won't allow one message through that was also sent to five hundred other people on other servers without some sort of authority (be it a p2p authority, or a centralized authority).
If you're looking for checklists, Microsoft has some available. But if you've been looking, you're probably aware of them. Nevertheless, I used them when securing my network.
I never banked with Bank One, but First Chicago (which was one of the banks merged into Bank One) screwed me out of $400 or so the very same way. I withdrew $20 from an ATM, twice, to get two $10 bills. I got charged $25 for an overdraft for both withdrawls, as a check I had deposited hadn't yet cleared. Then there was a flurry of check writing for this and that. Some large checks, and some small checks. $3.50 or $5.00 or whatever. Somehow, two weeks later, I had to borrow $50 from my mother in addition to my next paycheck, just to close the account, DESPITE them agreeing to drop one of the $25 fees from my ATM overdraft, and that it wasn't fair.
I now bank with LaSalle. They're pretty good. I'm very happy with them.
Last post!!1!
Pack everything important for day to day life up by itself, and make sure you keep track of it. (toiletries, daily clothes, etc.) After that's taken care of, pack everything up by according to which room it'll end up in. When possible, pack things as tight as possible, to minimize breakage and shifting.
Then again, I thought this was obvious.
Yes, what he said. Also, read the Jargon File. Anything it recommends is a good read. See the entries for Dragon Book for compiler design, for example.
http://www.progressquest.com
Just as addictive, but fully automated.
I checked both the terms & conditions linked at the bottom of the page, and the privacy policty just above it. I didn't see any reference to advertisements of any sort.
So, where is this new policy?
nop I don't get it.
</pun>
For a working example of this, see:
http://labs.google.com/keys/index.html
From what I've heard, don't live in Tokyo. The people of Tokyo itself are extremely xenophobic, and there are many places where foreigners are "not allowed". I also have heard that things become much better once you leave the city, and go out into the country, or to other cities. (This is all secondhand, but I've heard the same thing from multiple sources.)
(And it couldn't hurt to scan google groups.)
It means goat in czech too.
Who else feels like sending some crypto to postmaster@aspa.co.za?
Urm, forgot to say, I am aware of the "compress everything down to 1 bit" fallacy. But...
Anyway, I'll reserve further comment until after I read about everything a bit more.
Thanks for the reference.
I still find it extremely hard to believe that any nontrivial sequence of bits can be incompressible. (nontrivial because individual bits can't be compressed.) But I'm going to do some research.
Have you got a reference? This definition of random does not seem right.
(Assuming your definition),
Assuming there is no upper bound on random numbers,
Then any generalized test on whether a number is random takes an infinite number of bits.
Therefore any generalized test on whether a number is random is impossible. QED.
Then, going back to your first premise that they produced these random numbers using this system, how did they know?
Also, in my prior algo, you can change the test from "is the number random" to "is the number not provably non-random". Namely, testing the number with some compression schemes designed to fit in a small number of bits.
This doesn't make sense to me. Here's an algo optimized for storing random numbers according to your definition. Basically, it compresses based on the premise that not all numbers are random, and a number can be tested as being random or not.
Assuming your definition of random numbers
Assume not all numbers are random.
a = 0
for n = 0 to 2^32
If n is a random number, then
store n as a
a = a + 1
Computer Science is no more about computers than astronomy is about telescopes.
-- E. W. Dijkstra
If your random number generator is incapable of generating a string of 256 0's in a row, there is something wrong with it.
True randomness is defined by the fact that knowing all of the previous results gives you zero knowledge of the next result. Being difficult to compress is often a side effect of this, but is not a defining characteristic.
I know you didn't start this, but port 23 is telnet. SMTP is port 25.
In other news, Newark International Airport was shut down, because planes create excessive G-Force pressure on take-off. And accelerating your car too quickly? That's a no-no too.
(Relax, it's a joke.)
It's easy to remain undetected with a custom patch cord, (no transmit). IIRC, 10BaseT, you simply didn't set up the TX wires, and 100BaseT, you untwisted one of the twisted pairs.
It's even possible to remain undetected with software only, but you *really* need to know what you're doing. Stuff can be detected on the ethernet layer that most people aren't aware of.
I did something similar recently. Touched a very hot heat sink. The CPU fan had semi-died.
After telling my father, who is an EE, about it, he proceeded to tell me about why it is a bad idea to touch a heat sink. Some heatsinks are hot, as in electricity hot, at extremely high voltage. And some of them get extremely hot (temperature), with no obvious way of telling, (which I had already discovered by way of removing a fingerprint).
Oh no! They've blocked it for the rest of the world too!
Now they've gone too far.