Comparison of Hashing vs Encryption in MS SQL Server

Поделиться
HTML-код
  • Опубликовано: 26 окт 2024

Комментарии • 10

  • @rupenanjaria
    @rupenanjaria 4 года назад +1

    Great, just so others know, MD2, MD4, MD5, SHA, and SHA1 algorithms are deprecated starting with SQL Server 2016 (13.x). Use SHA2_256 or SHA2_512 instead. Older algorithms will continue working, but they will raise a deprecation event.

    • @JayanthKurup
      @JayanthKurup  4 года назад

      Yes, always a good idea to keep an eye on deprecated features.

  • @krscotthockey
    @krscotthockey 6 лет назад +1

    How do you check a password using hashing if it’s stored with newid() attached? Won’t newid() return a different ID every time? So when as user logs into a webpage and we take the password to compare to the stored one, how do we ensure an accurate comparison?

    • @JayanthKurup
      @JayanthKurup  6 лет назад

      For the above case you would store the seed ( newid value) in the database and concat it with the input password to generate the hash value. On login we fetch the seed from database for the username and concat it with the input password then generate the hash value at time of lohin. Next we compare the hash value with what is already saved in the db. WordPress uses a similar approach

    • @krscotthockey
      @krscotthockey 6 лет назад

      Jayanth Kurup makes total sense. I was thinking that we would add the newid to the select when comparing the values. Thanks for the response!

  • @PremKumarGanji
    @PremKumarGanji 7 лет назад

    Really Interesting and Informative..

    • @JayanthKurup
      @JayanthKurup  7 лет назад

      Prem Kumar thank you . Glad you found it useful

  • @professorhufe
    @professorhufe 7 лет назад

    Good explanation!