[8117] in Release_7.7_team
Re: locked out of my debathena workstation
daemon@ATHENA.MIT.EDU (Alex Chernyakhovsky)
Sat Mar 14 20:27:04 2015
MIME-Version: 1.0
In-Reply-To: <5504D145.9070302@mit.edu>
From: Alex Chernyakhovsky <achernya@mit.edu>
Date: Sun, 15 Mar 2015 00:26:55 +0000
Message-ID: <CAB18ysprY=QO4OREW5WyXacLP1BjjpU2MaprOhNBYPu=P+2b6A@mail.gmail.com>
To: Alex Prengel <alexp@mit.edu>, Alex Chernyakhovsky <achernya@mit.edu>
Cc: "release-team@mit.edu" <release-team@mit.edu>
Content-Type: multipart/alternative; boundary=089e01537d1e81a7fe051148cabf
--089e01537d1e81a7fe051148cabf
Content-Type: text/plain; charset=UTF-8
I checked on mkc, which is a fully updated alpha workstation (development)
and had no issues.
Workstations take updates automatically, so you may have had the update
happen while you where logged in.
-Alex
On Sat, Mar 14, 2015, 8:24 PM Alex Prengel <alexp@mit.edu> wrote:
> So Jon's reply answers this? But since I was logged in for a week at the
> time the problem started I couldn't have taken an update that might have
> caused this anyway.
>
> A.
>
>
> On 03/14/2015 12:35 PM, Alex Chernyakhovsky wrote:
> > Hi,
> >
> > On Friday, Ben Kaduk moved a new copy of kerberos-config to proposed.
> > I believe that will affect the beta workstations; the notable change
> > is that allow_weak_crypto got turned off. Is your Athena password by
> > any chance still using DES-only? That would explain these symptoms.
> >
> > Sincerely,
> > -Alex
> >
> > On Sat, Mar 14, 2015 at 11:25 AM, Alex T Prengel <alexp@mit.edu> wrote:
> >> Hi,
> >>
> >> I'm suddenly unable to log into my desktop machine (dit.mit.edu),
> debathena
> >> workstation running Precise, since yesterday afternoon. I get
> >> "authentication failure" on a graphical login attempt, a ctrl-alt-f1
> >> terminal login attempt, and ssh attempts from other machines. I'm able
> to
> >> log into other Athena machines, both locally and by ssh without
> problems.
> >> I'm not sure if or when an update might have triggered this as I was
> logged
> >> into the machine continuously since last Monday.
> >>
> >> Has anyone else seen this on beta workstations?
> >>
> >>
> >> Alex
>
>
--089e01537d1e81a7fe051148cabf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">I checked on mkc, which is a fully updated alpha workstation=
(development) and had no issues.</p>
<p dir=3D"ltr">Workstations take updates automatically, so you may have had=
the update happen while you where logged in.</p>
<p dir=3D"ltr">-Alex</p>
<br><div class=3D"gmail_quote">On Sat, Mar 14, 2015, 8:24 PM=C2=A0Alex Pren=
gel <<a href=3D"mailto:alexp@mit.edu">alexp@mit.edu</a>> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">So Jon's reply answers this? But since I w=
as logged in for a week at the<br>
time the problem started I couldn't have taken an update that might hav=
e<br>
caused this anyway.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 A.<br>
<br>
<br>
On 03/14/2015 12:35 PM, Alex Chernyakhovsky wrote:<br>
> Hi,<br>
><br>
> On Friday, Ben Kaduk moved a new copy of kerberos-config to proposed.<=
br>
> I believe that will affect the beta workstations; the notable change<b=
r>
> is that allow_weak_crypto got turned off. Is your Athena password by<b=
r>
> any chance still using DES-only? That would explain these symptoms.<br=
>
><br>
> Sincerely,<br>
> -Alex<br>
><br>
> On Sat, Mar 14, 2015 at 11:25 AM, Alex T Prengel <<a href=3D"mailto=
:alexp@mit.edu" target=3D"_blank">alexp@mit.edu</a>> wrote:<br>
>> Hi,<br>
>><br>
>> I'm suddenly unable to log into my desktop machine (<a href=3D=
"http://dit.mit.edu" target=3D"_blank">dit.mit.edu</a>), debathena<br>
>> workstation running Precise, since yesterday afternoon. I get<br>
>> "authentication failure" on a graphical login attempt, a=
ctrl-alt-f1<br>
>> terminal login attempt, and ssh attempts from other machines. I=
9;m able to<br>
>> log into other Athena machines, both locally and by ssh without pr=
oblems.<br>
>> I'm not sure if or when an update might have triggered this as=
I was logged<br>
>> into the machine continuously since last Monday.<br>
>><br>
>> Has anyone else seen this on beta workstations?<br>
>><br>
>><br>
>> Alex<br>
<br>
</blockquote></div>
--089e01537d1e81a7fe051148cabf--
