HackerOne has a free offering for open source projects. ^^
Let me know if you have any questions (I manage it). :-)
HackerOne has a free offering for open source projects. ^^
Let me know if you have any questions (I manage it). :-)
Not to be snarky, but haven't people written tools to help with this? This seems like a common issue. I mean, there's `sed` and similar tools, obviously, but something that could go, validate that the link works over https://, and update it. I don't see why that would need to be some monumental amount of work.
HTTPS is more than just privacy. See https://certsimple.com/blog/ssl-why-do-i-need-it and https://www.troyhunt.com/ssl-is-not-about-encryption/
I think this shows how valuable it is to use incentives to get people to Do The Right Thing(tm). Perhaps more things should be changed to require HTTPS.
Sure, Apple should ship a fix, but there are ways around it for now.
This should be implemented using a cryptographically secure random number generator. Presumably, the TSA requirements would specify some defense against an attacker being able to predict program outputs.
I submitted https://github.com/arik-so/tsa/issues/4 about this issue.
(removed DSA link as per advice below)
Signed, The guy who marked that bug report invalid.
And that's not even considering the security and privacy risks to email users from third-party email scanning and rewriting.
I could also imagine legal issues going both ways, particularly if the third party is tempted to retain data about email users.
For example, some universities that use Gmail and Google Apps for Education (for example) required that Google not scan student email, presumably due to privacy and legal requirements, or faculty email (due to faculty objections), and Google itself ultimately abandoned the practice in the face of a lawsuit.
https://marketbrief.edweek.org/marketplace-k-12/google_aband...