From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: IMAP/SSL with gnus
Date: Thu, 08 Aug 2002 21:14:32 +0200 [thread overview]
Message-ID: <ilulm7hrwmf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <873ctp4495.fsf@giotto.sj.ru> (Alexander Kotelnikov's message of "Thu, 08 Aug 2002 22:03:34 +0400")
Alexander Kotelnikov <sacha@giotto.sj.ru> writes:
> SJ> If the remote cert doesn't validate, you won't send your password. If
> SJ> it validates, doesn't this mean you trust the other end, and trust
> SJ> them to handle your password properly? I don't see how IP spoofing
> SJ> can modify this.
>
> Look. Now I do not have any cert on client side and password is sent
> and I am authorised :(
Ah, but you could install the CA/server cert on the client side. This
is safer than viewing the certificate each time, as you would need to
remember the public key to really gain any security.
>>> May be to switch to (nnimap-stream shell) with ssh, but it do not work
>>> for me, may be some tweaking is needed.
> SJ>
> SJ> SSH port forwarding can be recommended.
>
> Is there any working example of configuration?
Run this on your client
ssh -L 1430:yourmailserver:143 yxa.extundo.com
and then connect to port 1430 on localhost with Gnus.
next prev parent reply other threads:[~2002-08-08 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 16:22 Alexander Kotelnikov
2002-08-07 16:34 ` Simon Josefsson
2002-08-07 22:47 ` Alexander Kotelnikov
2002-08-07 23:00 ` Simon Josefsson
2002-08-08 17:16 ` Alexander Kotelnikov
2002-08-08 17:53 ` Simon Josefsson
2002-08-08 18:03 ` Alexander Kotelnikov
2002-08-08 19:14 ` Simon Josefsson [this message]
2002-08-12 18:46 ` Alexander Kotelnikov
2002-08-12 20:51 ` Andi Hechtbauer
2002-08-12 21:14 ` Simon Josefsson
2002-08-12 21:13 ` Simon Josefsson
2002-08-12 21:45 ` Alexander Kotelnikov
2002-08-13 8:37 ` 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=ilulm7hrwmf.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).