News for hackers. Stuff that matters.

A comment on .INTERNAL is now reserved for private-use applications. Parent comment

Re:.INTERNAL is now reserved for private-use applications by kevincox on Saturday August 10, 2024 @07:17AM (#41208724)
Yes, but then you are putting more information into the publically logged certificate. So it is a tradeoff between scope of certificate and data leak.

I guess you can use a pattern like {human name}.{random}.internal but then you lose memoribility.

[ Parent | on HN ]
Re:.INTERNAL is now reserved for private-use applications by 8organicbits on Saturday August 10, 2024 @07:40AM (#41208788)
I've considered building tools to manage decoy certificates, like it would register mail.example.com if you didn't have a mail server, but I couldn't justify polluting the cert transparency logs.
[ Parent | on HN ]
Re:.INTERNAL is now reserved for private-use applications by lacerrr on Saturday August 10, 2024 @07:44AM (#41208805)
Made up problem, that approach is fine.
[ Parent | on HN ]