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

Non-portable cert file names for pki backend (colon characters in CIFS mount) #2552

Closed
saikatguha opened this issue Apr 1, 2017 · 1 comment
Closed

Non-portable cert file names for pki backend (colon characters in CIFS mount) #2552

saikatguha opened this issue Apr 1, 2017 · 1 comment
Milestone
0.7.1

Comments

@saikatguha
Copy link

I have the data folder mounted using CIFS.
unix filename translation is not supported in my environment.
The PKI backend attempts to write the cert to file: logical/<guid>/certs/_33:d2:80:....
Due to colon characters in the name, the file creation fails, and the PKI backend doesn't work.

It should be possible to use characters that are portable across platforms.
@jefferai
Copy link
Member

jefferai commented Apr 6, 2017

Related to #2203

jefferai added a commit that referenced this issue Apr 6, 2017
@jefferai
Change storage of entries from colons to hyphens and add a
47035cf 
lookup/migration path

Still TODO: tests on migration path

Fixes #2552
@jefferai jefferai mentioned this issue Apr 6, 2017
Merged
@jefferai jefferai added this to the 0.7.1 milestone Apr 13, 2017
jefferai added a commit that referenced this issue Apr 18, 2017
@jefferai
Change storage of entries from colons to hyphens and add a
dba2de5 
lookup/migration path

Still TODO: tests on migration path

Fixes #2552
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
0.7.1
Development

No branches or pull requests
2 participants
@jefferai @saikatguha