[1248] in Hesiod
Re: [Hesiod] Announce: Hesutils, the Hesiod utilities
daemon@ATHENA.MIT.EDU (SZE CALVIN)
Fri Mar 19 05:19:11 2021
From: SZE CALVIN <calvinsze@hotmail.com>
To: JFLF <jflf-gitlab@outlook.com>
Date: Fri, 19 Mar 2021 09:18:27 +0000
Message-ID: <MN2PR01MB55187C237A70A348E946F939BC689@MN2PR01MB5518.prod.exchangelabs.com>
In-Reply-To: <HE1PR0402MB362895236A897BF421E388A381699@HE1PR0402MB3628.eurprd04.prod.outlook.com>
Content-Language: zh-TW
MIME-Version: 1.0
Cc: "hesiod@mit.edu" <hesiod@mit.edu>
Content-Type: text/plain; charset="utf-8"
Errors-To: hesiod-bounces@mit.edu
Content-Transfer-Encoding: 8bit
Please remove me from conversation
Thanks&Best Regars,
> JFLF <jflf-gitlab@outlook.com>於2021年3月19日 上午12:45寫道：
>
>
>> On 18/03/2021 16.31, David Krikorian wrote:
>> 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?
>
> I don't have anywhere to link it from I'm afraid. No website, no blog,
> not even a Twitter or Reddit account. And I am not really willing to
> play the game of commenting on random posts here and there just to plug
> my projects.
>
> I tried through the Google Search Console but the methods to "verify
> ownership of the property" don't work with the dynamically-generated
> Gitlab pages.
>
> I guess that I'll have to hope that Google indexes this list's archives!
>
> JF
>
>
>> 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
>> <mailto: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 <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 <http://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 <http://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
>> <http://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 <mailto:Hesiod@mit.edu>
>> http://mailman.mit.edu/mailman/listinfo/hesiod
>> <http://mailman.mit.edu/mailman/listinfo/hesiod>
>>
> _______________________________________________
> Hesiod@mit.edu
> http://mailman.mit.edu/mailman/listinfo/hesiod
_______________________________________________
Hesiod@mit.edu
http://mailman.mit.edu/mailman/listinfo/hesiod
