Karl Berry wrote: > I don't have my old checkout any more, but wouldn't we use, e.g., > svn+ssh://k...@svn.savannah.gnu.org/gnueval > to access? > (As shown on https://savannah.gnu.org/svn/?group=gnueval) > > Sorry if that's what you're already saying ...
Yes. Ignoring the mystery of how this could have been working before and moving forward to how it must be done to work with all of our thought put into it now we think it must be ssh:// protocol now. Since we have always used ssh for authentication and authorization. Using ssh from fencepost is inconvenient though due to needing to base private keys on fencepost and if needing to put them into a crontab then one can't encrypt the keys or the crontab won't be able to access them. (There is actually a way to use "keychain" + ssh-agent to do this, and I do this routinely, but it's more complex and complexity is the enemy of simplicity and all of that.) We do operate using fencepost as a trusted location. I presume that should be a safe place to have an unencrypted ssh private key? I'll ask that as a question but that's the direction I think we are headed unless there is another alternative. This is not a direct question for you Karl to answer but just a clarification email of things just discussed. I was only hoping you would have the memory to remember the details that we can't remember. Bob
