Joseph Galbraith wrote:
> Stefan Küng wrote:
>> Molle Bestefich wrote:
>>> Molle Bestefich wrote:
>>>> This sort of raises a question in my mind; is TSVNCache.exe
>>>> thread-safe?
>>>
>>> Also raises another question; perhaps TSVNCache.exe should per default
>>> install as a service when "install for all users" is selected in the
>>> installer.
>>
>> IMHO a bad idea. The cache communicates via named pipes. I'd rather
>> have it run with the same privileges as the current user. Otherwise a
>> user could ask information for files/folder he has no read access to.
>>
>>> I could try and make me a TSVN build environment again and add service
>>> support to TSVNCache. Seeing as it's something I've done before, it
>>> should be relatively simple.
>>
>> Simple, but dangerous and a potential security risk. I'd rather not do
>> it.
>
> An alternative would be to have one instance of the cache for
> each user.
>
> We could qualify the named pipe name (and any other named
> mutexes, events, etc.) with the string-ified user SID for
> example.
The named pipe the cache uses already allows other users to connect to
it. The problem is with Server2003, which doesn't allow this anymore due
to security reasons.
Having multiple instances of the cache isn't really an option either:
users would complain about the memory use.
But with the upcoming 1.4.0 release, you can select to *not* use the
status cache but the old shell overlay implementation (the one TSVN used
before the cache was introduced). That will make the overlays work in
such situations too.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jul 25 20:45:40 2006