Taz

Fwiw got some good and some bad news (latest == last Windows official patches to date of posting this message (I didn't test insider and I won't test it)), so: latest Windows 11 + KeePass 2.50 WORKS well with TLS 1.3 !!! however latest Windows 10 + KeePass 2.50 has same error as I wrote above :-( so whatever fix the .NET developers pushed to Windows 11 seems to resolve the situation, but not for Win 10 hope this helps someone L

FWIW - Dominik - did tls 1.3 work for you in some testing setup?

So schannel debug wasn't very helpful (it prints only windows system logs, I couldn't find in event viewer keepass app log for those events) I can trace the problem down to calling IOConnection WebRequest request = base.GetWebRequest(address); IOConnection.ConfigureWebRequest(request, m_ioc); I can see the ServicePointManager.SecurityProtocol contains TLS 1.3 , so it does get properly detected from runtime as supported if I try connection over firefox it autonegotiates TLS_AES_128_GCM_SHA256 , 128bit...

So schannel debug wasn't very helpful (it prints only windows system logs, I couldn't find in event viewer keepass app log for those events I can trace the problem down to calling IOConnection WebRequest request = base.GetWebRequest(address); IOConnection.ConfigureWebRequest(request, m_ioc); I can see the ServicePointManager.SecurityProtocol contains TLS 1.3 , so it does get properly detected from runtime as supported if I try connection over firefox it autonegotiates TLS_AES_128_GCM_SHA256 , 128bit...

Paul, I am trying to get to my NAS to latest security standard, hence the effort, same webdav is used for my notes(joplin) which are not encrypted, so ideally if the webdav can be on latest standards Danke Dominik, will get the logs and come back to this thread, I should be smarter then about what is going on, ev. send a patch (though I am not sure if there is some free Visual Studio that could compile your code besides VScode)

Thank you for quick reply Dominik, hmm system.net is 4.8.4084.0 for me ... but then this would mean 2.46 keepass has some issue with latest ciphers (note that latest firefox and joplin don't have any issues with same webdav https endpoint) the server side is webdav on Synology DSM 7.0 (yes, beta, I know) with full chain certificate from let's encrypt/R3 (it uses "modern level" profile, which I expect is using TLS 1.3, but not sure, need logs - https://www.synology.com/en-us/knowledgebase/DSM/help/DSM/AdminCenter/connection_security_advanced...

Hello how can I start keepass portable with .net 4.8 on latest stable Win 10 ? (I have latest updates and version check shows 4.8 is supported, but native images in windows/assembly is only 4.0) My goal is webdav https with TLS 1.3 ... but with current setting it always starts with 4.0 ( NativeImages_v4.0.30319_64 ) can I somehow force it to start with newer so TLS 1.3 can be used? (I tried adding 4.8 to KeePass.exe.config but failed miserably :-) ) thanks in advance for any pointer Lubos