Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Avoid recording confidential information in shell history #4891

Open
Tracked by #4899
royi-luo opened this issue Feb 12, 2025 · 0 comments · May be fixed by #4910
Open
Tracked by #4899

Avoid recording confidential information in shell history #4891

royi-luo opened this issue Feb 12, 2025 · 0 comments · May be fixed by #4910
Assignees
@MSebanc

Comments

@royi-luo
Copy link
Collaborator

We currently cache all executed commands in shell history.

However, there are some commands (such as when setting API secrets call s3_secret_access_key=...) that contain confidential information that we should not cache in shell history for security reasons.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MSebanc MSebanc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement confidential statement kuzudb/kuzu
2 participants
@royi-luo @MSebanc