Christian Thiele wrote:
> Hello,
>
> I haven't found an issue in your tracking system for the enhancement,
> described in the subject of this mail. We use Tortoise on shared
> Windows laptops and so it's of course not possible to save the username/password
> for a repository, because others may use this laptop with the shared
> account, too. So you have to enter your authentification data over
> and over again - sometimes auth windows pop up, which aren't even
> needed. It would be fine, if there would be a possibility, to save
> data only for this windows session or maybe save the last username.
I don't think you will ever find this in our issue tracker.
* caching auth data is done by the Subversion library, not TSVN itself
* you're not only sharing the laptop but also the account on that
laptop, which if I may say so is one of the biggest security sins you
can do.
* define "session" please.
- caching the auth data for as long as a user is logged on? That's
already done - you just need to have different accounts for every
user.
- caching the auth data for as long as TSVN is active? You still would
need to authenticate for every log dialog, every repository browser,
... since those are all separate processes.
- The *server* asks for authentication. The client just passes that
request back to you. And servers are usually set up secure and ask
for authentication for every connection. And since our dialogs often
have to do several connections at once, you're asked each time for
authentication. If you could configure your server to not do that,
then you could just get rid of authentication completely - it would
be as secure.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Jun 13 19:58:56 2007