On Tue, Mar 29, 2011 at 7:41 PM, Jan Danielsson <[email protected]> wrote: > Hmm.. I'm intrigued, but not completely convinced. An ssh/gpg:esque > agent solves the issue of having to re-enter the password, which is > obviously good if one does many operations within a short time-span over > https, but I'm not sure it would be the proper tool to keep track of > which certificates to associate with a particular project. It could > obviously be used for it, but I think it'll lead to unnecessary > complexity in the fossil code.
I think your own proposal answers this question: > To translate the environment variables to something which is more > "fossilic", I'm currently thinking along the lines of adding a new > sub-command "cert": > > $ fossil cert add myfoo --key ~/.certs/my.key --cert ~/.certs/my.crt > --cafile ~/.certs/ca.crt Replace the file paths with cert and key IDs. Now that you have mentioned it, it occurs to me that you might be able to use gpg's agent. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
