RFC 8567 "Customer Management DNS Resource Records" defines some interesting DNS RRtypes, including CREDITCARD and PASSWORD.

[gumnos@mastodon.bsd.cafe]

@jpmens

at what point does this just become LDAP-over-DNS?

[ben@bluetoot.hardill.me.uk]

@jpmens SSN? so 100% US centric way to do distributed identity theft?

OK, I'll admit I've only skimmed the ToC so far, but errrr, what?

[zhenech@chaos.social]

@jpmens Where else but in a database you'd store these?

[badsamurai@infosec.exchange]

@jpmens I now know my April 1st feature requests to Route53 and UltraDNS.

[jpmens@mastodon.social]

@ben hint: look at the date of the RFC

[gregr@mamot.fr]

@jpmens
> 1 April 2019
#captainItsFridayReading

[hyc@mastodon.social]

@gumnos @jpmens was just thinking the same thing. Funny, since DNS on LDAP is already a thing...

[miekg@mastodon.nl]

@jpmens @ben damn no iana code points allocated... missed oppertunity

[ben@bluetoot.hardill.me.uk]

@jpmens Bah, there is another 2 weeks before that stuff

[paul_ipv6@infosec.exchange]

@jpmens

"putting a password into a protocol designed to be published. bold move, Cotton, let's see if it pays off for them. or for the phishers/scammers..."