Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you modifying the NHibernate-based membership provider, or stuck using it out of the box? If the latter, it doesn't look like there's any extensibility. </p> <p>The ASP.NET SqlMembershipProvider works by accepting the name of a hash algorithm, conjures an instance via <a href="http://msdn.microsoft.com/en-us/library/wet69s13" rel="nofollow">HashAlgorithm.Create(name)</a> and then behaves a little differently if the algorithm type turns out to be a KeyedHashAlgorithm or regular (non-keyed) HashAlgorithm. The Zetetic.Security package is just providing a little bit of glue to make BCrypt and PBKDF2 compatible with that model.</p> <p>The sample code from NHMembershipProvider can't take advantage of that because it's very directly relying on HMACSHA1. I'd note that HMACSHA1 is not a secure algorithm for this purpose, nor is using a static salt for all users acceptable (it's scarcely better than no salt). The app ValidationKey and HMACSHA1 are meant for message integrity only.</p> <p>Here's a sample:</p> <pre><code>public class HashDemo { private static readonly RNGCryptoServiceProvider s_rng = new RNGCryptoServiceProvider(); public string HashPassword(string pwd, string hashName) { var alg = HashAlgorithm.Create(hashName); if (alg == null) throw new ArgumentException("Invalid hash name", "hashName"); byte[] tohash = System.Text.Encoding.UTF8.GetBytes(pwd); var ka = alg as KeyedHashAlgorithm; if (ka != null) { if (ka.Key == null || ka.Key.Length == 0) { byte[] key = new byte[20]; s_rng.GetBytes(key); ka.Key = key; } else { s_rng.GetBytes(ka.Key); } // TODO: return base64(ka.Key || alg.ComputeHash(tohash)) } else { var salt = new byte[20]; s_rng.GetBytes(salt); using (var ms = new System.IO.MemoryStream(salt)) { ms.Write(tohash, 0, tohash.Length); tohash = ms.ToArray(); } // TODO: return base64(salt || alg.ComputeHash(tohash)) } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVC - Integrating zetetic security with NHibernate Membership Provider
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSKradel
    1. USSKradel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET MVC - Integrating zetetic security with NHibernate Membership Provider
      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
    1. COI am modifying the NHibernate-based provider, so am at liberty to make modifications. It sounds (correct me if i'm wrong) like I need to pull out the EncodePassword implementation and insert a call to HashAlgorithm.Create?
      singulars
      1. PO
      1. USJP.
    2. COOne more thought - if you're rolling a MembershipProvider anyway, you might want to allocate separate columns for the hash alg name and parameters and hash output, in case you ever want to change from (let's say) BCrypt to SCrypt, or alter the work factor, the people with BCrypt hashes could still login.
      singulars
      1. PO
      1. USSKradel
    3. COThanks @SKradel - Your answer was very insightful. I'm moving away from using zetetics solution as it is more straightforward to invoke bcrypt directly from the MembershipPasswordFormat.Hashed case in the switch statement in the EncodePassword function (if i were not using a custom provider i would definitely go with the zetetic solution...). I really like the idea of storing both the algorithm and the work factor with each record and I plan to go a step further and rehash passwords upon login when the user's work factor does not match the current work factor used by the site.
      singulars
      1. PO
      1. USJP.
 

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