Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: secnews.netscape.com?
Date: 09 May 2001 21:30:11 +0200	[thread overview]
Message-ID: <ilu66fatj5o.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <q6mn18nmnwk.fsf@spartacus.utdallas.edu> (Amos Gouaux's message of "08 May 2001 18:17:15 -0500")

Amos Gouaux <amos+lists.ding@utdallas.edu> writes:

> Well, this was interesting.  I looked in the ding archive and
> noticed the maintainer of w3 stating that ssl-program-arguments
> shouldn't be modified.  Something about "s_client" no longer being
> valid with OpenSSL.

Right, OpenSSL used to ship a binary called `s_client', now it only
ship one binary `openssl' that take old binary names as the first
argument.

> !   (let* ((ssl-program-arguments '("-connect" (concat host ":" service)))
> !   (proc (open-ssl-stream "nntpd" buffer nntp-address nntp-port-number)))
...
> !   (let* ((ssl-program-arguments '("s_client" "-connect" (concat host ":" service)))
> !   (proc (open-ssl-stream "nntpd-ssl" buffer nntp-address nntp-port-number)))
>
> Now I'm able to login to secnews.netscape.com:563 without any problems.

The SSL stuff in nntp.el seem to be written for old OpenSSL, and you
have a new one.  Can you simply remove the line and see if it works?
I don't think nntp.el should mess with internal ssl variables unless
it's required. E.g.:

--- nntp.el.~6.8.~	Sun May  6 02:15:22 2001
+++ nntp.el	Wed May  9 21:28:48 2001
@@ -920,8 +920,7 @@
   (open-network-stream "nntpd" buffer nntp-address nntp-port-number))
 
 (defun nntp-open-ssl-stream (buffer)
-  (let* ((ssl-program-arguments '("-connect" (concat host ":" service)))
-	 (proc (open-ssl-stream "nntpd" buffer nntp-address nntp-port-number)))
+  (let ((proc (open-ssl-stream "nntpd" buffer nntp-address nntp-port-number)))
     (save-excursion
       (set-buffer buffer)
       (nntp-wait-for-string "^\r*20[01]")




  parent reply	other threads:[~2001-05-09 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08  4:49 secnews.netscape.com? Amos Gouaux
2001-05-08 23:17 ` secnews.netscape.com? Amos Gouaux
2001-05-09 17:44   ` secnews.netscape.com? Amos Gouaux
2001-05-09 19:32     ` secnews.netscape.com? Simon Josefsson
2001-05-09 19:30   ` Simon Josefsson [this message]
     [not found]     ` <q6mg0bgu06k.fsf@spartacus.utdallas.edu>
2001-07-28 23:16       ` secnews.netscape.com? Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ilu66fatj5o.fsf@barbar.josefsson.org \
    --to=simon@josefsson.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).