Version: (using KDE KDE 3.3.2) Installed from: Debian testing/unstable Packages When I read an article from the feed https://update.mozilla.org/rss/?application=firefox&type=E&list=newest I am asked to accept a certificate of the https-page, I answer to accept it permanently, but that does not work. I am asked again, when i read the feed again, after restart.
Please retest with KDE 3.4, and if still problems, open a bug against kio/kssl.
I have now KDE 3.4. The problem still exists. Do I have to file a new bug or can you reasign it to kio/ksll?
Confirmed on KDE 3.4.
Hmmhmm. I just checked the KSSL control module, changed a few things here and there (mostly tried to remove entries in the authentication page, set the default action to "Don't send") pressed Apply and now I can't reproduce the problem anymore. Unfortunately I don't have the old configuration files anymore, so I can't exactly tell the cause.
Mark: do you have the same scenario as Carsten where changing or wiping out your settings fixes it? There should be no difference between akregator and konqueror for this.
Retesting with KDE 3.4.2 (this time, Konqueror), I notice that the problem actually persists. The setup is this: I open https://intern.first.fhg.de, which is an alias to list.first.fhg.de The certificate is for space.first.fhg.de, which also is an alias to list.first.fhg.de It looks like kssl only saves the certificate's hostname, that is, space.first.fhg.de, looks for a certificate for the entered hostname (intern.first.fhg.de) and doesn't find anything, therefore keeps asking the user.
Still present w/ KDE 4.13.3