similar to: [LLVMdev] odd svn message

On Mon, Jun 9, 2008 at 1:45 PM, Dale Johannesen <dalej at apple.com> wrote: > Going to check something in I get this, which I've never seen > before....is it is safe to just hit P and go on? > > now what? svn commit config/i386/llvm-i386.cpp > Error validating server certificate for 'https://llvm.org:443': > - The certificate is not issued by a trusted

On 11-06-26 3:37 PM, Criswell, John T wrote: > Dear All, > > It looks like llvm.org is back up again. With an expiredcertificate? When trying to commit I got: Committing to https://llvm.org/svn/llvm-project/llvm/trunk ... Error validating server certificate for 'https://llvm.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate

Hi, I thought I'd set up a nightly tester and ran across the following issues: 1) Checkout is done using https, which causes the following message: Error validating server certificate for 'https://llvm.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: llvm.org -

Dear All, It looks like llvm.org is back up again. -- John T. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110626/7b7bbd8e/attachment.html>

I want Dovecot handling IMAPS. /etc/dovecot.conf: protocols = imaps imaps_listen = * ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem The problem is that Dovecot is not listening on 993 port, or there's something listening on 993, but it does not introduce itself. There's no problem if Dovecot listens on 143 (IMAP). When

Hello, I have a fresh install of puppet 3.2.3. on windows 8. I try to install the iis module (https://forge.puppetlabs.com/simondean/iis) with the command: puppet module install simondean/iis and it gives me *C:\Program Files (x86)\Puppet Labs\Puppet>puppet module install simondean/iis* *Notice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules .* *..* *Notice:

On Jun 9, 2008, at 2:17 PMPDT, Eli Friedman wrote: > On Mon, Jun 9, 2008 at 1:45 PM, Dale Johannesen <dalej at apple.com> > wrote: >> Going to check something in I get this, which I've never seen >> before....is it is safe to just hit P and go on? >> >> now what? svn commit config/i386/llvm-i386.cpp >> Error validating server certificate for

Dear All, The good news is that the new llvm.org SSL certificate is installed and appears to be configured correctly. The bad news is that some machines seem to recognize the intermediate SSL certificate (which is apparently used to sign the SSL certificates UIUC buys starting this year) while others do not. In particular, our internal Linux machines show no errors, while our Macs and

It's the top of chain CA cert, so browsers are being lazy and helpful to humans by (incorrectly, albeit) relying on the existing trust relationship. libcurl (et al) is not nearly as forgiving. On Sat, May 30, 2020 at 5:01 PM peter dalgaard <pdalgd at gmail.com> wrote: > > Odd. Safari has no problem and says certificate expires August 16 2020, but I also see the download.file

On 6/28/11 3:56 PM, John Criswell wrote: > Dear All, > > The good news is that the new llvm.org SSL certificate is installed and > appears to be configured correctly. As a followup to this, I discovered that I was using the MacPorts version of the svn client on our Mac OS X system. Using the svn client in /usr/bin/svn seems to recognize the certificate just fine. The pattern that

On Fri, Jun 23, 2017 at 5:52 PM, Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > It looks like we're already locked out? > > svn: E170013: Unable to connect to a repository at URL ' > https://llvm.org/svn/llvm-project/compiler-rt' > svn: E230001: Server SSL certificate verification failed: certificate has > expired > > And the new URL

Any issues with permanently accepting the intermediate certificate, which I did this morning, when getting the message? Thanks in advance Garrison On Jun 29, 2011, at 12:13, John Criswell wrote: > On 6/28/11 3:56 PM, John Criswell wrote: >> Dear All, >> >> The good news is that the new llvm.org SSL certificate is installed and >> appears to be configured

I've updated the dashboard (https://rud.is/r-project-cert-status/) script and my notifier script to account for the entire chain in each cert. On Sat, May 30, 2020 at 5:16 PM Bob Rudis <bob at rud.is> wrote: > > # A tibble: 13 x 1 > site > <chr> > 1 beta.r-project.org > 2 bugs.r-project.org > 3 cran-archive.r-project.org > 4 cran.r-project.org

> We are investigating if the certificate got updated by UIUC administrators > since they manage the certificates. The certificate was listed as valid from June 9, 2008 so I guess the old one expired? Gr. Matthijs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL:

Hi all, i have had sip TLS with an own signed certificate (using the ast_tls_cert script) running on asterisk-1.8.8 - i then have updated to 1.8.9.3 - and now i get the message "FILE * open failed!" I have already recreated the certificates with the script - but still no luck... Does anyone here know the source of the problem ? best regards, Wolfgang Pichler

Odd. Safari has no problem and says certificate expires August 16 2020, but I also see the download.file issue with 4.0.1 beta: > download.file("https://www.r-project.org", tempfile()) trying URL 'https://www.r-project.org' Error in download.file("https://www.r-project.org", tempfile()) : cannot open URL 'https://www.r-project.org' In addition: Warning

# A tibble: 13 x 1 site <chr> 1 beta.r-project.org 2 bugs.r-project.org 3 cran-archive.r-project.org 4 cran.r-project.org 5 developer.r-project.org 6 ess.r-project.org 7 ftp.cran.r-project.org 8 journal.r-project.org 9 r-project.org 10 svn.r-project.org 11 user2011.r-project.org 12 www.cran.r-project.org 13 www.r-project.org is the whole list b/c of the wildcard cert. On

On 30/05/2020 5:23 p.m., Bob Rudis wrote: > I've updated the dashboard (https://rud.is/r-project-cert-status/) > script and my notifier script to account for the entire chain in each > cert. You never posted which certificate has expired. Your dashboard shows they're all valid, but the download still fails, presumably because something not shown has expired. Hopefully someone

On macOS 10.15.5 and R-devel: > download.file("https://www.r-project.org", tempfile()) trying URL 'https://www.r-project.org' Error in download.file("https://www.r-project.org", tempfile()) : cannot open URL 'https://www.r-project.org' In addition: Warning message: In download.file("https://www.r-project.org", tempfile()) : URL

Hi all. Usually for in-house use and SSL I would just generate a self-signed certificate because most clients either ignore it or only ask the first time the account is configured. In terms of offering the service to our customers is there any value of getting someone like thawte or instantssl to sign a certificate for imaps/pop3s/smtp? Also, is there a configuration directive for dovecot