Grâce au Génie, tu peux faire 3 voeux...

 Inscris-toi au site pour pouvoir commenter ! 

Tes gestes pour ta planète...

Qui va gagner La Nouvelle Star ?

Mon blog	orianettte, le 02.03.2010 à 15:47 1.avoir des vœux a l'infinit
Mon blog	maeva123123, le 20.02.2010 à 17:40 etre tjrs le majore de la classe sa c mon première voeux la 2ème c ke mn ptit cop1 ne ma plaque pas
Mon blog	mimi 0924, le 16.02.2010 à 15:48 être riche 2 devenir mannequin de chez channel 3 avoir des pou
Mon blog	mimi 0924, le 16.02.2010 à 15:48 rester avec mon coeur d amour avoir une l imousine et .. etre riche
Mon blog	mimi 0924, le 16.02.2010 à 15:47 1: j adore popo ma copine 2: j aime mes parents 3: je suis enfants quaté par mon grand pere
Mon blog	mimi 0924, le 16.02.2010 à 15:47 visitez mon blog et laissez moi plein de coms pleazzz ! ;-)
Mon blog	mimi 0924, le 16.02.2010 à 15:46 mark posted this on February 03, 2010 This is part 2 in a 3-part series about security at Meebo. See part 1. Before we get started I want to make it clear that sharing this information doesn't give away any secrets and doesn't make you any less safe! Today I'd like to talk about how we store the password for your Meebo account. Or more accurately, how we don't actually store the password for your Meebo account. Instead we store a "hash" created from your password. A hash is a string of characters that is calculated by running your password through an algorithm created by cryptographers (aka crazy smart math people). For a given password, the algorithm generates the same hash every time. It is easy to take a password and create a hash, but it is basically impossible to reverse this process, i.e. to take a hash and determine the original password. (For anyone curious, we're using bcrypt.) When you type your username and password to log into Meebo we calculate the hash of the password you provided. If this hash matches the hash stored in our database then you have successfully authenticated, yay! By storing a hash instead of the password, we greatly lessen the damage in the unlikely case that a hacker manages to get ahold of the information stored in our database. One weakness with this scheme is that, because many users use a simple word as their password, if a hacker is able to obtain the password hashes from our database then it would be possible for them to perform a "rainbow attack" to ascertain weak passwords. In this attack the hacker precomputes chains of hashes for each word in the dictionary and creates a rainbow table. The hacker would look up each hash from our database in this rainbow table. If he finds a match then he knows the password that was used to generate the hash. We neutralize rainbow attacks by "salting" the password before generating the hash. Salting means that a few letters are added to the password before the hash is calculated. We generate a few random letters for each user, and store this "salt" along with the password hash. In effect this makes everyone's password just a bit more random, which would require an unfeasibly large rainbow table. In summary: We store a salted hash of your password, NOT The password itself. These techniques are pretty brilliant and we certainly can't take credit for them—Unix at least has been using salted password hashes since the 1970s. It is our hope that sharing this information inspires other companies to be equally diligent with their own websites. Stay tuned for part 3, coming in a few days! Mark [ comments ] [ past blogs ] Follow us on Twitter
Mon blog	mimi 0924, le 16.02.2010 à 15:45 :être immortel avec ma famille 2:chanter avec mes stars préfères 3: faire tout les voeu que je veut
Mon blog	sona23062000, le 13.02.2010 à 19:04 1:être immortel avec ma famille 2:chanter avec mes stars préfères 3: faire tout les voeu que je veut
Mon blog	girlxo, le 06.02.2010 à 18:45 mark posted this on February 03, 2010 This is part 2 in a 3-part series about security at Meebo. See part 1. Before we get started I want to make it clear that sharing this information doesn't give away any secrets and doesn't make you any less safe! Today I'd like to talk about how we store the password for your Meebo account. Or more accurately, how we don't actually store the password for your Meebo account. Instead we store a "hash" created from your password. A hash is a string of characters that is calculated by running your password through an algorithm created by cryptographers (aka crazy smart math people). For a given password, the algorithm generates the same hash every time. It is easy to take a password and create a hash, but it is basically impossible to reverse this process, i.e. to take a hash and determine the original password. (For anyone curious, we're using bcrypt.) When you type your username and password to log into Meebo we calculate the hash of the password you provided. If this hash matches the hash stored in our database then you have successfully authenticated, yay! By storing a hash instead of the password, we greatly lessen the damage in the unlikely case that a hacker manages to get ahold of the information stored in our database. One weakness with this scheme is that, because many users use a simple word as their password, if a hacker is able to obtain the password hashes from our database then it would be possible for them to perform a "rainbow attack" to ascertain weak passwords. In this attack the hacker precomputes chains of hashes for each word in the dictionary and creates a rainbow table. The hacker would look up each hash from our database in this rainbow table. If he finds a match then he knows the password that was used to generate the hash. We neutralize rainbow attacks by "salting" the password before generating the hash. Salting means that a few letters are added to the password before the hash is calculated. We generate a few random letters for each user, and store this "salt" along with the password hash. In effect this makes everyone's password just a bit more random, which would require an unfeasibly large rainbow table. In summary: We store a salted hash of your password, NOT The password itself. These techniques are pretty brilliant and we certainly can't take credit for them—Unix at least has been using salted password hashes since the 1970s. It is our hope that sharing this information inspires other companies to be equally diligent with their own websites. Stay tuned for part 3, coming in a few days! Mark [ comments ] [ past blogs ] Follow us on Twitter
	vachetcindy, le 04.02.2010 à 19:51 1: voir les acteur est actrice de TWILIGHT 2: voir l' opéra rock en concert 3:que mon amour dure longtemps
Mon blog	zakiaz, le 04.02.2010 à 18:05 1 être riche 2 devenir mannequin de chez channel 3 avoir des pouvoir
	mamalina, le 27.01.2010 à 08:53 1: j adore popo ma copine 2: j aime mes parents 3: je suis enfants quaté par mon grand pere
	naila93, le 14.01.2010 à 19:18 1 je ve que ma famille et moi ont soi immortele 2 je ve pu de devoir( mais j aime bien l école) et 3 je ve avoir tous les voeu que je ve .