Dealing with SVN cert changes
Infrastructure may change the SSL certificate used for svn.apache.org. Since we use an "https" SVN external, this causes problems: all users of SVN will be presented with a warning like the following:
svn up Fetching external item into 'rulesrc' Error validating server certificate for 'https://svn.apache.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.apache.org - Valid: from Jan 26 14:18:55 2007 GMT until Jan 26 14:18:55 2009 GMT - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US - Fingerprint: a7:a5:3f:1a:ae:bb:98:b2:f3:ec:91:1b:63:29:2d:e8:58:b6:53:28 (R)eject, accept (t)emporarily or accept (p)ermanently? p External at revision 513302. At revision 513302.
This includes various automated scripts. Here's how to update their certs to fix this problem.
Log into spamassassin.zones.apache.org, and issue:
sudo su - release [type password] svn info https://svn.apache.org/repos/asf/spamassassin/trunk Error validating server certificate for 'https://svn.apache.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: svn.apache.org - Valid: from Jan 26 14:18:55 2007 GMT until Jan 26 14:18:55 2009 GMT - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US - Fingerprint: a7:a5:3f:1a:ae:bb:98:b2:f3:ec:91:1b:63:29:2d:e8:58:b6:53:28 (R)eject, accept (t)emporarily or accept (p)ermanently? p External at revision 513302. At revision 513302. exit repeat the above for the automc, updatesd, bbmass and buildbot accounts.