-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Croc from recommendations #927
Conversation
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember to remove from the tools page too
@dngray As @lx-is already stated, it is still present here (to clarify): https://deploy-preview-927--privacyguides.netlify.app/tools/#file-sharing. Please remove it from there, then we should be ready to merge. |
He has blocked me as I cannot comment on any issues. I don't think there's much hope of SIEC being removed, which is very unfortunate. I'm not sure why RedRocket was unconcerned when investigating, although they note weird design decisions in their conclusion. The developer's blog again reinforces the fact that he views SIEC as a good choice. |
In general, this is something that concerns us, experimental crypto should never make it into products as a default which people depend on. |
croc author here. Had some time today so I defaulted croc to P-256 instead of SIEC as of v9.5.3. Ps. Yeah samuel-lucas6 is banned from croc temporarily for doubling down on troll behavior (inflammatory comments, etc). |
A wise decision. If you had clarified your initial reply to the Curve25519 issue, then I would have done the PR for that myself, but you chose not to answer my question. It's notable that you have still not removed SIEC despite closing the GitHub issue, meaning a risk of potential insecurity remains for a reason you have yet to justify because you did not respond to my questions.
My intent was never to troll. However, I was and will continue to be accusatory and infuriated because you are blatantly avoiding my questions, brushing off criticism related to SIEC, and comfortable with your design decisions despite potential harm to your users. For the final time, let me make myself very clear:
If you do not want this security obligation, then I suggest you avoid security projects. |
Then you were and will continue to be a troll and the ban will be permanent.
People exhibiting troll-like behaviors are not worth answering to. Anyways, this privacy guide is new to me. I think its a great project, but I don't want any part of it. 👋 |
This is a follow up of #886
We're removing Croc, see issue: schollz/croc#468
We may consider it when schollz/croc#467 is completed.
For now as an alternative, we suggest using Magic Wormhole.