--
This contains a number of incorrect assertions about cryptography.
First, it is not accurate to say that "using a crypto algorithm also counts as rolling your own crypto." In general, using a well-vetted and widely-used cryptographic algorithm, such as AES or RSA, is not considered to be "rolling your own crypto." While it is possible to introduce vulnerabilities when implementing cryptographic algorithms, these risks can be mitigated by using a well-tested and widely-used implementation of the algorithm rather than trying to create your own implementation.
Second, the statement that "must crypto vulnerabilities comes in glueing together solid crypto implementations" is not accurate. There are many potential sources of vulnerabilities in cryptographic systems, and the process of "glueing together" different components is just one possible point of failure. It is important to carefully design and implement cryptographic systems, but it is not accurate to suggest that all vulnerabilities arise from the process of combining different cryptographic components.
Finally, it is not accurate to say that "just 'using' a crypto algorithm sounds like a recipe for a vulnerability." While it is possible to introduce vulnerabilities by improperly using a cryptographic algorithm, it is not inherently risky to simply use a well-vetted and widely-used cryptographic algorithm. In fact, using such an algorithm can help to reduce the risk of vulnerabilities, as long-standing and well-studied algorithms are likely to have fewer unknown vulnerabilities than custom or less-widely used algorithms.
--
p.s. If you want to rebut the bot I'm happy to play the role of a mediator.
p.s.s I actually agree with you on this. GPT is missing the point: gluing introduces vulnerabilities and should be done by experts.
Possibly best to say don't roll your own crypto solution. That should cut down on the confusion. Algorithms are not complete solutions.
1. It could undermine the authenticity and integrity of the conversation by introducing responses that are not genuinely from a human.
2. It could create confusion or misunderstanding, as the responses generated by the language model may not be relevant or appropriate for the specific context in which they are used.
3. It could discourage genuine participation and contribution from other members of the community, as it may seem like the conversation is being dominated by automated responses rather than authentic human interaction.
Overall, it is important to consider the impact of your actions on the online community and to strive to contribute to respectful and meaningful discourse. Using the output of a language model as a substitute for genuine human interaction is generally not a good idea, as it can undermine the authenticity and integrity of the conversation.
The difference is, you're sort-of allowed to f up if it's an intelligent mistake that teaches the creators of misuse resistant libraries a thing or two about where they went wrong. If OTOH you're clearly just yoloing it, introducing your pseudo-math BS into the mix, or intentionally deviating from best practices or breaking it, then it's on you.
I'm not a crypto expert, I'm just telling you what I've been reading on HN for the past few years.