(*** This bug was imported into bugs.kde.org ***) Package: knode Version: 0.7.1 (using KDE 3.0.1 ) Severity: wishlist Installed from: Mandrake Linux Cooker i586 - Cooker Compiler: gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk) OS: Linux (i686) release 2.4.18-6mdk OS/Compiler notes: KNode should support SNews (NNTP over SSL) using port 563. The only way I can use KNode now is by using STunnel to access a news server that requires SSL. I had looked at Mahogany and Mozilla but those are not satisfactory. Thanks. (Submitted via bugs.kde.org) (Called from KBugReport dialog)
On Thursday 13 June 2002 10:09 oma00215@mail.wvnet.edu wrote: > KNode should support SNews (NNTP over SSL) using port 563. The only way I > can use KNode now is by using STunnel to access a news server that requir= es > SSL. I had looked at Mahogany and Mozilla but those are not satisfactory. Just for my curiosity: whats the reason why you can't live with stunnel? Mathias
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 13 June 2002 14:26 Mathias Waack wrote: > On Thursday 13 June 2002 10:09 oma00215@mail.wvnet.edu wrote: > > KNode should support SNews (NNTP over SSL) using port 563. The > > only way I can use KNode now is by using STunnel to access a news > > server that requires SSL. I had looked at Mahogany and Mozilla but > > those are not satisfactory. > > Just for my curiosity: whats the reason why you can't live with > stunnel? <snip> Apart from that fact that stunnel is too low-level for a User KNode should really start using the NNTP KioSlave which has SSL support already. Marc - -- Marc Mutz <mutz@kde.org> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9CLS23oWD+L2/6DgRAmqeAJ0b8IBjJ5j8eC1bDJyHwQiXZG/vTwCcCGKO jMelT+zQpeL85H5JwXguFhA= =E33O -----END PGP SIGNATURE-----
This is a multipart message in MIME format --61042762-POCO-51606700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have been asked why I can't live with STunnel. I'm using STunnel currently with KNode and I can live with that for the moment. It's a stopgap measure. However I don't like this because: 1) I have to open up a port with STunnel to access the server. 2) I can only start STunnel using the root account to access one SSL NNTP server. Some users might not have this and this would be problematic for people having to use more than one NNTP SSL server. 3) I just feel it would be more elegant if KNode itself supported SSL. The easiest way to do things is to make a SH script to start STUNNEL with the appropriate parameters. -- Support the anti-Spam amendment - Join at http://www.cauce.org/ J. Peter Mugaas oma00215@mail.wvnet.edu on 6/13/2002 http://wvnvm.wvnet.edu/~oma00215/ ICQ Number: 14297043 Finger for PGP Key --61042762-POCO-51606700 Content-Type: text/html Content-Transfer-Encoding: Quoted-Printable <HTML><HEAD> <BASEFONT FACE=3D"Arial" SIZE=3D"3" COLOR=3D"#000000"> </HEAD> <BODY> <div>I have been asked why I can't live with STunnel. I'm using STunn= el currently with KNode and I can live with that for the moment.  = ; It's a stopgap measure. However I don't like this because:</div> <div> </div> <div>1) I have to open up a port with STunnel to access the server.</div> <div>2) I can only start STunnel using the root account to access one SSL N= NTP server. Some users might not have this and this would= be problematic for people having to use more than one NNTP SSL server.</di= v> <div>3) I just feel it would be more elegant if KNode itself supported SSL.= The easiest way to do things is to make a SH script to start STUNNEL= with the appropriate parameters.</div> <div>-- </div> <div>Support the anti-Spam amendment - Join at <a href=3D"http://www.cauce.= org/">http://www.cauce.org/</a></div> <div>J. Peter Mugaas oma00215@mail.wvnet.edu on 6/13/2002</div> <div><a href=3D"http://wvnvm.wvnet.edu/~oma00215/=A0">http://wvnvm.wvnet.ed= u/~oma00215/ </a>; ICQ Number: 14297043</div> <div>Finger for PGP Key</div> </body></html> --61042762-POCO-51606700--
Sourceforge ships with a SSL encrypted News server and it would be great if KNode could allow to use it, handling SNews.
*** Bug 21443 has been marked as a duplicate of this bug. ***
Why isn't this on the feature list for 3.2 or at least 3.3? Konqueror and KMail handle SSL versions of their protocols. It seems weird that I have to pop open Mozilla to read NNTP posts on SourceForge. And the stunnel suggestion, although a technical fix, is just plain weird. I don't want to explain stunnel to my mom.
People, please! This is 2005! Am I really expected to blow my password in clear over the network in order to read news?
nttps:// has existed for so long, is there a reason knode can't use it?
Any news about this thing? Could the dev's please explain _why_ ssl is not possible.
It is an important feature for me (and many people working with secure-crazy administators): my University News (EPFL) are protected by SSL and I do not want to open Thunderbird just for that.
I don't think that your admin is secure-crazy. If you have a campus with wlan and DON'T have WPA, you can't allow non SSL connections. Everbody can sniff your password. Because you just have one password for the campus this is a bad thing. On the other side you can't just use wpa, because many users do not yet have (hardware side) support for this stronger encryption. SSL is the only secure way...
N.B. WPA or VPN on the campus... SSL is needed in every case (even if now it works without, it should'nt). I acceed to Newsgroups from home. Therefor is SSL intelligent and needed, no?
Is anyone maintaining Knode? There was no response to this bug for over a year now, and it's still unresolved (NEW, rather). I would really appreciate it if Knode did support Snews, so that we have a simple graphical interface for connecting to encrypted news servers without having to go through the technical STunnel stuff. Perhaps the Devs are working on the KDE4 version and have no time to fix this?
Implemented for KDE4.0.
Fantastic!
Yep. Fantastic !