News for hackers. Stuff that matters.
Re:.INTERNAL is now reserved for private-use applications by nox101 on Friday August 09, 2024 @08:10PM (#41206437)
What about things like cookies, storage, caching, etc.. If my job has `https://testing.internal` and some company I visit also has `https://testing.internal` ...
Re:.INTERNAL is now reserved for private-use applications by dudus on Friday August 09, 2024 @08:34PM (#41206514)
Great question. I think they leak but this happens regardless.
Re:.INTERNAL is now reserved for private-use applications by kelnos on Friday August 09, 2024 @09:54PM (#41206772)
Presumably you don't trust the CA that signed the certificate on the server at the company you're visiting. As long as you heed the certificate error and don't visits the site, you're fine.
Re:.INTERNAL is now reserved for private-use applications by hsbauauvhabzb on Saturday August 10, 2024 @01:57AM (#41207631)
So we’re back to trusting the user?
Re:.INTERNAL is now reserved for private-use applications by 0l on Saturday August 10, 2024 @06:36AM (#41208583)
Use HSTS, browsers are specifically designed not to let users bypass these.
Re:.INTERNAL is now reserved for private-use applications by hsbauauvhabzb on Saturday August 10, 2024 @07:46AM (#41208816)
Hsts forces encryption, it has no impact on certificate invalidity, at least to my knowledge.
Re:.INTERNAL is now reserved for private-use applications by 0l on Saturday August 10, 2024 @08:43AM (#41209055)
Visit your .internal site -> website uses TLS cert signed by root CA that is preloaded on your device. Succeeds and HSTS flag is set.

Visit other .internal site -> uses TLS cert NOT signed by root CA that is preloaded on your device -> certificate error, and cannot be bypassed due to HSTS.

Re:.INTERNAL is now reserved for private-use applications by thayne on Saturday August 10, 2024 @12:24PM (#41210535)
Now suppose you are a contractor who did some work for company A, then went to do some work for company B, and still have some cookies set from A's internal site.
Re:.INTERNAL is now reserved for private-use applications by thebeardisred on Friday August 09, 2024 @10:42PM (#41206925)
May god have mercy on the person using this in their mobile applications.
Re:.INTERNAL is now reserved for private-use applications by mrkstu on Friday August 09, 2024 @11:11PM (#41207033)
I'm assuming you wouldn't import their CA as authoritative just to use their wifi...
Re:.INTERNAL is now reserved for private-use applications by fulafel on Saturday August 10, 2024 @01:17AM (#41207498)
Yep, ambiguous addressing doesn't save you, same as 10.x IPv4 networks. And one day you'll need to connect or merge or otherwise coexist with disparate uses if it's a common one (like in .internal and 10.x)...
Re:.INTERNAL is now reserved for private-use applications by kevincox on Saturday August 10, 2024 @07:22AM (#41208740)
IPv6 solves this as you are strongly recommend to use a random component at the top of the internal reserved space. So the chance of a collision is quite low.
Re:.INTERNAL is now reserved for private-use applications by pas on Saturday August 10, 2024 @09:22AM (#41209283)
there's some list of ULA ranges allocated to organizations, no?

edit: ah, unfortunately it's not really standard, just a grassroots effort https://ungleich.ch/u/projects/ipv6ula/

Re:.INTERNAL is now reserved for private-use applications by fulafel on Saturday August 10, 2024 @01:06PM (#41210781)
There's usually little reason to use reserved space vs internet addresses, unless you just want to relive the pain of NAT+IPv4. The exception is if you lack PI space and can't copy with potential renumbering.
Re:.INTERNAL is now reserved for private-use applications by ghshephard on Tuesday August 13, 2024 @01:22PM (#41237406)
I've deployed/managed over 25 million production elements in RFC4193 space. These elements ((mostly mesh networking nodes for utilities) ), by definition, should never route to the internet. (According to NERC CIP they shouldn't even route beyond the substation for distribution elements).

Non routability was a design feature.

I've been out of Enterprise IT for 15 years - but if I was going to do an IPv6 deployment today - I would strongly consider NAT6 prefix replacement - it offers 90% of the benefits of native IPv6 addresses, doesn't conflate "security" and "flexibility" (prefix replacement is just a straight 1:1 passthrough - globally routable) - and who want to go update all their router configs and DNS every time they change their upstream. Ugh.

Re:.INTERNAL is now reserved for private-use applications by viraptor on Saturday August 10, 2024 @03:57AM (#41208027)
Ideally, you use "testing.company-name.internal" for that kind of things. (Especially if you think you'll ever end up interacting at that level)
Re:.INTERNAL is now reserved for private-use applications by mrighele on Saturday August 10, 2024 @10:09AM (#41209643)
I would expect ACME to use https://testing.acme.internal, and not just https://testing.internal, that would remove most of the incidental clashes (not malicious ones, of course).