Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In my (electrical engineering, techie) graduate school, all computer accounts were initialized with passwords that, I assume, were generated by a standard linux utility. They consisted of three random syllables, with three lowercase letters in each syllable. The result was reasonably secure (on the order of billions of possible combinations) yet so pronounce-able that I still use some of those passwords over a decade later. James' example is an excellent demonstration of this.</p> <p>A comment on passwords in general, from a network-security professional: they're terrible, for several reasons, including:</p> <ul> <li><p>Generally easily broken, either through social engineering or with attack software, especially if you know <em>anything</em> about your target. </p> <p><em>Example 1:</em> I recently needed to revise a password-protected technical document. Looking at the date, I knew who our Tech Writer in residence was at the time, typed the first word that entered my mind, and immediately unlocked the document. </p> <p><em>Example 2:</em> Standard password-cracking programs allow the cracker to specify a set of rules that operate on a user-supplied dictionary. It's trivial to replace certain letters with $ymb01$, or to translate into 1337, etc.</p></li> <li><p>"Secure" passwords aren't. Given the sheer number of passwords most people need to remember, the most common way to "remember" a "strong" password like "a4$N!8_q" is to write it on a piece of paper (or, worse, store it in a text file). 'Nuff said.</p></li> </ul> <p>If you need truly <em>secure</em> authentication, <em>multi-factor</em> (or <em>two-factor</em>) is the industry-accepted mechanism. The "two factors" are usually something you <em>have</em> (such as an access card) and something you <em>know</em> that enables it (such as a PIN). Neither one works without the other--you need both.</p> <p>On the other hand, consider the level of security you really need. What are you protecting? How badly do the "bad guys" want to get it, and what are the consequences if they do? Chances are, "Its@Secret!" is more than good enough. :-)</p>
    singulars
    1. This table or related slice is empty.
    1. POCharacters to avoid in automatically generated passwords
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdam Liss
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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
    1. COIf you're interested, the password was "Yahweh" with a capital Y. I'm not psychic, either. If you'd had a 5-minute conversation with our tech writer, you'd have guessed it, too -- first try.
      singulars
      1. PO
      1. USAdam Liss
 

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