|
Authored by: Anonymous on Sunday, November 18 2012 @ 05:17 PM EST |
I'm assuming that the class members are to provide the
passwords, not the social media companies ;)
Also, I keep thinking about how dumb people can be. The only
social media I use is Twitter. And I don't use personal
messages there, so everything is already in the open. I
there for consider that before every tweet I make.
Other than Twitter I use a Google+ account to follow people
that have interesting topics they post on. I sometimes
comment, again al in the open and always considering this
when I post.
I.do.not.ever.post.personal.information.on.the.internet!
I have asked my friends not to mention me by name or put
pictures of me on their accounts. And to notify me if they
see that someone has done so. I have only had to get angry a
few times.
What you can find on me on the internet is now mostly what I
want people to find or what I don't mind people to find. I
wasn;t always like this though and there is some stuff I
would not post today on me on the internet from wayback in
1993 and before! Mostly in old usenet posts, when I noticed
these were saved for ever I wisened up. The world should
too.
Look on the internet and see how many people with permanent
heart conditions you can find for example. Good luck to them
finding jobs ... :/[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Sunday, November 18 2012 @ 05:21 PM EST |
I was wondering how long it will take someone to modify the password command to
take 2 passwords. One to grant access and a second one that will wipe the
account. Although you could also use several login ID's. On one machine I had
a account called shutdown that let users shutdown the machine, rather than a
login shell it pointed to the shutdown command.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, November 19 2012 @ 01:37 AM EST |
It's not _that_ difficult to reverse it back into the password. Remember, the
client into which you type your password, has to be able to hash it into that
number. So even if its salted, it has to be salted with something predictable
or something that will be sent to the client as part of the transaction.
On-line attacks can be defended against (just slow down the responses after a
couple of incorrect login attempts), but that only works when the hashes are
safely locked up and can only be accessed by talking to the server.
An attacker with a copy of the hashes (i.e. after a security breach where
someone hacked the server, or just stole a laptop out of the back seat of a car,
or whatever) can brute-force guess a lot of the passwords by trying several
billion guesses in an hour or so. They can use sophisticated password-guessing
algorithms and huge rainbow tables to speed up the guessing process. That's why
weak passwords are a problem; if the hashes ever get stolen, a weak password
equals a compromised account.[ Reply to This | Parent | # ]
|
|
|
|
|