[1245] in Hesiod
Re: [Hesiod] Announce: Hesutils, the Hesiod utilities
daemon@ATHENA.MIT.EDU (David Krikorian)
Thu Mar 18 11:32:59 2021
MIME-Version: 1.0
In-Reply-To: <HE1PR0402MB362840397BE2C6C2C7A77B6081699@HE1PR0402MB3628.eurprd04.prod.outlook.com>
From: David Krikorian <dkk@mit.edu>
Date: Thu, 18 Mar 2021 11:31:16 -0400
Message-ID: <CA+PjyzV4h2TYBSTL332S_bPALjabnomTFiqSJxYEKq+R0EzhAw@mail.gmail.com>
To: JFLF <jflf-gitlab@outlook.com>
Cc: hesiod@mit.edu
Content-Type: multipart/mixed; boundary="===============4194479861808622242=="
Errors-To: hesiod-bounces@mit.edu
--===============4194479861808622242==
Content-Type: multipart/alternative; boundary="0000000000000540be05bdd14cc7"
--0000000000000540be05bdd14cc7
Content-Type: text/plain; charset="UTF-8"
JF wrote:
> I haven't managed yet to get Google to index it (any hint is appreciated)
Have you linked to it from anywhere with more traffic and still publicly
readable?
Dave McGuire wrote:
> I implemented a scheme by which the menu from the Chinese restaurant was
> encoded
> in Hesiod records in our nameserver, using delimited fields in the TXT
> records that
> implemented a linked list in Hesiod records.
What was that comment about "anyone remotely sane"?
:-)
Seriously, though, I wouldn't be at all surprised to learn that one of my
then-colleagues at MIT had done something similar with the menu for Mary
Chung's chinese restaurant in Central Square, Cambridge (the one in
Massachusetts). I used to serve restaurant menus to `finger` clients, but
that had no technical... ("merit" isn't the right word...) cachet.
On Thu, Mar 18, 2021 at 9:46 AM JFLF <jflf-gitlab@outlook.com> wrote:
>
> Hello again Andy,
>
> Apologies for the delay, it took me that long to write up the rest of
> the documentation.
>
> There is a lot more now, and it covers much more ground. And I have the
> two example pages.
>
> I haven't managed yet to get Google to index it (any hint is
> appreciated), so for now you still need the URL:
> https://gitlab.com/jflf/hesutils
>
> Again, feedback / suggestions / mistake reports would be highly
> appreciated.
>
> Thanks!
> JF
>
>
>
>
> On 25/02/2021 14.46, Andy Bennett wrote:
> > Hi,
> >
> >>> It looks great.
> >>> I also have a script called `hesgen` that I wrote years ago but it's
> >>> nowhere near as sophisticated or well written as this one! ...
> >>
> >> Thank you for the kind words! I hope that you won't change your mind
> >> after looking into it more closely. :)
> >
> > It still looks great, although I noticed that he 2 example pages don't
> > seem to exist.
> >
> >
> >> I was going to add that the MIT still have their Hesiod NS
> >> (ns.athena.mit.edu) available over the internet without any security
> >> of any sort. That's the reason why there's an option to block
> >> requests to that NS in the Hesutils configuration file, as
> >> unconfigured clients would send their requests there. But it seems to
> >> have disappeared! I'm only getting a custom SOA with
> >> "HESREQ.mit.edu." as the rname.
> >>
> >> When I started writing those scripts, about 4 years ago, that NS
> >> still answered. So it seems that the changes have happened
> >> comparatively recently. Does anyone know what happened? Are they
> >> still using Hesiod internally, or have they decommissioned their
> >> Hesiod infrastructure entirely?
> >
> > I had noticed that the ns.athena.mit.edu zone was still available a
> > few years ago when I was thinking about GDPR stuff here in the UK.
> > I hadn't noticed that it had since disappeared tho'.
> > Good find!
> >
> >
> > It strikes me that Hesiod + Kerberos are a good design that haven't
> > kept up with advances in cryptography practice. ...and there are lots
> > of projects which are vainly attempting to do similar things over
> > https, etc. They all seem a lot more complex. It'd be nice if Hesiod &
> > Kerberos were up-to-date with security and crypto practices as they
> > otherwise still seem to be best-in-class approaches to the underlying
> > problems.
> >
> >
> >
> >
> >
> >
> > Best wishes,
> > @ndy
> >
>
> _______________________________________________
> Hesiod@mit.edu
> http://mailman.mit.edu/mailman/listinfo/hesiod
>
--0000000000000540be05bdd14cc7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>JF wrote:</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">I haven't managed yet to get Google to index it (any hint i=
s appreciated)</blockquote><div><br></div><div>Have you linked to it from a=
nywhere with more traffic and still publicly readable?</div><div><br></div>=
<div>Dave McGuire wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">I implemented a scheme by which the menu from the Chinese restau=
rant was encoded<br>in Hesiod records in our nameserver, using delimited fi=
elds in the TXT records that<br>implemented a linked list in Hesiod records=
.</blockquote><div><br></div><div>What was that comment about "anyone =
remotely sane"?</div><div>:-)</div><div><br></div><div>Seriously, thou=
gh, I wouldn't be at all surprised to learn that one of my then-colleag=
ues at MIT had done something similar with the menu for Mary Chung's ch=
inese restaurant in Central Square, Cambridge (the one in Massachusetts).=
=C2=A0 I used to serve restaurant menus to `finger` clients,=C2=A0but that =
had no technical... ("merit" isn't the right word...) cachet.=
</div><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Thu, Mar 18, 2021 at 9:46 AM JFLF &l=
t;<a href=3D"mailto:jflf-gitlab@outlook.com">jflf-gitlab@outlook.com</a>>=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hello again Andy,<br>
<br>
Apologies for the delay, it took me that long to write up the rest of<br>
the documentation.<br>
<br>
There is a lot more now, and it covers much more ground. And I have the<br>
two example pages.<br>
<br>
I haven't managed yet to get Google to index it (any hint is<br>
appreciated), so for now you still need the URL:<br>
<a href=3D"https://gitlab.com/jflf/hesutils" rel=3D"noreferrer" target=3D"_=
blank">https://gitlab.com/jflf/hesutils</a><br>
<br>
Again, feedback / suggestions / mistake reports would be highly appreciated=
.<br>
<br>
Thanks!<br>
JF<br>
<br>
<br>
<br>
<br>
On 25/02/2021 14.46, Andy Bennett wrote:<br>
> Hi,<br>
><br>
>>> It looks great.<br>
>>> I also have a script called `hesgen` that I wrote years ago bu=
t it's<br>
>>> nowhere near as sophisticated or well written as this one! ...=
<br>
>><br>
>> Thank you for the kind words! I hope that you won't change you=
r mind<br>
>> after looking into it more closely. :)<br>
><br>
> It still looks great, although I noticed that he 2 example pages don&#=
39;t<br>
> seem to exist.<br>
><br>
><br>
>> I was going to add that the MIT still have their Hesiod NS<br>
>> (<a href=3D"http://ns.athena.mit.edu" rel=3D"noreferrer" target=3D=
"_blank">ns.athena.mit.edu</a>) available over the internet without any sec=
urity<br>
>> of any sort. That's the reason why there's an option to bl=
ock<br>
>> requests to that NS in the Hesutils configuration file, as<br>
>> unconfigured clients would send their requests there. But it seems=
to<br>
>> have disappeared! I'm only getting a custom SOA with<br>
>> "<a href=3D"http://HESREQ.mit.edu" rel=3D"noreferrer" target=
=3D"_blank">HESREQ.mit.edu</a>." as the rname.<br>
>><br>
>> When I started writing those scripts, about 4 years ago, that NS<b=
r>
>> still answered. So it seems that the changes have happened<br>
>> comparatively recently. Does anyone know what happened? Are they<b=
r>
>> still using Hesiod internally, or have they decommissioned their<b=
r>
>> Hesiod infrastructure entirely?<br>
><br>
> I had noticed that the <a href=3D"http://ns.athena.mit.edu" rel=3D"nor=
eferrer" target=3D"_blank">ns.athena.mit.edu</a> zone was still available a=
<br>
> few years ago when I was thinking about GDPR stuff here in the UK.<br>
> I hadn't noticed that it had since disappeared tho'.<br>
> Good find!<br>
><br>
><br>
> It strikes me that Hesiod + Kerberos are a good design that haven'=
t<br>
> kept up with advances in cryptography practice. ...and there are lots<=
br>
> of projects which are vainly attempting to do similar things over<br>
> https, etc. They all seem a lot more complex. It'd be nice if Hesi=
od &<br>
> Kerberos were up-to-date with security and crypto practices as they<br=
>
> otherwise still seem to be best-in-class approaches to the underlying<=
br>
> problems.<br>
><br>
><br>
><br>
><br>
><br>
><br>
> Best wishes,<br>
> @ndy<br>
><br>
<br>
_______________________________________________<br>
<a href=3D"mailto:Hesiod@mit.edu" target=3D"_blank">Hesiod@mit.edu</a><br>
<a href=3D"http://mailman.mit.edu/mailman/listinfo/hesiod" rel=3D"noreferre=
r" target=3D"_blank">http://mailman.mit.edu/mailman/listinfo/hesiod</a><br>
</blockquote></div>
--0000000000000540be05bdd14cc7--
--===============4194479861808622242==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hesiod@mit.edu
http://mailman.mit.edu/mailman/listinfo/hesiod
--===============4194479861808622242==--
