On Thursday, May 7, 2020 at 4:21:58 PM UTC+2, Michael Cole wrote: > > Hi there, thanks for keeping this project going. I used TortoiseSVN > before git and now I've come full circle with a version control problem > that is better suited to svn than git. > > My users are often new developers and technical non-developers who don't > understand the difference between TortoiseSVN and PuTTY, and that is ok. > > To better support them, I'd like to make a simple settings page in > TortoiseSVN where they can manage their keys: > - create new keys > - paste in existing keys > - copy their public key to paste into a website > > Adding a page to the UI seems like copy/pasting code from another settings > page (please let me know if I'm wrong). > > My questions are: > > - How does TortoiseSVN create it's part of the ssh tunnel. > TortoisePlink? PuTTY? openssl in the code? >
that's all done by the svn library, not TSVN. TSVN only configures the SSH client to be TortoisePlink by default, that's all. > > - Where are the keys stored? I think it goes through TortoisePlink.exe - > can I set the key when making the tunnel so I don't have to mess with > PuTTY's settings? > Plink stores the keys, that's another application. TortoisePlink is just the original Plink compiled and slightly modified so that ugly console window doesn't pop up every time. > > - Can TortoiseSVN (or it's programs) create keys or does it need an > external program? ( (I see \ext\openssl in the repo checkout) > No, TSVN can't create keys. Sorry. you should first start with the svn library (the original subversion code) and see there whether you might be able to reuse some of their code that handles the ssh connection. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/7e4dfbf8-d8f3-4ffb-91b1-108d1f3ceea9%40googlegroups.com.
