From: Boris Samorodov <bsam@ipt.ru>
Subject: [SOLVED+patch] nnimap doesn't work with: stream gssapi, auth gssapi and SSL/TLS
Date: Wed, 16 Nov 2005 11:58:08 +0300 [thread overview]
Message-ID: <96851839@srv.sem.ipt.ru> (raw)
In-Reply-To: <62932049@srv.sem.ipt.ru>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Hi!
I've posted a bug report to news server, but it seems to be overloaded
by spam. Here is the original message.
On Wed, 16 Nov 2005 01:25:53 +0300 Boris Samorodov wrote:
> Hello Bugfixing Girls and Boys,
[skip]
> As I can see, the main difference is that the latter answer is
> beginning with some error message (the certificate is
> self-signed). But authentication in fact was successful.
Yes. That was the case.
Looking at gnus/imap.el I noticed a code at kerberos4 function dealing
with such messages. Hence, the next patch made gnus happy.
[-- Attachment #2: Patch for imap.el --]
[-- Type: text/plain, Size: 592 bytes --]
--- imap.el.orig Sun Oct 30 23:34:53 2005
+++ imap.el Wed Nov 16 09:55:45 2005
@@ -591,6 +591,13 @@
(while (and (memq (process-status process) '(open run))
(set-buffer buffer) ;; XXX "blue moon" nntp.el bug
(goto-char (point-min))
+ ;; Athena IMTEST can output SSL verify errors
+ (or (while (looking-at "^verify error:num=")
+ (forward-line))
+ t)
+ (or (while (looking-at "^TLS connection established")
+ (forward-line))
+ t)
;; cyrus 1.6.x (13? < x <= 22) queries capabilities
(or (while (looking-at "^C:")
(forward-line))
[-- Attachment #3: Type: text/plain, Size: 172 bytes --]
Is anybody interested in committing the patch?
WBR
--
Boris B. Samorodov, Research Engineer
InPharmTech Co, http://www.ipt.ru
Telephone & Internet Service Provider
next prev parent reply other threads:[~2005-11-16 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 8:54 Boris Samorodov
2005-11-16 8:58 ` Boris Samorodov [this message]
2005-11-16 15:25 ` [SOLVED+patch] " 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=96851839@srv.sem.ipt.ru \
--to=bsam@ipt.ru \
/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).