On Fri, Feb 17 2017, Yuri D'Elia wrote: > When a CertificateFile is provided, do not trust the system store by > default, since this is not the expected behavior for X.509 > certificates.
Please let me know if this is the appropriate way to report a patch, and if there's anything I missed that you want me to fix. If you remember, I suggested this behavior a while ago and I wanted to see the codebase a bit before committing something larger. As for the second patch, I'd like to contribute extended exit status codes. To avoid breaking old scripts, I'd add a new switch (-e/--exit-code or something like it) that changes the meaning of the exit status. I couldn't find something that I could copy (rsync status codes do not make much sense for mbsync), so I came up with this: - 0: no errors, something synced - 1: errors - 2: usage errors - 4: no errors, nothing synced - 8: transient errors, something synced - 12: transient errors, nothing synced It's mostly compatible with the regular exit codes, and you have two bits (3rd/4th) that you can use to mask sync status and transient errors respectively. We already have all the global state required. Exit code 3 is currently used by the crashHandler, which I found out existed only now. I'd honestly remove it (the crashHandler function itself), since even as a developer I really don't like interference when I'm debugging issues, but otherwise we can keep exit(3) as well. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
