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

make encryption optional #23

Open
huangp opened this issue Jan 13, 2016 · 3 comments
Open

make encryption optional #23

huangp opened this issue Jan 13, 2016 · 3 comments

Comments

@huangp
Copy link
Collaborator

huangp commented Jan 13, 2016

configuration option
@alex-sl-eng
Copy link
Owner

Work level or application level?

@huangp
Copy link
Collaborator Author

huangp commented Jan 17, 2016

Now it's in both place.config.properties to define which field to encrypt.
work form will contain optional encryption key to use.

On Sun, Jan 17, 2016 at 12:18 PM, Alex Eng [email protected] wrote:

Work level or application level?

—
Reply to this email directly or view it on GitHub
#23 (comment).

Patrick Huang
Senior Software Engineer
Engineering - Internationalisation
Red Hat, Asia-Pacific Pty Ltd
Level 1, 193 North Quay
Brisbane 4000
Office: +61 7 3514 8278
Fax: +61 7 3514 8199
IRC: pahuang
github: github.com/huangp
Website: www.redhat.com

@alex-sl-eng
Copy link
Owner

I think its best if the encryption is on all the time, and let Field decide if it needs encryption.
This will prevent user to be able to edit the yaml file directly on the encypted field but they can still update in using the UI. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alex-sl-eng @huangp