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

Make internal database files group-readable #68

Closed
michaelklishin opened this issue Mar 13, 2015 · 1 comment · Fixed by #77
Closed

Make internal database files group-readable #68

michaelklishin opened this issue Mar 13, 2015 · 1 comment · Fixed by #77

Comments

@michaelklishin
Copy link
Member

They are currently world-readable.

@michaelklishin
Copy link
Member Author

Archive bug tracker has 26443 which fixes this for Debian packages, fixed in ad004f9.

michaelklishin added a commit that referenced this issue Mar 16, 2015
 * Revoke group writing permission
 * Revoke all "others" permissions

References #68.
@dumbbell dumbbell added this to the 3.5.1 milestone Mar 18, 2015
michaelklishin added a commit that referenced this issue Mar 18, 2015
 * Revoke group writing permission
 * Revoke all "others" permissions

References #68.
dcorbacho pushed a commit that referenced this issue May 27, 2016
dcorbacho pushed a commit that referenced this issue Jul 5, 2023
As discovered in #68, there is a typo in one of the returned
error atoms.

We stick to "invalid_last_offset_epoch" over "invalid_last_epoch_offset"
because the check that detects an invalid value
in osiris_log:check_chunk_has_expected_epoch/3 checks for epoch
validity, not offset validity.

This is a potentially breaking change but even in RabbitMQ-related
projects, this specific error was not handled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants