[7987] in Release_7.7_team
Re: Linerva transition meeting today
daemon@ATHENA.MIT.EDU (Jonathan D Reed)
Wed Jan 29 09:52:07 2014
From: Jonathan D Reed <jdreed@MIT.EDU>
To: Alexander W Dehnert <adehnert@MIT.EDU>
CC: Jonathon Weiss <jweiss@MIT.EDU>,
Alexander Chernyakhovsky
<achernya@MIT.EDU>,
"linerva@mit.edu" <linerva@MIT.EDU>,
"release-team@mit.edu" <release-team@MIT.EDU>
Date: Wed, 29 Jan 2014 14:51:57 +0000
Message-ID: <E7E9997A-0F9C-45A1-9551-7045B0B57931@mit.edu>
In-Reply-To: <4C13BC47-CABA-4365-B333-0287A0A89B7A@mit.edu>
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_E7E9997A0F9C45A195517045B0B57931mitedu_"
MIME-Version: 1.0
--_000_E7E9997A0F9C45A195517045B0B57931mitedu_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
On Jan 29, 2014, at 9:13 AM, Jonathan D Reed <jdreed@MIT.EDU<mailto:jdreed@=
MIT.EDU>> wrote:
On Jan 29, 2014, at 5:02 AM, Alex Dehnert <adehnert@MIT.EDU<mailto:adehnert=
@MIT.EDU>> wrote:
Linerva crashed this evening, so we decided to do the transition early.
Documentation of the change is at http://web.mit.edu/linerva/www/. In the p=
rocess of writing that, I noticed some lacking documentation that I would h=
ave liked to link to:
- Why doesn't athena.dialup work with ssh -k (there's okay docs on how to u=
se ssh -K instead, but I'd love to have something to link to for the "why" =
behind the "no" answer to "Can I use athena.dialup without delegating my ti=
ckets?=94
Let me think about where the right place to put that is.
OK, I added an info block on the top of the ssh -K article, which is alread=
y linked. So if you want to remove the =93please ask linerva@mit.edu<mailt=
o:linerva@mit.edu>=94 part about public-key and link to the new article bel=
ow, we should be done.
- How can I use ssh public key authentication on athena.dialup? https://ath=
ena10.mit.edu/trac/ticket/1216#comment:11 explains how to do it, but is als=
o clear that there should be some text about the issues with it. I'm not re=
ally able to write that text at 4AM, and in any case I would prefer somebod=
y appropriate at IS&T write text they like, rather than me trying to guess.
Here, have a skeleton article. I=92ll flesh it out later, specifically to =
include setting up _new_ key pairs (do we want to issue recommendations abo=
ut keysize (4096?) or preferred algorithm?)
http://kb.mit.edu/confluence/x/qz4YCQ
-Jon
--_000_E7E9997A0F9C45A195517045B0B57931mitedu_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <82024CEA08AD8E4085F4A776B2B0D249@exchange.mit.edu>
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<br>
<div>
<div>On Jan 29, 2014, at 9:13 AM, Jonathan D Reed <<a href=3D"mailto:jdr=
eed@MIT.EDU">jdreed@MIT.EDU</a>> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<br>
<div>
<div>On Jan 29, 2014, at 5:02 AM, Alex Dehnert <<a href=3D"mailto:adehne=
rt@MIT.EDU">adehnert@MIT.EDU</a>> wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">Linerva crashed this evening, so we decided to do=
the transition early.<br>
<br>
Documentation of the change is at <a href=3D"http://web.mit.edu/linerva/www=
/">http://web.mit.edu/linerva/www/</a>. In the process of writing that, I n=
oticed some lacking documentation that I would have liked to link to:<br>
- Why doesn't athena.dialup work with ssh -k (there's okay docs on how to u=
se ssh -K instead, but I'd love to have something to link to for the "=
why" behind the "no" answer to "Can I use athena.dialup=
without delegating my tickets?=94</blockquote>
<div><br>
</div>
<div>Let me think about where the right place to put that is.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>OK, I added an info block on the top of the ssh -K article, which is a=
lready linked. So if you want to remove the =93please ask
<a href=3D"mailto:linerva@mit.edu">linerva@mit.edu</a>=94 part about public=
-key and link to the new article below, we should be done.</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<div><br>
<blockquote type=3D"cite">- How can I use ssh public key authentication on =
athena.dialup?
<a href=3D"https://athena10.mit.edu/trac/ticket/1216#comment:11">https://at=
hena10.mit.edu/trac/ticket/1216#comment:11</a> explains how to do it, but i=
s also clear that there should be some text about the issues with it. I'm n=
ot really able to write that text
at 4AM, and in any case I would prefer somebody appropriate at IS&T wr=
ite text they like, rather than me trying to guess.<br>
</blockquote>
<div><br>
</div>
<div>Here, have a skeleton article. I=92ll flesh it out later, specif=
ically to include setting up _new_ key pairs (do we want to issue recommend=
ations about keysize (4096?) or preferred algorithm?)</div>
<div><br>
</div>
<div><a href=3D"http://kb.mit.edu/confluence/x/qz4YCQ">http://kb.mit.edu/co=
nfluence/x/qz4YCQ</a></div>
<div><br>
</div>
</div>
-Jon </div>
</blockquote>
</div>
<br>
</body>
</html>
--_000_E7E9997A0F9C45A195517045B0B57931mitedu_--
