Where to manage the most sensitive content that you use when managing versions?

Question

Are there any version control systems to indicate security restrictions at the line level, and not at the file level? I know that it would be terrible to support. If I wanted to never allow certain rows in the database, should I study the concept of hooks and manage all the very sensitive information in this hook layer? How to intercept hooks from system to system?

Update: Perhaps the best way to handle this is with pgp encryption of sensitive data, and those who cannot decrypt it will be left in the dark. Any thoughts on this? This is probably not the best security practice.

Answer 1

We had the same problem, and we decided to solve it by installing a second repository.

This arose when I needed to save configuration management files in version control, which contained sensitive information. It made sense to store sensitive data from our applications there.

We initially used svn externals and git subodules to include sensitive data, but later discovered that it was less problematic to simply connect to a different location.

, . - .

, , - , .

Answer 2

, , (, , ). , .

Answer 3

- , , ?

- , ? , NSA ( ).

, , . , . git diff, - .

Answer 4

Subversion , , .

Answer 5

.