public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Strange behaviour of google certificates.
Date: Thu, 2 Apr 2015 11:57:26 +0300	[thread overview]
Message-ID: <551d04d3.6a93700a.614c.4814@mx.google.com> (raw)
In-Reply-To: <20150402075240.GB20058@waltdnes.org>

On Thu, 2 Apr 2015 03:52:40 -0400 "Walter Dnes" <waltdnes@waltdnes.org> wrote:

> On Wed, Apr 01, 2015 at 08:19:45PM +0300, Gevisz wrote
> 
> > So, I am using Claws Mail that downloads e-mails from several
> > google mail accounts (all are mine :) and about once or twice
> > in a month get into the situation when Claws asks me to verify
> > and change the google certificates, first in one direction and
> > soon after that (usually during the next downloading of my e-mails)
> > - in another.
> > 
> > The situation is illustrated by the 2 message screenshots that are
> > attached to this e-mail.
> > 
> > The strange thing for me is that, first, the Claws asks me to verify
> > and accept a newer certificate complaing that the old one is in some
> > aspect "bad", and soon after that it complains about a newer
> > certificate and asks me to verify and and accept the older one.
> > 
> > I suspect that it is google that makes something wrong here.
> > 
> > What do you think?
> 
>   The same question came up on the local linux user group here in
> Toronto.  Apparently "pop.gnail.com" is actually 2 servers...
> 
> [d531][waltdnes][~] nslookup pop.gmail.com
> Server:         206.248.154.170
> Address:        206.248.154.170#53
> 
> Non-authoritative answer:
> pop.gmail.com   canonical name = gmail-pop.l.google.com.
> Name:   gmail-pop.l.google.com
> Address: 173.194.192.108
> Name:   gmail-pop.l.google.com
> Address: 173.194.192.109
> 
>   The 2 servers probably have different certificates, which is why you
> get this behaviour.  I suggest going into "apk mode" and putting an
> entry into your hosts file <G>, like...
> 
> 173.194.192.108     pop.gmail.com
> 
>   This will force your system to always use the same server, and avoid
> the re-validation every time you hit the other server from the one you
> used the previous time.

Thank you for your advice. Added that line to my /etc/hosts file.
After that Claws asked to verify the google certificate once again,
but I hope that that was the last time this month and that that madness
with google certificates finally ends. (Because in the last 2 days this
situation repeated at least 20 or more times.)



  reply	other threads:[~2015-04-02  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 17:19 [gentoo-user] [OT] Strange behaviour of google certificates Gevisz
2015-04-01 21:41 ` Mickaël Bucas
2015-04-02  4:43   ` Gevisz
2015-04-02  2:17 ` wabenbau
2015-04-02  4:50   ` Gevisz
2015-04-02  7:52 ` Walter Dnes
2015-04-02  8:57   ` Gevisz [this message]
2015-04-03  6:26     ` bitlord
2015-04-03  6:50       ` Gevisz
2015-04-02 15:57   ` [gentoo-user] " James
2015-04-03  6:53     ` Gevisz

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=551d04d3.6a93700a.614c.4814@mx.google.com \
    --to=gevisz@gmail.com \
    --cc=gentoo-user@lists.gentoo.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