C. Michael Pilato wrote on Fri, Mar 23, 2012 at 12:21:20 -0400: > But the benefits to the developers will be noticeable. Currently, the use > of the various "outsourced" providers is a mess. Every time we want to add > a new provider, we have to add flavors of it for all the various keyrings > and such. With the master passphrase paradigm in place, the on-disk cache > is *the sole cache* for Subversion credentials, and the keyrings have but a
What will the on-disk cache contain? Will it contain the username/password credentials encrypted via the master password somehow? Conversely -- suppose I know the master password, and I have read access to the .subversion/auth/ directory. What is the process for me to obtain the cache password in cleartext, to authenticate to the server with? > single, shared, simple task: store the master passphrase securely. This > may not sound like a big deal, but if you were reading the authn code, you'd > breathe a sigh of relief. > ++1
