Which is why you have no business writing security sensitive software.
Maybe come back in a few years after some more study and understanding of this world.
Maybe come back in a few years after some more study and understanding of this world.
With due respect to the fact you are making an effort to get into the scene, congratulations for making the effort to share! Maybe just hold off on saying it’s going to “change the world”. We never say unhackable.
But in all seriousness, you do not have sufficient exposure or time in the field to sufficiently understand the threats your product is trying to defend against.
You are proposing replacing people’s security systems with your new unhackable thing. But it’s missing essential parts.
Schneier’s Law: any person can invent a security system so clever that they can’t think how to break it.
Keep playing, but maybe hold off on the “products” for a few more years while you learn the rest of the field, otherwise you may be doing harm to people, people’s data, etc.
That said, I definitely respect the complexity of the field and the importance of experience. I’m still learning every day and appreciate the insights from more seasoned professionals. While I may have had some early experiences, I realize there’s always more to learn, especially when it comes to ensuring my systems are truly secure and ready for the real world.
I’ll be taking the feedback seriously and continuing to build on my knowledge. Thanks again for sharing your thoughts!
Security Engineering: https://www.cl.cam.ac.uk/~rja14/book.html
His student network social's are filled with examples of defeating various commercial security systems.
That’s why folks all said the same thing. Real security people don’t talk like this.
Be really careful. You are at an age at a point in history where most written text you are going read is AI slop. Don’t be part of the problem here.
Written entirely by a human with no AI assistance.
One thing I would suggest is dropping the mail component and not involving it at all - you are using this as a weak second factor, exportable; monthly rotation. Bind it to a hardware key instead and use proper cryptography.
I understand that the way I explain things might come off differently compared to more seasoned security professionals, and I’ll work on improving the system that as I continue learning. I’m very hands-on in my approach, from testing to developing, and the feedback I’m receiving is helping me see where I can improve, especially in how I communicate technical concepts.
I appreciate the constructive criticism, and I’ll keep working to make sure I’m approaching things with the depth and accuracy expected in the field. Thanks for the advice!
Best,