its still just making the rainbowtable bigger. its a table over (telephonnumbers x salts), which is n times m when there are n possible phone-numbers and m possible salts. depending on length of the salt (and charset) its possible with a big HDD.
imagine, you have a salted hash with random salt for each hash (if the salt stays the same, the rainbow-table is easily generated). Now your phone hashes some telephone-number with a random salt. Try to find it in the db of numbers hashed with random salts. no chance, because a different salt is used.
the worst case stays the same: somebody who wants to do evil things captures as much as possible and does evil things with it. This is possible now and then. But the average case differs. When its forbidden to capture anything, the people, who are not plain criminals, but just dataminers acting in the legal range, will be stopped.
So of course, the worst case isn't any different, and you should still be afraid and encrypt your wlan as good as possible. But the sum of all datamining will be less, because the legal acting people will behave differently. Which is at least a small advantage to the status quo.
simple calculation: there a lot more linux servers than windows servers. but the percentage of linux servers hacked is a lot smaller than the percentage of windows-servers hacked.
the point is protecting people who do not know any better.
Of course, your worst-case analysis should consider: everything sent will be captured and stored forever and when its possible to decrypt it, then it will be analysed and used against you. When you assume this, no bad surprise will happen.
But another thing is, what the laws should look like. They should not assume the worst-case to be normal anyway, but forbid the bad parts. So the worst case CAN still happen, but it WON'T happen that often, because only people not caring about the legality of their actions will do it.
From the security point of view, you need still to consider the worst-case. But for people who do not know anything about security, their average case will be much better.
salting is only a small advantage. think of a salt-hashed telephone-number. a brute-force attack over all possible numbers (only the valid ones for the region where the contact is from) is done fastly. Okay, its too much when you want to crack each one in this way, but if you're only interested in a few special ones, it can be done.
some things to consider: - when you hash a telephone number, a rainbowtable is easily generated - even when you have ids, which are real pseudonyms, no option to crack them, then you can correlate "ah, user X knows Y, which is known by Z, too".
So uploading contact data is exposing private things, even when the nodes are ano(pseudo)nymous and only the edges of the social graph are known.
who would comply with this? Anyone who would is not worth hiring, as he will be the person handing out all company-data to the next social engineer. When the social engineer comes around the corner and says "hey, data-inspection day, please hand over all the company passwords"... you really hope none of your employees complies.
and you can represent every file as a number, you can now abandon all copyright on digital files.
this does not apply for stuff like real art, because there is no finite representation of an image on real paper. so you cannot find all the information contained in the image in pi, so its still copyrightable.
yes, and the ulimit is useful. But do not rely on the out-of-memory-killer of the kernel, it tends to kill completely unrelated processes first before killing the memleaking one.
at least it is possible to tweak firefox to look like in the 3.x releases. Even Win7 is hard to change to look really like win2000. You can change a lot of stuff, but at all places you will see its not the native look, its a compatiblity option.
Most of the "you are not allowed to rent some software" licenses are invalid in many countries. So if they are hosting outside of US, it may be just okay.
better the computer gets slow, because its swapping, than the computer starts killing random processes because its running out of memory. And today running out of memory means, you need to think in hundreds of mb, because when most programs use more memory on normal operation, they will request more memory when the system is short of memory, too.
Slashdot Mirror
its still just making the rainbowtable bigger. its a table over (telephonnumbers x salts), which is n times m when there are n possible phone-numbers and m possible salts. depending on length of the salt (and charset) its possible with a big HDD.
cannot be used.
imagine, you have a salted hash with random salt for each hash (if the salt stays the same, the rainbow-table is easily generated). Now your phone hashes some telephone-number with a random salt. Try to find it in the db of numbers hashed with random salts. no chance, because a different salt is used.
i do not think you got the point.
the worst case stays the same: somebody who wants to do evil things captures as much as possible and does evil things with it. This is possible now and then.
But the average case differs. When its forbidden to capture anything, the people, who are not plain criminals, but just dataminers acting in the legal range, will be stopped.
So of course, the worst case isn't any different, and you should still be afraid and encrypt your wlan as good as possible. But the sum of all datamining will be less, because the legal acting people will behave differently. Which is at least a small advantage to the status quo.
simple calculation: there a lot more linux servers than windows servers. but the percentage of linux servers hacked is a lot smaller than the percentage of windows-servers hacked.
the point is protecting people who do not know any better.
Of course, your worst-case analysis should consider: everything sent will be captured and stored forever and when its possible to decrypt it, then it will be analysed and used against you. When you assume this, no bad surprise will happen.
But another thing is, what the laws should look like. They should not assume the worst-case to be normal anyway, but forbid the bad parts. So the worst case CAN still happen, but it WON'T happen that often, because only people not caring about the legality of their actions will do it.
From the security point of view, you need still to consider the worst-case. But for people who do not know anything about security, their average case will be much better.
salting is only a small advantage. think of a salt-hashed telephone-number. a brute-force attack over all possible numbers (only the valid ones for the region where the contact is from) is done fastly. Okay, its too much when you want to crack each one in this way, but if you're only interested in a few special ones, it can be done.
some things to consider:
- when you hash a telephone number, a rainbowtable is easily generated
- even when you have ids, which are real pseudonyms, no option to crack them, then you can correlate "ah, user X knows Y, which is known by Z, too".
So uploading contact data is exposing private things, even when the nodes are ano(pseudo)nymous and only the edges of the social graph are known.
who would comply with this? Anyone who would is not worth hiring, as he will be the person handing out all company-data to the next social engineer. When the social engineer comes around the corner and says "hey, data-inspection day, please hand over all the company passwords" ... you really hope none of your employees complies.
oh tempora oh mores!
google got a lot of trouble for doing so. because its inevitable they capture some actual content of connections on insecure wlans.
and you can represent every file as a number, you can now abandon all copyright on digital files.
this does not apply for stuff like real art, because there is no finite representation of an image on real paper. so you cannot find all the information contained in the image in pi, so its still copyrightable.
> no real benefit to themselves
better ads = less adblocking.
you mean: Crap in, Crap out.
yes, and the ulimit is useful. But do not rely on the out-of-memory-killer of the kernel, it tends to kill completely unrelated processes first before killing the memleaking one.
just use a chroot, or maybe even lxc.
debootstrap is a great helper there, too.
no, it does not. either i owned you, or i pwned you, same thing, but fat fingers.
as they are not using cookies or other tracking stuff, they just cannot track you this way.
telnet to ssh port ... WTF
either use netcat as tool, or use "ssh -v" (much better idea for looking at the ssh-parameters)
Acid: Melts your mind, not your hand....
ftfy
i know people, who use firefox/ie, so they can login two times with different accounts to the same e-mail provider.
at least it is possible to tweak firefox to look like in the 3.x releases. Even Win7 is hard to change to look really like win2000. You can change a lot of stuff, but at all places you will see its not the native look, its a compatiblity option.
i think you're mixing up panels and WMs.
the smartest homer quote ever. (maybe after the triangles thing ;))
Most of the "you are not allowed to rent some software" licenses are invalid in many countries. So if they are hosting outside of US, it may be just okay.
better the computer gets slow, because its swapping, than the computer starts killing random processes because its running out of memory.
And today running out of memory means, you need to think in hundreds of mb, because when most programs use more memory on normal operation, they will request more memory when the system is short of memory, too.