Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 23 replies
  • Answers 3 answers
  • Subscribers 7 subscribers
  • Views 9196 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAF + Let's Encypt

Michael Henkes

Hallo, selbst nachdem ich das alte R3 entfernt habe, das X3 automatisch gelöscht und die UTM neugestartet habe, gibt die UTM WAF (reverse proxy) immer noch den alten Pfad mit aus.

www.ssllabs.com:

Certification Paths
Path #1: Trusted
1 Sent by server xxx.domain.com
Fingerprint SHA256: c6fd72b49484c6124acd17f5bff8d90bf941200e889d67a607511f72ac429dfd
Pin SHA256: thxSHxnuQfCLGcjZzukPDVgDsYMm8Dc7L6KvNWLdB2I=
RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server R3
Fingerprint SHA256: 67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
Pin SHA256: jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0=
RSA 2048 bits (e 65537) / SHA256withRSA
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=
RSA 4096 bits (e 65537) / SHA256withRSA
Path #2: Not trusted (invalid certificate [Fingerprint SHA256: 0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739])
1 Sent by server xxx.domain.com
Fingerprint SHA256: c6fd72b49484c6124acd17f5bff8d90bf941200e889d67a607511f72ac429dfd
Pin SHA256: thxSHxnuQfCLGcjZzukPDVgDsYMm8Dc7L6KvNWLdB2I=
RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server R3
Fingerprint SHA256: 67add1166b020ae61b8f5fc96813c04c2aa589960796865572a3c7e737613dfd
Pin SHA256: jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0=
RSA 2048 bits (e 65537) / SHA256withRSA
3 Sent by server ISRG Root X1
Fingerprint SHA256: 6d99fb265eb1c5b3744765fcbc648f3cd8e1bffafdc4c2f99b9d47cf7ff1c24f
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=
RSA 4096 bits (e 65537) / SHA256withRSA
4 In trust store DST Root CA X3   Self-signed
Fingerprint SHA256: 0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
Pin SHA256: Vjs8r4z+80wjNcr1YKepWQboSIRi63WsWXhIMN+eWys=
RSA 2048 bits (e 65537) / SHA1withRSA
Valid until: Thu, 30 Sep 2021 14:01:15 UTC
EXPIRED
Weak or insecure signature, but no impact on root certificate

Lösche ich das aktuelle R3 aus der UTM, wird der Pfad nicht mehr mit ausgegeben aber verschieden Endgeräte können keine vertrauenvolle Verbindung mehr aufbauen.

Hat dazu jemand eine Lösung ohne die Endgeräte einstellen zu müssen?



This thread was automatically locked due to age.
Parents
  • 0

    Mein Ticket diesbezüglich ist jetzt beim Sophos DevOps Team

    Dear Sophos Customer,

our Development team has informed us that the processing of the bug ID is unfortunately still delayed.

GES expects a status update now in calendar week 23.

We apologize for the delay.

  • 0 in reply to Michael Henkes 

    Hello,

Development has confirmed this as a Bug. Fix will be available in the next release.

Regards, 

Sophos Global Escalation Support

  • 0 in reply to Michael Henkes

    Na, wenn das nächste Release so lange auf sich warten lässt, wie der gefixte Sophos Connect Client ....

    Der wurde mir vor mehr als 3 Monaten als Lösung für einen Case "versprochen" ... (und dann natürlich der Case wegen Inaktivität geschlossen)


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte 

    Development reference number: 
NUTM-13504

Current Status:
Assigned to release

Issue type:
Defect

Your issue with the above reference number has been assigned to a release.

Current plans are to include this fix as part of 9.7MR12 and release the fix by Q3 2022.  Should it be delayed, we will inform you accordingly.

Reply
  • 0 in reply to dirkkotte 

    Development reference number: 
NUTM-13504

Current Status:
Assigned to release

Issue type:
Defect

Your issue with the above reference number has been assigned to a release.

Current plans are to include this fix as part of 9.7MR12 and release the fix by Q3 2022.  Should it be delayed, we will inform you accordingly.

Children
Unfiltered HTML