[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: TLS default enabled/disabled?
From:       Michael =?iso-8859-1?q?H=E4ckel?= <Michael () Haeckel ! Net>
Date:       2001-05-20 21:29:12
[Download RAW message or body]

On Friday, 18. May 2001 20:29, Waldo Bastian wrote:
>
> Again, this is an ugly hack which isn't necassery any longer. The URL
> should indicate _what_ you want to fetch, not _how_ you want to do that.
> Use slaveConfig() to specify how. You can then put default values in
> kio_smptrc which will be used unless the application overrides them.

Back on my main computer I had a look at SlaveConfig, however somehow it 
doesn't really fit the needs required for storing information about using TLS 
or not.

At least from the point of view of the user, I would like to add a checkbox 
to for example the IMAP account config dialog which allows to set this option 
for every account as it is possible to check the option for SSL already. This 
appears to me to be the natural way of doing this.

Using SlaveConfig, this fails at least, if the user has two accounts on the 
same server. Ok, usually then TLS is also supported on both accounts, but the 
user might wonder, why the other checkbox also changes, when he actually 
changed only one of them.

Also my imap servers at localhost:143 and localhost:144 do support TLS, but 
my imap server at localhost:145 does not and I don't like to work around this 
problem by using localhost, michael, 127.0.0.1, etc. like required in 
Netscape.
Ok, a not very common situation...

Therefore I currently don't have a better idea, than passing it via the url 
as currently already the SASL method.

Regards,
Michael Häckel

[prev in list] [next in list] [prev in thread] [next in thread]