Antoine Beaupré wrote: > > First, a big warning: By checking /etc into version control, you are > > creating a copy of files like /etc/shadow that must remain secret. Anytime > > you have a copy of a secret file, it becomes more likely that the file > > contents won't remain secret. etckeeper is careful about file permissions, > > and will make sure that repositories it sets up don't allow anyone but root > > to read their contents. However, you *also* must take care when cloning > > or copying these repositories, not to allow anyone else to see the data. > > That seems pretty clear to me... So I am downgrading this to a normal > issue and removing the security tag as the security implications of > running etckeeper are clearly stated from the start.
Also, the next paragraph points out that permissions won't be restored when checking out the repository until etkeeper is run, and further on there are examples of doing checkouts in a mode 700 parent directory to avoid leaking information. Smudge filters are an interesting idea, but the current smudge interface does not provide a way to set file permissions. -- see shy jo
signature.asc
Description: Digital signature
