Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Firesheep is <strong>nothing new</strong>. Session hijacking has been going on for more than two decades. You don't need "encrypt" your cookie, thats handled by your transport layer. Cookies must always be a <a href="http://en.wikipedia.org/wiki/Cryptographic_nonce" rel="nofollow">cryptographic nonce</a>. </p> <p>Usually hackers just set their own cookie by typing this into the address bar <code>javascript:document.cookie='SOME_COOKIE'</code>, FireSheep is for script kiddies that fear 1 line of JavaScript. But it really doesn't make this attack any easier to perform. </p> <p>Cookies can be hijacked if you don't use HTTPS for the entire life of the session and this is apart of <a href="http://www.owasp.org/index.php/Top_10_2010-A9-Insufficient_Transport_Layer_Protection" rel="nofollow">OWASP A9 - Insufficient Transport Layer Protection</a>. But you can also hijack a session with XSS.</p> <p>1)Use <a href="http://www.owasp.org/index.php/HttpOnly" rel="nofollow">httponly cookies</a>. (Makes it so JavaScript cannot access document.cookie, but you can still do session riding with xss)</p> <p>2)Use "<a href="http://enablesecurity.com/2008/08/29/setting-the-secure-flag-in-the-cookie-is-easy/" rel="nofollow">secure cookies</a>" (Horrible name, but its a flag that forces the browser to make the cookie HTTPS only.)</p> <p>3)Scan your web application for xss using <a href="https://sitewat.ch/en/About" rel="nofollow">Sitewatch(free)</a> or <a href="http://wapiti.sourceforge.net/" rel="nofollow">wapiti (open source)</a></p> <p>Also don't forget about CSRF! (Which firesheep doesn't address)</p>
    singulars
    1. This table or related slice is empty.
    1. POMitigating the 'firesheep' attack in the application layer?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USrook
    1. USrook
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMitigating the 'firesheep' attack in the application layer?
      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. COYes. It's nothing new. The New as you mention is that the skript kiddies can get in on the act. Which is why it's potentially such a problem. I want to protect my users.
      singulars
      1. PO
      1. USpobk
    2. CO@pobk You should be enabling these security features before Firesheep. This tool doesn't change anything.
      singulars
      1. PO
      1. USrook
    3. COOur application is as secure as we can make it (it complies with PCI DSS)... We're just looking beyond at protecting our users.
      singulars
      1. PO
      1. USpobk
 

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