Re: HTTP authentication vs. --username and --password

>
> > Second, and I think more importantly, it's easy to write code that will
> > invade another process, scan it's memory for the 401 piece of the header,
> > and come up with the user-id and password, fully exposed, ready for re-use
> > (infact, I've got some code that does this for netscape and IE though I'm
> > unsure if my employer wants me to share this intellectual property-wise).
> > anyway, hopefully these thoughts make the 401 approach less exciting and
> > svn more secure.
> >

Is this implemented as some sort of plugin? Just curious. I never really
considered this approach too carefully.
gat

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 15:44:01 2002