21
wowotek
204d

maybe it's a joke....

Comments
  • 12
    Rolling your own encryption is the safest way to store sensitive data!!!!!!
  • 2
    Oh god why
  • 2
    @pingu yeaaay moar exaggeration, complexity = SECUREEEE!!!!!
  • 4
    Thats.... a mess?
    Looks like the one who came up with this decided to sha256(base64(utf8(everything))) makes sense somehow.
  • 1
    @magicMirror yeah thats why i tag this as a joke, i don't know why this exaggerated code is necessary -_-
  • 1
    The only valid reason is to add complexity when doing reverse engineering
  • 0
    Actually at least two of those layers have a very valid reason. I still do not understand the whole function though.
  • 1
    To make it truely secure, store the data as a hash and then bruteforce it every time to reveal the original data.
  • 2
    @unsignedint so the user can wait to finally login about a year after pressin' the button
  • 1
    This is like hashing on steroids. Very inefficient and unnecessary too. Just create a SHA2 or SHA3 hash using an implementation of PBKDF2 key derivation to make brute forcing difficult.
  • 0
    RIP Clean Code
  • 0
    @bigus-dickus wat? pbkdf is essentially repeated sha....
    oh..... i get it now.
Add Comment