StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7270581
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-09-01T12:53:12.517
FavoriteCount
0
LastActivityDate
2011-09-01T12:53:12.517
LastEditDate
LastEditorUserId
0
OwnerUserId
194528
ParentId
7270526
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
No, because when the password gets hashed it doesn't look like <code>fishABC09</code>, it looks like: <code>5f4dcc3b5aa765d61d8327deb882cf99</code> which is an md5 hash. To gain access to your system, even if they know the hash, it cannot be reversed. We use salts in order to add complexity to our hashes, and to prevent hash lookups in rainbow tables. For example: Do a <a href="http://www.google.co.uk/search?aq=f&sourceid=chrome&ie=UTF-8&q=5f4dcc3b5aa765d61d8327deb882cf99" rel="nofollow">Google search</a> for the md5 hash of "password" which is: <code>5f4dcc3b5aa765d61d8327deb882cf99</code> A lot of results right? Now I'm going to create a hash again, I will still use "password", but I will add a SALT which is "AHG(*@". I'm guessing the only response will be for this post and some bot scrapers that have read this post :) <pre><code>cbe57e92ffbb0086320891b9f979156d </code></pre> Should be only a <a href="http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=md5%20concat#sclient=psy&hl=en&source=hp&q=cbe57e92ffbb0086320891b9f979156d&pbx=1&oq=cbe57e92ffbb0086320891b9f979156d&aq=f&aqi=&aql=&gs_sm=e&gs_upl=23464l23464l0l23794l1l1l0l0l0l0l282l282l2-1l1l0&bav=on.2,or.r_gc.r_pw.&fp=79337a0a8d512e3a&biw=1920&bih=944" rel="nofollow">few results</a>, or this post which are this post. <h2>Just Remember</h2> Just remember this... hashes are one way, so even if you gain the hash, you do not know what was used to create it 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do you securely store a user's password and salt in MySQL?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLayke
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COOh okay. Thanks for the clarification, Layke.
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
2. COMD5 is no longer secure, use something stronger like SHA2 with a 512 bit key.
 singulars
 PostPostId
 PO
 UserUserId
 USJohan
3. COYeah I know. :) I didn't have mcrypt library so I couldn't generate a hash using that algorithm. It was just as an example to make the point to answer the question.
 singulars
 PostPostId
 PO
 UserUserId
 USLayke

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.