This is a Feature Proposal Request to support the command line option "no-check-certificate" functionality within the configuration and for a specific remote definition
Background:
Even if the feature "no-check-certificate" is something that you should only use if you really know what your are doing, many people own private NAS devices with often provide WebDAV built in and then mostly have a self-signed certificate (e.g. Synology). It is correct that is is possible to setup those commercial NAS devices with a correct SSL-certificate including a complete valid chain-of-trust. Also the support for Let's Encrypt makes life a bit easer.
Still sometimes it is simply enough to have a encryption based on self-signed certificates and just use it in your daily work with rclone without always having the no-check-certificate flag set on the command prompt.
Would be nice if such an exception can be configured for those remotes, where the user exactly knows what he is doing.
Specially if you do a remote to remote action on which you only want the certificate check being disabled for the one remote which needs it.
I'm aware that the flag can set also as an env but then it is not just activated for a special remote.
Thx and BR,
c-w-e
See also discussion in: