Sender: <marv@lancaironline.net>
To:  lml@lancaironline.net
Date: Fri, 10 Jan 2014 22:51:05 -0500
Message-ID: <redirect-6682782@logan.com>
Received-SPF: neutral
 receiver=logan.com; client-ip=98.138.91.110; envelope-from=ralphlove@stanfordalumni.org
From: Ralph Love <ralphlove@stanfordalumni.org>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [LML] Yahoo
References: <list-6682408@logan.com>
In-Reply-To: <list-6682408@logan.com>

Thanks for telling us what's going on! I have missed about 3 or 4 days LDL

Sent from my iPhone

> On Jan 10, 2014, at 12:19 PM, Rob Logan <Rob@Logan.com> wrote:
>=20
>=20
> mail from our server is sent encrypted as much a possible, but Yahoo's new=
 encryption
> code fails to connect to ours causing email delays to yahoo and other site=
s hoisted by
> yahoo (sbcglobal.net) for now I have turned off encrypted mail until yahoo=
 fully
> implements PFS.
>=20
>=20
> --Yahoo! Mail Now Encrypted by Default
> (January 9, 2014)
> While Yahoo! has at last adopted default HTTPS encryption for Yahoo!
> Mail, the company is facing criticism over its "failure to follow
> industry best practices in rolling out" the encryption. Yahoo! has
> supported full-session HTTPS since 2012, but until now, it has been an
> opt-in feature. Yahoo!'s implementation of HTTPS encryption is not
> consistent across servers and includes flaws that leave it vulnerable
> to snooping. Yahoo!'s implementation of the encryption is missing what
> is known as Perfect Forward Secrecy, which is used by Google, Microsoft,
> and Twitter.
> http://www.computerworld.com/s/article/9245258/Yahoo_email_encryption_stan=
dard_needs_work
> http://www.theregister.co.uk/2014/01/09/yahoo_always_on_crypto_unstrong/
>=20
>                Rob
>=20
>=20
> --
> For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.htm=
l