doubi5520 2019-04-23 03:44
浏览 86

在SQL中存储密钥作为明文是一个不好的举动? [重复]

In my web page, whenever someone creates a user account, a secret key would be generated for the 2nd Authentication(aka One-Time Password). An example of the generated key looks like this:"C9DR2VWVEE1SQXAR". Is it a bad move if I were to store this key as it is into the database, without hashing or salting or encrypting it? If so, what's a good way to store it php/mySQL?

Edit: I'm not looking for solutions for storing password, I'm asking about the secret key for the time-based OTP that is generated by the back-end. I don't see how it's linked to storing password, unless yo're telling me to store like a password.

</div>
  • 写回答

0条回答 默认 最新

    报告相同问题?

    悬赏问题

    • ¥15 写一个方法checkPerson,入参实体类Person,出参布尔值
    • ¥15 我想咨询一下路面纹理三维点云数据处理的一些问题,上传的坐标文件里是怎么对无序点进行编号的,以及xy坐标在处理的时候是进行整体模型分片处理的吗
    • ¥15 CSAPPattacklab
    • ¥15 一直显示正在等待HID—ISP
    • ¥15 Python turtle 画图
    • ¥15 关于大棚监测的pcb板设计
    • ¥15 stm32开发clion时遇到的编译问题
    • ¥15 lna设计 源简并电感型共源放大器
    • ¥15 如何用Labview在myRIO上做LCD显示?(语言-开发语言)
    • ¥15 Vue3地图和异步函数使用