THe result of a security scan yielded this:
“The calendar feed route uses MD5 to generate HTTP ETag values, a cryptographic algorithm considered weak since it is vulnerable to collision attacks.”
This weakness has been known for many years, and his “security” implementation should not be proposed or implemented in our code bases.
@Replit,
Can you please add avoiding such unsafe coding practices to a guardrail in .local/?
Thank you.