The amework package that we distribute for macOS now uses the AppleTLS stack for implementing our SSL/TLS transport. I was also trying to follow up on the thought (though I can’t personally add the easy fix).įully implement X509Store and related APIs #7019 has interesting comments on the design in 2018.ĪppleTLS stack is a more recent change (mono v5, minimum requirement for Duplicati 2.0.5.1 Beta): Supply one or more module names, separated by commas to unload themĬ:\ProgramData\Duplicati\duplicati-2.0.5.1_beta_> disable-module (String): Disables one or more modules Module is loaded automatically, use -disable-module to prevent thisĬ:\ProgramData\Duplicati\duplicati-2.0.5.1_beta_> help disable-module Installed and suggest installing them otherwise When running with Mono, this module will check if any certificates are Possibly the reason Duplicati sees little of this is that maybe others downloaded from mono-project.Īlthough you don’t need it now, one other possible workaround to end the noise might be based on: C:\ProgramData\Duplicati\duplicati-2.0.5.1_beta_> help check-mono-sslĬheck for SSL certificates (check-mono-ssl): Possibly brew install mono would be a compile from source. you don’t have access to the Apple TLS implementation), you can use cert-sync to populate the Mono certificate stores with CA certificates from the curl maintainers which are based on Mozilla’s trusted CA list: On Mac if you compiled and installed Mono from source (i.e. I found one about the same time, however I wasn’t sure it was the fix for you, but I’m glad it was… I found a page for Mono support with the fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |