From: dhruva <dhruvakm@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs and TLS support
Date: Mon, 27 Sep 2010 08:48:22 +0530 [thread overview]
Message-ID: <AANLkTimEifxfcbvA_ew4GHh-nrhudmotKNGxtBb9qquw@mail.gmail.com> (raw)
> From: Ted Zlatanov <tzz@lifelogs.com>
> To: emacs-devel@gnu.org
> Date: Sun, 26 Sep 2010 16:33:04 -0500
> Subject: Re: Emacs and TLS support
> On Sun, 26 Sep 2010 23:06:46 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>
> It would be great if the GnuTLS developers could comment. But these
> references seem to specifically confirm that non-blocking sockets should
> work the way I'm doing it:
>
> http://lists.gnupg.org/pipermail/gnutls-dev/2005-March/000839.html
> http://www.gnu.org/software/gnutls/manual/html_node/The-transport-layer.html
>
> I tried setting the low water value to 0 in `Fgnutls_handshake' after
> `gnutls_transport_set_ptr2' but it didn't make a difference:
>
> gnutls_transport_set_lowat (state, 0);
>
> So I removed it in the patch. I sort of suspect right now that
> recv/send are not working correctly so I need to provide custom versions
> with `gnutls_transport_set_pull_function' and
> `gnutls_transport_set_push_function'. But I don't know enough about the
> Emacs internals that set up processes, which are ridiculously
> complicated because of all the supported platforms. And Simon Josefsson
> said his patch worked when he first wrote it, so I assumed that this
> kind of deep surgery would not be required.
>
Not sure if this is related to the thread. I am having problems using
gnutls to access my company (M$ Exchange) mail using imap.
This used to work ~2 weeks back though. I had not done any specific
setting to use gnutls-client but now I see it barfing with error
(unable to handshake). I did a bit of troubleshooting. I executed the
same program "gnutls-cli" from command line and found same error. I
later installed starttls package and used that to connect from command
line and it worked!
Now, I try to cajole gnus to use starttls, it just refuses to use it
and keeps defaulting to gnutls-cli or openssl. This is when I stopped
and decided to take a break.
If someone can help me use starttls through gnus, I can try to capture
the packets with gnutls-cli and starttls and hope it can throw some
light. Let me try doing that with command line since starttls works
and gnutls-cli does not.
-dhruva
next reply other threads:[~2010-09-27 3:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 3:18 dhruva [this message]
2010-09-27 8:00 ` Emacs and TLS support Lars Magne Ingebrigtsen
2010-09-27 21:52 ` Jason Earl
-- strict thread matches above, loose matches on Subject: below --
2010-09-26 16:11 Angelo Graziosi
2010-09-26 16:22 ` Lars Magne Ingebrigtsen
2010-09-26 21:02 ` Ted Zlatanov
2010-09-26 21:06 ` Lars Magne Ingebrigtsen
2010-09-26 21:33 ` Ted Zlatanov
2010-09-30 10:18 ` Simon Josefsson
2010-10-04 1:27 ` Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimEifxfcbvA_ew4GHh-nrhudmotKNGxtBb9qquw@mail.gmail.com \
--to=dhruvakm@gmail.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).