...
For many users, this solution is secure enough . because, for instance, there is but a single user on their machine, or there are several users with their own home directories whose filesystem-level permissions don't permit one user to access and read another user's credential caching files. But some Subversion-using companies desire more in terms of password caching. So Subversion also integrates with several other types of external storage mechanisms.
...
Built-in Encryption with a Master Passphrase
...
In theory, Subversion could do something similar, but the short-lived nature of the command-line client means that a user would typically need to provide the master password (or passphrase) as often as they would their repository credentials, rendering the credential cache rather pointless. This approach would only be useful if there was a way to securely persist the master passphrase across command-line client invocations for at least some period of time.
One way to do so would be to use a daemon-based persistence layer (for example, the GPG Agent) to hold the user-provided master passphrase in memory.
...
Subversion could employ built-in encryption
...
protected by a
...
Per-site Password Caching Options
...