-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client 4.0.1 full chain signature #2928
Comments
Thanks for the report! |
And again in 4.1.0. |
And again in 4.1.1 :-D |
Seems to be something on your side. The signing hour is exactly the same.
This happens on another machine?
…On Fri, Sep 27, 2024 at 2:36 AM Lukáš Tesař ***@***.***> wrote:
Something must be different...
Looks like CA R36 has no full chain signature when you signing code.
image.png (view on web)
<https://github.com/user-attachments/assets/bb61445a-99a9-4074-a332-35e14efa85d6>
—
Reply to this email directly, view it on GitHub
<#2928 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI7PCXABE2EWFFXW5TEQO3ZYTVEVAVCNFSM6AAAAABMXJDF4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYGQZTKNZYGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Atenciosamente,
Jean Brito.
|
Tried on different machine (Windows Server 2019 Std) and same situation. We don't have direct connection to Internet, so it can't verify online full chain. Version 4.0.0 (and previous versions) still works perfectly which is weird. |
May be something related to the direct connection? I never got a report about this. |
Microsoft Store isn't available. |
Search before asking
Operating System
Operating System Version
Windows 10
It happens on the web browser too?
No, it just happens on the Desktop app
Rocket.Chat Desktop App Version
4.0.1
Rocket.Chat Server Version
6.6.12
Describe the bug
Hello, Could you please sign client version 4.0.1 with full chain certificate, like version 4.0.0? I can't install update because invalid certificate (missing full chain).
How to Reproduce
Try to autoupgrade new version (4.0.1) from version 4.0.0
Describe your Expected behavior
No response
Anything else
No response
Are you willing to submit a code contribution?
The text was updated successfully, but these errors were encountered: