Hi all,
I'm trying to commit 0.41-1 to the svn repository, but can't figure out how to get authenticated. I checked the trunk out ala
svn checkout https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/pd/
and now when trying to commit I get a username challenge. In CVS I was using sourceforge's "ssl" authentification but can't figure out how to get SVN to use that.
Do I have to check the sources out anew using a svnserve: or svn+ssh: URL? I'm not eager to try stuff at random since I'll have to redo all my changes if I check out from scratch.
thanks Miller
Hi Miller, You can use svn commit --username {yourusername} (and optionally if there's trouble --password {password} too).
Also as a general tip you can always type "svn help {command e.g. "commit"}" to check the options on any command (or just svn help for an overview). Cheers Luke
On Feb 12, 2008 4:41 PM, Miller Puckette mpuckett@imusic1.ucsd.edu wrote:
Hi all,
I'm trying to commit 0.41-1 to the svn repository, but can't figure out how to get authenticated. I checked the trunk out ala
svn checkout https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/pd/
and now when trying to commit I get a username challenge. In CVS I was using sourceforge's "ssl" authentification but can't figure out how to get SVN to use that.
Do I have to check the sources out anew using a svnserve: or svn+ssh: URL? I'm not eager to try stuff at random since I'll have to redo all my changes if I check out from scratch.
thanks Miller
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
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?
thanks M
On Tue, Feb 12, 2008 at 04:49:40PM -0800, Luke Iannini (pd) wrote:
Hi Miller, You can use svn commit --username {yourusername} (and optionally if there's trouble --password {password} too).
Also as a general tip you can always type "svn help {command e.g. "commit"}" to check the options on any command (or just svn help for an overview). Cheers Luke
On Feb 12, 2008 4:41 PM, Miller Puckette mpuckett@imusic1.ucsd.edu wrote:
Hi all,
I'm trying to commit 0.41-1 to the svn repository, but can't figure out how to get authenticated. I checked the trunk out ala
svn checkout https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/pd/
and now when trying to commit I get a username challenge. In CVS I was using sourceforge's "ssl" authentification but can't figure out how to get SVN to use that.
Do I have to check the sources out anew using a svnserve: or svn+ssh: URL? I'm not eager to try stuff at random since I'll have to redo all my changes if I check out from scratch.
thanks Miller
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
hi miller, matju, all!
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.
fortunately it is not that complicated. the password is (tada:) your sourceforge-password (with the sourceforge username of course); this is the very same password as the one you are using to log into the bug-tracker.
unlike CVS, svn does not use ssh as backend for encrypted transport. instead it uses http(s) (in our case it _does_ use https, i just mentioned http for completeness); as a consequence, there is no more ssl-key exchange for authentication.
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.
to prevent caching (e.g. because you are on an untrusted machine), you can use the "--no-auth-cache" flag when committing.
gfmasdr. IOhannes
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
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
On 14 Feb 2008, at 19:20, IOhannes m zmoelnig wrote:
Miller Puckette wrote:
(And now I'm hearing that the update didn't fix the problem it was intended to in the first place.
huh? are you referring to pd-0.41-1 or to the svn migration?
He means the patch I committed didn't fix the whole problem. See my recent post on 10.5.1 thread to pd-dev. I'm now testing patches against 0.40 and building Pd.app everytime, to try to debug further. Feel free to take a look at my post and see if you can tell what's wrong.
d
On Wed, Feb 13, 2008 at 11:56:09AM -0500, Mathieu Bouchard wrote:
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)
Cleartext. Do you use Google?
http://www.google.com/search?q=svn+password+cache+security
Second link.
Chris.
------------------- http://mccormick.cx
On Feb 13, 2008, at 2:59 AM, IOhannes m zmoelnig wrote:
hi miller, matju, all!
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.
fortunately it is not that complicated. the password is (tada:) your sourceforge-password (with the sourceforge username of course); this is the very same password as the one you are using to log into the bug-tracker.
unlike CVS, svn does not use ssh as backend for encrypted transport. instead it uses http(s) (in our case it _does_ use https, i just mentioned http for completeness); as a consequence, there is no more ssl-key exchange for authentication.
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.
to prevent caching (e.g. because you are on an untrusted machine), you can use the "--no-auth-cache" flag when committing.
I believe that like CVS, SVN uses other things to handle network communications. It relies on an external webserver to provide http/ https support, and it has a command line version, so you can use ssh with svn if the server is setup for it, I believe it's called "svn +ssh", i.e. svn+ssh://pure-data.svn.sourceforge.net. It just seems that SourceForge doesn't use that kind of setup.
SSH keys are great and quite secure. The idea of password caching kind of sucks (just like with CVS ;) Any word on how (in)secure that password caching is?
.hc
------------------------------------------------------------------------ ----
All mankind is of one author, and is one volume; when one man dies, one chapter is not torn out of the book, but translated into a better language; and every chapter must be so translated.... -John Donne