Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As I remember, ASP.NET session id generator gives good protection against session prediction. The session id has 24 characters using [a-z] chars and [0-5] digits (total of 32 possible chars which is 2^5) which gives a total of 2^(5*24) = 2^120 possible values. However you can implement a SessionIDManager to append some information (like user hostaddress, user-agent, a validation token using a HMAC algorithm) for even better protection - so that a session id comming from a different IP Address or different browser wouldn't pass the validation. If you have forms authentication implemented, this is not necessary since the authentication ticket already provides these kinds of protection. </p> <p>If you want a better random session id you can use a RandomNumberGenerator such as RNGCryptoServiceProvider in your SessionIDManager and fill a bunch of bytes (say 32 which is 256 bits), then encode them using Base64</p> <pre><code>byte[] random = new byte[100]; //RNGCryptoServiceProvider is an implementation of a random number generator. RNGCryptoServiceProvider rng = new RNGCryptoServiceProvider(); rng.GetBytes(random); // The array is now filled with cryptographically strong random bytes. return Convert.ToBase64String(random) </code></pre> <p>However, <a href="http://msdn.microsoft.com/en-us/library/system.web.sessionstate.sessionidmanager.sessionidmaxlength.aspx" rel="nofollow">this article</a> says that the max length of your session id is 80, so you must override the Validate method also in order for it to work. </p>
    singulars
    1. This table or related slice is empty.
    1. POSession ID not random enough - ASP.NET
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVasea
    1. USVasea
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSession ID not random enough - ASP.NET
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWe don't use forms authentication on this application, but we have run a scan on a different application using forms authentication and get the same problem.
      singulars
      1. PO
      1. USryanulit
    2. COYour report also says that ASP.NET SessionId is generally random and big enough - it says it must have at least 32 bits and the Session Id in ASP.NET is a lot bigger than that. Have you tried to see what the values for your cookies are? (using fiddler or firebug in mozilla)
      singulars
      1. PO
      1. USVasea
    3. COBased on the linked articles in the OP, it sounds like this is exactly why this warning is appearing - they're triggering off of the 32 possible characters as being too narrow, without looking at the length or generation method.
      singulars
      1. PO
      1. USGalacticCowboy
 

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