[48167] in SIPB-AFS-requests
Re: sipb5 checked back in
daemon@ATHENA.MIT.EDU (Jacob A Morzinski)
Thu Jul 11 14:48:25 2013
From jmorzins@MIT.EDU Thu Jul 11 18:48:24 2013
Return-Path: <jmorzins@MIT.EDU>
Delivered-To: sipb-afsreq-mtg@CHARON.mit.edu
Received: (qmail 22959 invoked from network); 11 Jul 2013 18:48:24 -0000
Received: from mailhub-auth-3.mit.edu (18.9.21.43)
by charon.mit.edu with SMTP; 11 Jul 2013 18:48:24 -0000
Received: from outgoing-exchange-1.mit.edu (outgoing-exchange-1.mit.edu [18.9.28.15])
by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r6BImDrw020140;
Thu, 11 Jul 2013 14:48:13 -0400
Received: from W92EXEDGE6.EXCHANGE.MIT.EDU (w92exedge6.exchange.mit.edu [18.7.73.28])
by outgoing-exchange-1.mit.edu (8.13.8/8.12.4) with ESMTP id r6BIm8JL031902;
Thu, 11 Jul 2013 14:48:12 -0400
Received: from OC11EXHUB7.exchange.mit.edu (18.9.3.19) by
W92EXEDGE6.EXCHANGE.MIT.EDU (18.7.73.28) with Microsoft SMTP Server (TLS) id
14.2.309.2; Thu, 11 Jul 2013 14:47:08 -0400
Received: from OC11EXPO24.exchange.mit.edu ([169.254.1.128]) by
OC11EXHUB7.exchange.mit.edu ([18.9.3.19]) with mapi id 14.02.0309.002; Thu,
11 Jul 2013 14:47:52 -0400
From: "Jacob A Morzinski" <jmorzins@MIT.EDU>
To: Leonid Grinberg <leonidg@mit.edu>
CC: "<sipb-afsreq@mit.edu>" <sipb-afsreq@mit.edu>,
"<sipb-staff@mit.edu>"
<sipb-staff@mit.edu>
Subject: Re: sipb5 checked back in
Thread-Topic: sipb5 checked back in
Thread-Index: AQHOfmW8yOaqTKZJ5kCUjm+IjDHoQJlgFIyA
Date: Thu, 11 Jul 2013 18:47:52 +0000
Message-ID: <6AE61CEC8823FE45A4E44012A924169C2F1C972B@OC11EXPO24.exchange.mit.edu>
References: <CADNtwxdJwZ_hvsyaQ83vcU+dy7zQq2dWnTOtsV1EdKu0wy7vew@mail.gmail.com>
In-Reply-To: <CADNtwxdJwZ_hvsyaQ83vcU+dy7zQq2dWnTOtsV1EdKu0wy7vew@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [18.189.43.58]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BEBA0AC9E169BE4B9165025AD2C5FCC8@exchange.mit.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
It's probably worthwhile to come up with a new canonical password.
-Jacob
On Jul 11, 2013, at 2:37 PM, Leonid Grinberg wrote:
> However, neither kpasswd nor the online form will let me change it back t=
o the original canonical password on the grounds that it"was found in a dic=
tionary of possible passwords and therefore may be easily guessed."
>=20
> Please advise?
> Leonid
