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.

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

Add builder.secret() to mark Properties for obfuscation in memory #26

Open
eeverman opened this issue Dec 8, 2016 · 0 comments
Open

Comments

@eeverman
Copy link
Owner

eeverman commented Dec 8, 2016

Any Property could be secret. Perhaps some sort of obfuscation that hides the value a bit in memory so it is not see easily harvested would be a nice addition? Might additionally ensure that toString() doesn't print the value.

@eeverman eeverman modified the milestone: v0.3 Dec 18, 2016
@eeverman eeverman changed the title Add Password string ConfigPoint that doesn't spew its values to the log Add Password string Property that doesn't spew its values to the log Dec 18, 2016
@eeverman eeverman removed this from the v0.3 milestone Dec 24, 2016
@eeverman eeverman modified the milestones: 0.3.1, 0.3.2, 0.3.x Mar 28, 2017
@eeverman eeverman modified the milestones: 0.3.x, 0.4.x Jul 25, 2017
@eeverman eeverman modified the milestones: 0.4.x, 0.4.1 Sep 10, 2018
@eeverman eeverman changed the title Add Password string Property that doesn't spew its values to the log Add Password string Property Oct 17, 2018
@eeverman eeverman modified the milestones: 0.4.1, 0.5.0 Oct 17, 2018
@eeverman eeverman changed the title Add Password string Property Add builder.secret() to mark Properties for obfuscation in memory Oct 26, 2021
@eeverman eeverman modified the milestones: 0.5.0, 0.5.1, Next Next Major Oct 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant