Description of problem:
I would like to connect to a private FTPS server with a self-signed certificate (official certificate from let's encrypt not possible, since my server is on a private local IP address). But this is not a possible without a prompt asking me to confirm I would like to do this.
Version-Release number of selected component (if applicable):
The certificate have been added to the list of trusted certificates using this guide:
Caja refuses to connect to this server without displaying a prompt asking me if I agree to connect to a server with an "unknown certificate authority".
This is quite a problem, since I use this server as a destination for my duplicity automatic backups. Duplicity would not perform automatic backup in such a case !
I absolutely need automatic connection to this server without interactive prompt.
This procedure used to work perfectly however in previous releases of Fedora (not sure, but I think it ceases working in fedora 28...).
You like to have a code change. Than you should ask upstream.
Created attachment 1699080 [details]
I've got no answer from upstream for almost two months...
Anyway, I've found that the bug is not specific from caja: I get the exact same prompt with nautilus (see attachment).
Thus I think the bug comes from a library, probably in gnome, both used by caja, nautilus or deja-dup.
Could you please help find this library so that I shall submit the bug in the right place ?
Thanks in advance.
It is used by most file-managers.
Summary Backends for the gio framework in GLib
Description The gvfs package provides backend implementations for the gio framework in GLib. It includes ftp, sftp, cifs.
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 31 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.