Frank Habicht via db-wg wrote:
>
> so on my self-hosted MTA I got an email [unsure about good intentions,
> thus checking origin] from 82.156.114.62
>
> Whois directed to ripe, ripe said it's iana, iana said it's ripe
Yes, but it's a bit more subtle than that.
I have hacked a bit on FreeBSD's wh
Peter Koch via db-wg wrote:
>
> I'm not sure I understand the proposal.
Me too :-)
> "punycode" is primarily IDNA2003 speak
AFAIK IDNA2008 uses punycode in exactly the same way as IDNA2003.
One of the major changes was to get rid of stringprep.
> How would that system deal with conversion fail
George Michaelson via db-wg wrote:
> As a point of information, APNIC uses cc "ZZ" specifically for
> unallocated and "stub" (outward transferred) records.
>
> ZZ is an ISO3166 assigned code for "unknown"
Which reminds me of some of the more horrible code I have shipped.
FreeBSD's whois client
Nick Hilliard via db-wg wrote:
> Gert Doering wrote on 10/04/2019 09:22:
> >
> > On the server side, yes, please store one-way hashed in
> > a secure fashion.
>
> How though?
RIPE DB API authentication is just password authentication, so you can
just use bcrypt or some other modern unix crypt or
