On Fri Sep15'23 04:10:55PM, Ranjan Maitra wrote: > From: Ranjan Maitra <mlmai...@gmx.com> > Date: Fri, 15 Sep 2023 16:10:55 -0500 > To: Community support for Fedora users <users@lists.fedoraproject.org> > Reply-To: Community support for Fedora users <users@lists.fedoraproject.org> > Subject: Re: OT but F38: Cisco SecureClient VPN suddenly stops connecting > since this morning > > On Fri Sep15'23 04:03:16PM, Ranjan Maitra wrote: > > From: Ranjan Maitra <mlmai...@gmx.com> > > Date: Fri, 15 Sep 2023 16:03:16 -0500 > > To: Community Support for Fedora Users <users@lists.fedoraproject.org> > > Reply-To: Community support for Fedora users <users@lists.fedoraproject.org> > > Subject: OT but F38: Cisco SecureClient VPN suddenly stops connecting since > > this morning > > > > Hi, > > > > I have a strange problem, after last night's updates on F38. I am not > > actually sure that that is the cause, but I can no longer get Cisco's VPN > > to work. (I have to use Cisco's SecureClient because of the more "secure" > > 2-factor-authentication required to connect: before that, I used > > OpenConnect for a long time, and did not have a problem till I was forced > > to move to Cisco's version two years ago. I have till date not had any > > issue with Cisco either.) > > > > But that last statement in parenthesis only holds till last night. From > > this morning, I am unable to connect to Cisco's VPN. After logging in, and > > going through 2FA, all of which are successful, I get that: > > > > "Cisco Secure Client was not able to establish a connection to the > > specified secure gateway. Please try connecting again." <Close> > > > > which is on top of: > > > > "The certificate on the secure gateway is invalid. A VPN connection will > > not be established." <Close> > > > > > > Things I have tried: > > > > 1) Trying on a different machine, with an up to date, F38, I have the same > > issue. > > > > 2) Using my wife's F37 machine (possibly not very up to date) and I am able > > to connect on VPN using the same account, so the issue seems to be with me > > and F38. > > > > 3) Back to my F38 machine, I looked at /var/log/report as the connection > > was happening, and got the following, and was wondering if it shows > > anything that is fixable. > > > > After another reject: this time, the file is probably just over 60.001 KB > because of added header, etc information, I put this file at: > > https://paste.centos.org/view/6e50432b >
Downgrading glibc (from 2.37-5 to 2.37-1) gets around the problem (in that I can log on). So, is this is a bug or an enhanced feature that Cisco or the people who control my certificate have not gotten around to? Best wishes, Ranjan _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
