[Building Sakai] Fixed! Re: ssl cert for source.sakaiproject.org

[Poindexter, David Ray]

Looking good now, thanks!
--
David Poindexter
Systems Analyst
Enterprise Student Systems
UITS
Indiana University
535 West Michigan Street
Indianapolis, IN 46202-5157
O: 317.274.8686
W: http://uits.iu.edu<http://uits.iu.edu/>

From: Neal Caidin <nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>>
Date: Wednesday, June 19, 2013 2:30 PM
To: Cris J Holdorph <holdorph at unicon.net<mailto:holdorph at unicon.net>>
Cc: Sakai Dev <sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>>
Subject: [Building Sakai] Fixed! Re: ssl cert for source.sakaiproject.org

Hi All,

Thanks to Sam Ottenhoff, Matt Jones, and Anthony Whyte working very quickly behind the scenes, this is now fixed.

Please say if otherwise. :-)

Cheers,
Neal



On Wed, Jun 19, 2013 at 1:51 PM, Neal Caidin <nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>> wrote:
That's not good! I'll look into the ssl certificate issue (appears to be the root of the problem).

Thanks,
Neal Caidin

CLE Community Coordinator



On Wed, Jun 19, 2013 at 1:28 PM, Cris J Holdorph <holdorph at unicon.net<mailto:holdorph at unicon.net>> wrote:
I was doing some git svn syncing with Sakai this morning at hit this.

git svn fetch --parent
Error validating server certificate for
'https://source.sakaiproject.org:443':
  - The certificate has expired.
Certificate information:
  - Hostname: source.sakaiproject.org<http://source.sakaiproject.org>
  - Valid: from Jun 21 03:20:01 2010 GMT until Jun 19 14:57:11 2013 GMT
  - Issuer: 07969287, http://certificates.godaddy.com/repository,
GoDaddy.com, Inc., Scottsdale, Arizona, US
  - Fingerprint: 34:c5:11:ed:00:74:04:cd:65:85:79:e7:da:da:fb:02:75:bc:a8:d0
(R)eject, accept (t)emporarily or accept (p)ermanently? RA layer request
failed: OPTIONS of 'https://source.sakaiproject.org/svn': Server
certificate verification failed: certificate has expired
(https://source.sakaiproject.org) at /usr/bin/git-svn line 2315

Normally this wouldn't be such a big deal, but I have to do each sakai
module individually, so I do this with a script.  I've tried running a
command once and accepting the certificate permanently, but it appears
"permanent" is only for the duration of the command.

So, two questions.

Is there any chance the ssl certificate on source.sakaiproject.org<http://source.sakaiproject.org> will
be fixed soon?

Does anyone know a flag I can provide to my git svn commands that will
work around this current problem?

---- Cris J H
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"



--
Neal Caidin
Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>
skype: nealkdin





--
Neal Caidin
Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>
skype: nealkdin


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130619/b204e0b8/attachment.html