[2355] in Enterprise Print Delivery Team
Re: Pillage Certificate
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Sat Mar 2 17:52:30 2002
Mime-Version: 1.0
Message-Id: <p05010400b8a705dc83bd@[192.168.1.101]>
In-Reply-To: <5.0.2.1.2.20020302160628.02d23780@hesiod>
Date: Sat, 2 Mar 2002 17:52:27 -0500
To: "Lynne E. Durland" <durland@MIT.EDU>, "Peter B. Kelley" <kelley@MIT.EDU>,
ipm-cm@MIT.EDU
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Cc: printdel@MIT.EDU
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hello Everyone,
What Peter installed on Saturday was the MIT client trusted root (a
special certificate that lives on the server and validates the MIT
client certificates that live in our Browsers). I suspect that this
trusted root is performing just fine and will continue to be valid
until August as Jeff Schiller explained during his ITAG Seminar. I
think that what has actually expired is the Pillage server
certificate (the one signed by the MIT server trusted root) that
identifies Pillage to our web browsers. Jeff Schiller generally sets
them up to expire after 1 year when he digitally "signs" them. I
will confirm this shortly.
Rocklyn
-------
At 4:10 PM -0500 3/2/02, Lynne E. Durland wrote:
>Peter,
>
>Since I do not know enough about certificates to truly answer that
>question, I will respond with one:
>
>Is the expired certificate still encrypting the information?
>
>If the answer to the above question is no, then yes this is a major priority!!
>
>If the answer to the above question is yes then it could wait until
>Monday, in my opinion.
>
>Sorry for the delayed response I just got home from the cape.
>
>Lynne
>
>At 10:12 PM 3/1/2002 -0500, Peter B. Kelley wrote:
>>Lynne,
>>
>>Just to validate what I read here... it appears that the
>>certificate has expired, but by clicking the continue button, you
>>can access pillage per usual. Just trying to understand the
>>priority of this situation and whether it's an "inconvenience", or
>>a "show-stopper". thanks, Pete
>>
>>
>>
>>
>>At 07:55 PM 3/1/02 -0500, Lynne E. Durland wrote:
>>>Peter,
>>>
>>>We are getting an error message when first attempting to access
>>>https://pillage.mit.edu.
>>>
>>>The text of the message enclosed in a box:
>>>
>>>Certificate Is Expired
>>>
>>>
>>>pillage.mit.edu is a site that uses encryption to protect
>>>transmitted information. However
>>>the digital Certificate that identifies this site has expired.
>>>This may be because the
>>>certificate has actually expired, or because the date on your
>>>computer is wrong.
>>>
>>>The certificate expires on Wed Feb 27, 2002.
>>>
>>>Your computer's date is set to Fri Mar 01, 2002. If this date is
>>>incorrect, then you should
>>>reset the date on your computer.
>>>
>>>You may continue or cancel this connection.
>>>
>>>At the bottom of the box is cancel and continue buttons.
>>>
>>>When we hit the continue button, we can access pillage normally
>>>from that point.
>>>
>>>Dave and I after reading the above message deduced the pillage
>>>server certificate is the one that has expired. Hence the page
>>>this evening. We are figuring this is the certificate you
>>>installed last Saturday noontime.
>>>
>>>Please let us know when the work has been completed,
>>>
>>>Thanks,
>>>
>>>Lynne
>>>
>>>Lynne E. Durland
>>>Information Systems
>>>Database Services
>>>W91-109
>>>O: 617-258-5857
>>>C: 617-293-8091
>>>H: KB1FEM
>>>
>>>"When one door of happiness closes, another opens; but often we
>>>look so long at the closed door that we do not see the one which
>>>has been opened for us."
>>>
>>> --Helen Keller
>>
>
>Lynne E. Durland
>Information Systems
>Database Services Team
>W91-109
>P:258-5857
>E: durland@mit.edu
>H: 603-421-0940
>H: KB1FEM
>
>
>"When speaking to a Bear of Very Little Brain, remember that long
>words may Bother Him."
> --A.A. Milne
