-
Notifications
You must be signed in to change notification settings - Fork 173
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
the relative path in secretFile
is error-prone; 限制 secretFile 能访问的路径
#631
Comments
这个我来看一下吧 |
secretFile
is error-pronesecretFile
is error-prone 限制 secretFile 能访问的路径
secretFile
is error-prone 限制 secretFile 能访问的路径secretFile
is error-prone; 限制 secretFile 能访问的路径
plz assign it to me, thx |
@MichaelDeSteven Cool. Thanks! |
@seeflood 这个是不是要将 |
@MichaelDeSteven 是的,如果发现不在相同目录就报错
就是读 “和配置文件相同目录下的 secret_local_file.json” |
|
/good-first-issue cancel |
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue or help wanted. Thank you for your contributions. |
What happened:
Currently we have
secretFile
configuration in config.json.layotto/configs/config_standalone.json
Line 62 in 4f5a3e4
This configuration uses relative path, which is error-prone.
error message:
If someone configurates some other path as the
secretFile
, security issues may arise.For example, we can configurate a path where we don't have read permission, and leverage layotto to read the sensitive data.
What you expected to happen:
Restrict that the
secretFile
configuration can only refer to the files under same path.For example:
And Layotto will try to read the
secret_local_file.json
under the same path with config.jsonHow to reproduce it (as minimally and precisely as possible):
See case 2 above
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: