Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Being able to see others' passwords is really bad practice, if for no other reason, because in practice everyone uses the same password for different services/sites/logins. So that would be a big NO in my opinion.</p> <p>Even more, you should always keep passwords encrypted when in a database. The usual ways to encrypt passwords (SHA, MD5, crypt or some other form of hash) are not two-way, so that once the password is typed and cyphered, it cannot be decyphered. What the application does, when the user enters the password again, cypher what the user typed and compare the resulting hash to what is stored in the database. So that prevents any users from seen the plain-text passwords and if you have a data leak, won't be of much use, as long as you require "secure" passwords.</p> <p>Passwords should have a minimum allowed size, usually 8 or more characters (makes it harder to brute-force discovering them), and preferably be composed of lower case, higher case, numbers and special characters. The longer the password, the better. Passphrases are really much more secure than smaller passwords with lots of different cases, numbers, special charaters, because they will take longer to brute force.</p> <p>As for being able to change others' passwords, that is desirable, yes, because users loose their passwords all the time, and you need a way to reset them, or change them. Also can be a quick dirty way of disabling a users' account if needed.</p> <p>Changing passwords periodically can increase security in the long term, because a possibly comprimised password will not be usable when changed, but they introduce the burden of having a lot more forgotten passwords and complains from users.</p> <p>Never send a password by email, and password recovery functionality is also a lower of security grade, but again security is always in a balance together with practical use.</p> <p>Having a temporary change-on-first-login password is also interesting, because it will lower the use of support and prevent users from having to go to the administrator, or have their passwords sent by email (permnanent passwords).</p> <p>For temporary passwords always use good random ones, and never user1234 or surname123 or any combination of public information, because it is very easy to obtain and can be used by anyone with knowledge of the formation rule.</p>
    singulars
    1. This table or related slice is empty.
    1. POGood practice for password management for supervisor?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarco Poli
    1. USMarco Poli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGood practice for password management for supervisor?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGreat answer. So basically, only let the manager change the password, reset it, or disable the user account?
      singulars
      1. PO
      1. USRob Shnayder
    2. COclarification: hashing is not encryption. MD5, SHA, etc., do not perform any encryption. you do not compare a cypher to a hash (you could, but it's largely pointless), you compare a hash to a hash. Other than that, excellent answer!
      singulars
      1. PO
      1. USRussell Uhl
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload