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

Should not change permissions for SSL certificates #1324

Closed
michaelrsweet opened this issue Oct 19, 2005 · 3 comments
Closed

Should not change permissions for SSL certificates #1324

michaelrsweet opened this issue Oct 19, 2005 · 3 comments
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.1.23
CUPS.org User: twaugh.redhat

(Red Hat Bugzilla bug #171163)

The SSL certificate specified by ServerCertificate, and key specified by ServerKey, should not have their permissions or ownership modified.

Firstly, the SSL certificate might need to be world-readable in some environments. Secondly, the SSL key might be shared with other services, such as LDAP or HTTP servers, which will also need to read the contents.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

OK, I can agree with this change if it only applied when the ServerKey and ServerCertificate are not under the ServerRoot (/etc/cups) directory, similar to how we treat the TempDir directive.

Does that sound reasonable?

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: twaugh.redhat

Sounds reasonable to me, yes. If the key is a link, the admin can use a symlink instead to avoid permissions changing where not expected.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Fixed in Subversion repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant