Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is no technical reason to disallow any characters in a password. I guess in the case you describe, they would allow only alpha-numeric characters to avoid problems on the user's side (say, by entering a character that isn't available on keyboards in another country). </p> <p>Many providers and sites force users to choose very complex passwords containing a minimum number numbers and, sometimes, evenb special characters to prevent brute-forcing or <a href="http://en.wikipedia.org/wiki/Dictionary_Attack" rel="noreferrer">dictionary attacks</a>.</p> <p>I don't think <em>forcing</em> people to choose a complex password is wise. Passwords you can't remember, you will write down somewhere, which is often creating a much bigger security risk in real life. </p> <p>A simple rate limit in the login system (e.g. deny access for 15 minutes after 3 failed login attempts) takes the edge off the brute-forcing threat much more elegantly. </p> <p>One doesn't have to agree 100% with it, but I found this provocative paper on the subject from Microsoft Research very interesting. <a href="http://www.google.de/url?sa=t&amp;source=web&amp;cd=1&amp;ved=0CBkQFjAA&amp;url=http%3A%2F%2Fresearch.microsoft.com%2Fen-us%2Fum%2Fpeople%2Fcormac%2Fpapers%2F2009%2FSoLongAndNoThanks.pdf&amp;ei=UQMvTIqRA8SlOIaSpfUB&amp;usg=AFQjCNFnnpIpPA2pr_sWPMYEon3wfiWYrw" rel="noreferrer">So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users</a></p> <p>From the abstract:</p> <blockquote> <p>It is often suggested that users are hopelessly lazy and unmotivated on security questions. They choose weak passwords, ignore security warnings, and are oblivious to certificates errors. We argue that users' rejection of the security advice they receive is entirely rational from an economic perspective. The advice offers to shield them from the direct costs of attacks, but burdens them with far greater indirect costs in the form of effort. </p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. PODisallowing characters in a password?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPekka 웃
    1. USPekka 웃
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODisallowing characters in a password?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for not forcing. =)
      singulars
      1. PO
      1. USAlix Axel
    2. CO+1 for no restrictions. I distrust sites that feel the need to restrict my password - it makes me wonder why they feel the need to restrict it, and how they are storing it.
      singulars
      1. PO
      1. USMike
    3. COWriting down your complex password isn't as much a security risk as not writing down your weak or "easy to guess" password. Most attacks are made remotely. If people have access to your desk where your written down password is, they will also be likely to have physical access to your computer with cookies that keep you logged in. That is unless you encrypt your harddisk, but I don't know any non-geek that does that. I don't think a lockout system is a good idea. It will be too easy doing a DoS against your users. All I have to do is make a few failed attempts on your account to lock you out.
      singulars
      1. PO
      1. USDaniel Egeberg
 

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