You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described here, source files with names containing non-ASCII characters can be used to compromise a code base.
Enforcing ASCII-only filenames helps preventing these kind of attacks. revive is the perfect place to implement such enforcement.
There is already a banned-characters rule that helps mitigating some security risks, it seems a good candidate where to implement the checks on filenames.
The text was updated successfully, but these errors were encountered:
As described here, source files with names containing non-ASCII characters can be used to compromise a code base.
Enforcing ASCII-only filenames helps preventing these kind of attacks.
revive
is the perfect place to implement such enforcement.There is already a
banned-characters
rule that helps mitigating some security risks, it seems a good candidate where to implement the checks on filenames.The text was updated successfully, but these errors were encountered: