At our company we use https to access our subversion system. We do
not have a valid certificate. This results in a message being
printed to stderr that says:
Don't you have the ability to change the script so it doesn't do that?
So, this is usually no big deal - we just enter "p" and then we
never see this thing again.
I think you'd be better off disabling the validation check within the
script, if only as an optional flag.
However, when I am running my script as a CGI, the user that it
runs as is called "www". And apparently "www" is a very sad little
user because he hasn't accepted the fact that this certificate is bad.
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. But the easy/lazy way would
be to simply login as "www" 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 think there's a better third way: stop sending textual feedback
prompts to non-human users. If this were a compiled application, it
might make sense to work around the problem of your script assuming a
human user, but as you apparently have access to the script source,
why not fix it so it can be run without the certificate validation
prompts?
Peace,
Scott
_______________________________________________
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
