Am 05.07.2007 um 21:09 schrieb Brant Sears <email@hidden>:
There are two ways I can think of to solve this. The right way would
be to convince someone that it was important to have a valid
certificate for our subversion server.
Probably correct.
But the easy/lazy way would be
to simply login as "www"
A real UNIX expert can probably explain this in a better way but you
can't login as www because (by default) www has /usr/bin/false set as
its shell. See /Applications/Utilities/NetInfo Manager.app. It's a
security feature. I was refering to a command-line login here but if
you are talking about a GUI login I think that is even less possible.
and accept the certificate permanently which
would solve the problem for the foreseeable future. Unfortunately I
don't know the password for "www". Therefore, I could reset the
password - but would this cause problems for Apache? Or alternatively
I guess I could crack the password, but that might take a while.
I don't think there is a password to crack. And having one would not
help.
I'm still figuring this stuff out myself but maybe adding your
certificate to the System keychain (and the issuer to the
X509Anchors?) and setting the trust values to always trust them might
do the trick.
HTH
Mike
--
Mike Fischer Softwareentwicklung, EDV-Beratung
Schulung, Vertrieb
Note: I read this list in digest mode!
Send me a private copy for faster responses.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
