OK, I think I straightened my thing out. I hadn't realized that the login/password for getting on the the "trackers" was the same I needed to feed svn. All fine now.
(And now I'm hearing that the update didn't fix the problem it was intended to in the first place. Software development is such a learning experience ...) cheers Miller On Wed, Feb 13, 2008 at 11:56:09AM -0500, Mathieu Bouchard wrote: > On Wed, 13 Feb 2008, IOhannes m zmoelnig wrote: > >Miller Puckette wrote: > >>However, I don't have a password (only ssl auth, if even that > >>exists in the same form) ... anyway to change SVN authentification > >>methods in midstream? > >>And/or should I just get an old-fashioned password from Iohannes? > >unfortunately _i_ cannot give you a password. > > It's very possible that Miller's problem is exactly the same as mine, that > is, just using svn.puredata.info. > > >unlike CVS, svn does not use ssh as backend for encrypted transport. > > That feature of SVN is called "svn+ssh" as a URL protocol component (the > first part before the colon) and we could file a request to SF to have it > added if it hasn't been added yet. > > >rather, subversion caches your password on filesystem (once you have > >entered it correctly), so you don't have to re-enter it again and again. > > Does it cache them in cleartext, or hashed? (md5, sha1, crypt(), whatever) > > _ _ __ ___ _____ ________ _____________ _____________________ ... > | Mathieu Bouchard - t?l:+1.514.383.3801, Montr?al QC Canada _______________________________________________ PD-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
