MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  September 2015

MSUNAG September 2015

Subject:

Re: Eudora problem -- solved!

From:

"Kwiatkowski, Nicholas" <[log in to unmask]>

Reply-To:

Kwiatkowski, Nicholas

Date:

Thu, 24 Sep 2015 21:06:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (109 lines)

Speaking personally -- I don't represent IT Services, nor do I work for them...

I think the wording of "Support" will never really be announced.  If a client is officially supported then the expectation is that there will be documentation, testing and technical assistance given if something went wrong.  It also means that when things like certificates are rotated then we notices will need to be made, etc.  I don't see that happening.

Will it work, given the user does the work-around?  It should.  But to have the expectation that a client that the vendor gave up support on 10 years ago should still be supported is a bit much.  If you take a look at the top 5 desktop clients out there, Eudora won't be on that list.  I think it's reasonable to support the top 5, and allow users to use any client they want -- provided they know that support is only provided for the most popular clients.

-Nick
________________________________________
From: David McFarlane [[log in to unmask]]
Sent: Thursday, September 24, 2015 2:37 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] Eudora problem -- solved!

Nick,

Thanks much, thats a great explanation.

A couple comments ...

First, did you really mean "conical names", or should that read
"canonical names"?  Google could not find anything on "conical names".

Second, if it's just a matter of manually importing/trusting the
certificate from Office 365 when it comes, then Office 365 *does*
support Eudora to the same extent that our current system does, and
users may happily go along with their beloved Eudora even when we
switch over, as long as they do not mind the manual management from
time to time.

I have other issues to discuss, but I will start a new thread for that.

-- dkm


At 9/24/2015 01:11 PM Thursday, Kwiatkowski, Nicholas wrote:
>Eudora's TLS/SSL support does not support conical names, nor does it
>know about some of the new Certificate Authorities that now
>exist.  Conical Names: It used to be that if you issues an SSL
>certificate, you could only issue it to one domain name, and you had
>to dedicate an IP address to that domain name.  The functionality
>wasn't really built into the SSL/TLS standard until about 10 years
>ago, and really wasn't widely supported until about 5 years
>ago.  Services like Microsoft's Office 365 have thousands of domains
>hosted by one IP address.  They use a single SSL certificate for the
>domains hosted on that IP, and list all the domains in the conical
>field in order for everything to work right.   Eudora does not
>support this function and only "sees" the first domain name on the
>certificate.  If it does not match the URL/Server Name that was
>entered, the client will reject the connection. With new CAs --
>every year new root Certificates are added to the "realm of trust",
>either because old ones expire (or get close to expiring), or there
>are new companies out there that are issuing Certificates.  For
>example, if you bought an SSL certificate in 1996, it was signed by
>the root "Network Solutions" certificate they used for all their
>customers.  That certificate was valid until 2011.  If you were to
>buy a new SSL certificate today, it would be signed by "User Trust
>d.b.a Network Solutions III", which is valid until 2035 (or
>something like that).  The problem is that clients like Eudora
>didn't leverage the operating system to know about these new root
>certificates and instead baked them into the program.  Any
>certificates that were issued utilizing a new root since Eudora last
>updated their internal list won't be listed as valid until you
>import those certificates manually.   Baking in certificates is
>somewhat common for application developers -- but you tend to see it
>in apps that are updated regularly (like Mozilla Firefox and Google
>Chrome).  The issue with Eudora connecting with MSU's systems is
>related to the new CA.  Issues connecting Eudora to O365 will be
>related to both of the above issues.  The fix will be to manually
>import these certificates for both cases -- but do beware that when
>the certificate is updated (either because it is expired or for some
>other reason), you will have to manually import and trust the new
>certificates.  This happens transparently for the rest of the world,
>but since Eudora won't trust these new ones it will have to be done
>by hand. -Nick ________________________________________ From: David
>McFarlane [[log in to unmask]] Sent: Thursday, September 24, 2015
>11:54 AM To: [log in to unmask] Subject: Re: [MSUNAG] Eudora
>problem -- solved! Yay!  It eventually worked for me too!  In my
>case, I had to go 8 layers deep, with multiple restarts.  The final
>cert from East Lansing goes through 3 different Certificate
>Authorities, including ones in Ann Arbor and New Jersey.  Seems like
>generally suspicious behavior, Eudora is right to reject this
>nonsense, shame on all the other clients! This nonsense only took
>away 1 hour of my work day, with three calls to MSU Help
>Desk.  Still waiting for details on why exactly the upcoming mail
>system will not work with an ordinary POP3 client like Eudora.  I
>would gladly update to a newer, "supported" POP3 client, as long as
>it was not Outlook, Thunderbird, or Eudora OSE.  Anybody have any
>ideas? Thanks, -- dkm (replying using Eudora, so my name should
>definitely show correctly now!) At 9/24/2015 11:30 AM Thursday,
>STeve Andre' wrote: >Thanks to Chris for this link.  It has indeed
>fixed the problem.  The key >to this is remembering the chain here,
>such that you have to go multiple >levels to fix the problem (trust
>the cert). > >I thank you all for the help. > >--STeve Andre' > >On
>09/24/15 07:32, Chris Wolf wrote: >>This will probably fix the
>problem: >>http://blog.timeoff.org/rick/2015/09/09/revisiting-eudora-
>ssl-certificate-fa >>ilures/ >> >>I used this a month ago to fix the
>same type of certificate problem with >>Comcast servers, and I'll be
>trying it shortly with the current MSU
>problem. >> >> >>-----Original Message----- >>From: STeve Andre'
>[mailto:[log in to unmask]] >>Sent: Thursday, September 24, 2015 12:48
>AM >>To: [log in to unmask] >>Subject: [MSUNAG] Eudora
>problem >> >>So, for my anniversary of starting at MSU, I get a
>present of Eudora not >>working, owing to a expired certificate.  I
>don't think I have any Eudora >>users working at the
>moment. >> >>There is a tech base article tb158 which didn't work
>for me. >> >>Has anyone else crashed into this problem and how was
>it fixed? >>I can enter what I'm seeing tomorrow.  Right now I'm
>about to fall down. >>;-) >> >>--STeve Andre'

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager