From: Ted Zlatanov <tzz@lifelogs.com>
To: gmane-discuss@hawk.netfonds.no
Cc: ding@gnus.org
Subject: Re: Problems entering gmane groups with git gnus
Date: Mon, 17 Feb 2014 09:47:04 -0500 [thread overview]
Message-ID: <87d2ileqzb.fsf@lifelogs.com> (raw)
In-Reply-To: <86txbzdq7b.fsf@dod.no>
On Sun, 16 Feb 2014 16:36:56 +0100 Steinar Bang <sb@dod.no> wrote:
>>>>>> Steinar Bang <sb@dod.no>:
>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>>> I don't run on W32 so I can't confirm this, but please check that the
>>> installed GnuTLS version is the latest before anything else.
>> Then I did
>> (setq gnutls-log-level 1)
>> in the scratch buffer, and tried entering gmane.discuss, and this time
>> it worked.
SB> Today I did (setq gnutls-log-level 1) and it still wouldn't enter any
SB> groups. See error messages below.
SB> I would like one of the following solutions:
SB> 1. The possibility to switch off the attempted upgrade to STARTTLS for
SB> NNTP connections
SB> 2. The possibility to tell GNU-TLS not to be so stringent about
SB> certificate verification
SB> 3. A news.gmane.org cerficate signed with a CA that is acceptable to
SB> GNU-TLS, instead of the self-signed certificate it has today
Could we move this discussion to the Emacs bugs? `M-x report-emacs-bug' please.
Add the log messages you got. I think (1) is possible; (2) is possible
to a degree and planned more fully after the code freeze; and (3) is not
my call.
Thanks!
Ted
next prev parent reply other threads:[~2014-02-17 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:02 Steinar Bang
2013-12-14 17:04 ` Lars Magne Ingebrigtsen
2013-12-14 22:25 ` Steinar Bang
2013-12-15 3:13 ` Lars Magne Ingebrigtsen
2013-12-15 9:27 ` Steinar Bang
2013-12-16 15:21 ` Ted Zlatanov
2014-02-14 15:09 ` Steinar Bang
2014-02-16 15:36 ` Steinar Bang
2014-02-17 14:47 ` Ted Zlatanov [this message]
2014-02-17 17:55 ` Steinar Bang
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=87d2ileqzb.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=gmane-discuss@hawk.netfonds.no \
/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).