News for hackers. Stuff that matters.
Re:Giving every IPv6 address a name by robbya on Monday December 16, 2019 @12:16PM (#21804743)
This is cool, but keep in mind that the operator can also get SSL certs for your site (they just point the domain somewhere else and use Lets Encrypt or similar to get a certificate). So from a security perspective, you are putting a ton of trust if you use this for anything real.
Re:Giving every IPv6 address a name by gregmac on Monday December 16, 2019 @01:18PM (#21805465)
Also don't use for anything real, because you should not be teaching users that https://1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name is the proper, trusted domain for your service. Because it was supposed to be https://1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name and I just tricked you.
Re:Giving every IPv6 address a name by jandrese on Monday December 16, 2019 @02:26PM (#21806185)
The fundamental problem with this whole scheme is that it is still just trying to memorize the entire IP address. The point of a name is to make it something that feels natural for actual people.

Maybe it would make more sense to choose the 65,536 most common English words (or whatever language you want) and break the address up into 8 words to form a crazy looking phrase. This is still difficult to memorize but not as bad as just stuffing 128 bits of hex down your throat. You could even allow for the collapsing 0s by making entry 0 be "and" and adding a bit of logic that does the collapse.

For fun I wrote a tiny script that does this and tried it with their example domain:

1234:5678:9abc:def0:1234:5678:9abc:def0 -> balcony gaining pawn toothill balcony gaining pawn toothill

Or Google's address from that page:

2a00:1450:4009:811::200e -> chinker bauchle dorter amor and bromidic

So maybe this wasn't the best idea, but at least they're a bit more amusing than the hex noise in the article.

Anyway, if anybody else wants to play around with it I have a tiny demo: http://jubei.ceyah.org/cgi-bin/ipv6toenglish

Re:Giving every IPv6 address a name by gerdesj on Monday December 16, 2019 @04:21PM (#21807330)
Once you really get into IPv6 you tend to find that the addresses are not actually that bad or at least not as bad as you might expect. For starters, your prefix stays the same and probably looks like this 2001:wwww:xxxx::/48 ISP is wwww and your allocation is xxxx. There are lots of ways you can break up your allocation: yyzz. For me yy is the first dot1Q and zz is the second tag. yy = 00 is for single tagged 802.1Q VLANs. I have quite a lot of "spare" space for expansion, VPNs or whatever. So using the https://tools.ietf.org/html/rfc3849 documentation prefix 2001:DB8::/32 - that's my "ISP". Let's say I am :2d1:, I give my routers ::1 ie the first address and therefore on my default VLAN with no tags, I get an address of:

2001:db8:2d1::1 for the router on that VLAN (10.10.0.1)

My DNS servers are on a single tagged vlan 10 (they are 10.10.10.11 and 10.10.10.12):

2001:db8:2d1:a::11 and 2001:db8:2d1:a::12

I wont be using that site or anything like it. DNS does the trick for me along with documentation, just as it does for IPv4. I toyed with ULA addresses (a bit like RFC 1918) but dropped it because it adds complexity. You only need a few addresses to bootstrap a network and a change of ISP will have more hassles to deal with than a prefix change.

Re:Giving every IPv6 address a name by judge2020 on Monday December 16, 2019 @04:29PM (#21807424)
Were you given a /48 for your residential IP, or is that for a business? Residential AT&T in Georgia assigned a /64 for me.
Re:Giving every IPv6 address a name by lokedhs on Tuesday December 17, 2019 @01:17PM (#21816680)
My old ISP gave me only a /64. That's absolutely useless for doing anything more than there most basic of configuration. This seemed to be because of limitations in their own infrastructure as they were using 6rd. I ended up switching ISP's to one that gave me a /48.

I seem to recall general recommendations that ISP's assign at least /56 to customers?

Re:Giving every IPv6 address a name by gerdesj on Monday December 16, 2019 @04:57PM (#21807750)
/48 for work (actually I have six of the bloody things!) and /56 for home which is reasonable. /64 is ridiculous unless they will give you more on request but then why not /56 so you can plan. We really are not going to run out of those and even /48 for all is pretty reasonable. At work I have an additional /64 just for WAN but I understand /112 and the like are popular for that as well.

I suggest you have a play with the /64 just for fun and to get the hang of things but the future has a shed load of IoT in it and all networks will need breaking up into subnets for security, including residential networks. Even if only to separate guest wifi.

In the UK we have the relative luxury of being able to choose from a fairly long list of ISPs. Some of them nearly get IPv6. Funnily enough dear old BT (business) is one of the few that gets it all correct out of the box, when you order a leased line.

You have my sympathies.

Re:Giving every IPv6 address a name by jrockway on Monday December 16, 2019 @08:20PM (#21809543)
/64 is a lot of addresses. That's 2^32 internets.
Re:Giving every IPv6 address a name by jandrese on Monday December 16, 2019 @09:20PM (#21809871)
When you see an IPv6 address mentally block out the last 64 bits. A /64 in IPv6 land is the equivelent of a single public IPv4 address for most practical purposes.
Re:Giving every IPv6 address a name by borumpilot on Tuesday December 17, 2019 @08:20AM (#21813137)
I would prefer to "A /64 in IPv6 land is the equivalent of a single public IPv4/24 for most practical purposes."
Re:Giving every IPv6 address a name by jandrese on Tuesday December 17, 2019 @02:53PM (#21817971)
Back in the 80s or possibly 90s that might have worked, but an experienced admin today will look at a /24 and go "I can support 16 sites with that", whereas a /64 is really the smallest allocation you should see with IPv6, like a single IP address in IPv4.
Re:Giving every IPv6 address a name by darkr on Monday December 16, 2019 @08:37PM (#21809645)
But it’s only a single subnet or point-to-point link, you can’t do anything interesting with that space
Re:Giving every IPv6 address a name by jandrese on Monday December 16, 2019 @04:42PM (#21807573)
Typically it's pretty easy to get an ISP to cough up a /48 if you ask.
Re:Giving every IPv6 address a name by Dagger2 on Monday December 16, 2019 @02:36PM (#21806315)
This scheme isn't designed to make the addresses memorable though. It's designed as a workaround for cases where hostnames are supported but v6 literals aren't, for example in UNC paths to Windows network shares.
Re:Giving every IPv6 address a name by jholloway7 on Monday December 16, 2019 @02:56PM (#21806542)
I don't think they're proposing this for anything other than a prototyping solution along the lines of this:

http://xip.io/

There are cases where you simply want to use a name during development because it generalizes better for the eventual production case, but you don't care what the name is, you don't care if anyone can memorize it, you just need it to be a name and not an IP address.

Re:Giving every IPv6 address a name by rs23296008n1 on Monday December 16, 2019 @11:40PM (#21810641)
I'm guessing you are referring to the "config needs a hostname" problem. Been there myself.
Re:Giving every IPv6 address a name by woolcap on Monday December 16, 2019 @03:25PM (#21806806)
Kinda like https://what3words.com/. Question is, how long would the string of words have to be to enable such a scheme for the entire IPv6 address space?
Re:Giving every IPv6 address a name by bowmessage on Monday December 16, 2019 @04:07PM (#21807203)
Dictionary size of what3words: (57*10^12)^(1/3) ~= 38485 [0]

Number of IPv6 addresses: ~340 undecillion [1]

Length of string of words: ~8.4 [2]

Probably closer to 8 as what3words likely doesn't cover the full 3-word-address-space of the English language.

[0] https://en.wikipedia.org/wiki/What3words#cite_note-16 [1] https://en.wikipedia.org/wiki/IPv6#cite_ref-rfc2460_2-2 [2] https://www.wolframalpha.com/input/?i=log+base+38485+of+340%...

Re:Giving every IPv6 address a name by virusduck on Tuesday December 17, 2019 @12:38PM (#21816113)
I call dibs on Buffalo.buffalo.Buffalo.buffalo.buffalo.buffalo.Buffalo.buffalo
Re:Giving every IPv6 address a name by jandrese on Monday December 16, 2019 @04:07PM (#21807199)
8 words. 128 bit address space and 65k English words gives you 16 bits per word, so you need 8 words to cover the entire space.

My dictionary excludes all proper nouns and all words longer than 8 characters. Only about 60% of the 8 character words were used, chosen completely at random. Even so, given a full IPv6 address the resulting "phrase" is a mouthful. Shortened addresses are a little easier to deal with.

Re:Giving every IPv6 address a name by dheera on Monday December 16, 2019 @06:34PM (#21808752)
One of the biggest things that keeps me using IPv4 is that I can memorize all the IPv4 addresses for most of my servers. That alone is a huge mental hurdle.
Re:Giving every IPv6 address a name by treysis on Monday December 16, 2019 @07:43PM (#21809315)
That just proves you haven't understood IPv6 yet. ULA addresses make it much easier, e.g. fd00::1 or fd00:2 (though this is bad practice, should be fdxy:zvwx:xyzw, xyvwz being random).
Re:Giving every IPv6 address a name by jandrese on Monday December 16, 2019 @09:22PM (#21809888)
I thought this would be an issue when I deployed IPv6 on my home network, but it turns out that I memorized the prefix pretty quick and the host part you mostly end up ignoring.
Re:Giving every IPv6 address a name by IcePic on Tuesday December 17, 2019 @03:45AM (#21811824)
$ host sprint.net

sprint.net has address 208.24.22.50

sprint.net has IPv6 address 2600::

wonder which one is easiest to remember? =)

Re:Giving every IPv6 address a name by Zamicol on Monday December 16, 2019 @03:43PM (#21807005)
Re:Giving every IPv6 address a name by treysis on Monday December 16, 2019 @01:53PM (#21805856)
Same/similar working mechanism is built-in into Windows since Vista: 1234-5678--abcd.ipv6-literal.net This doesn't even need functioning DNS and can work offline (add s<devnumber> for link-local addresses).
Re:Giving every IPv6 address a name by numlock86 on Monday December 16, 2019 @01:44PM (#21805762)
I actually had to look three times before I spotted it. Good one!
Re:Giving every IPv6 address a name by Natfan on Monday December 16, 2019 @01:52PM (#21805837)
In case anyone wants to know the difference it's that the third "section" on the first URL is "9adc" and the third "section" on the second URL is "9abc".
Re:Giving every IPv6 address a name by TallGuyShort on Monday December 16, 2019 @03:19PM (#21806745)
I had to diff it! Even if there was no difference, the time it would've taken to be sure really illustrates the problem.
Re:Giving every IPv6 address a name by dv_dt on Monday December 16, 2019 @07:52PM (#21809386)
It would be interesting if there was even an informal URL extension that was able to specify alternative name resolution protocols. Maybe overload scheme in the url otherns-https://name
Re:Giving every IPv6 address a name by chrisstanchak on Monday December 16, 2019 @05:23PM (#21808054)
Neither of those loaded. Not tricked.

/s

Re:Giving every IPv6 address a name by joosters on Monday December 16, 2019 @12:32PM (#21804940)
Presumably they could just get a wildcard certificate for *.has-a.name perfectly legitimately and then they can mimic every IPv6 has-a.name site they want.
Re:Giving every IPv6 address a name by milankragujevic on Monday December 16, 2019 @12:35PM (#21804963)
Not without the ability to add a TXT record to the root domain.
Re:Giving every IPv6 address a name by joosters on Monday December 16, 2019 @12:42PM (#21805045)
Which root domain? If they own has-a.name then that is good enough, right?
Re:Giving every IPv6 address a name by LeonM on Monday December 16, 2019 @12:47PM (#21805101)
No, they'd have to get a cert for your domain name. Which they can't, because they cannot prove they own your domain name.

All they are doing if pointing to your IPv6 address, anyone can do that, that is why DNS TXT validation if needed in the first place.

Re:Giving every IPv6 address a name by jrockway on Monday December 16, 2019 @08:25PM (#21809569)
ACME is entirely based on DNS. The HTTP and ALPN challenges look up which IP address to speak to via DNS. The DNS challenges look for a TXT record in DNS. (Letsencrypt tries pretty hard to ensure that the DNS is legitimately being served by looking up the IP address from multiple networks, so you can't disrupt one of their networks to issue fake certs. But it has no idea who really controls your DNS server or glue records.)

If you host your site at foo.example.com, then example.com can get a wildcard certificate for *.example.com that will be valid even if you have your own foo.example.com certificate and they can also change the A or AAAA record for foo.example.com to get a certificate with an HTTP challenge.

You could always petition browser vendors to pin your foo.example.com certificate, and thus override any tampering by the example.com DNS server. It is exceedingly unlikely they would do this for you.

TLS certificates these days only prove one thing: control over the DNS server at the time of provisioning.

Re:Giving every IPv6 address a name by MrOxiMoron on Monday December 16, 2019 @12:53PM (#21805160)
whatever.has-a.name is the domain name they are suggesting you use, if you had your own you wouldn't need their service. So yes, you are basically giving them control that way. But for simple solution to temporarily get SSL to work on your container during development it's fine. But in that case a self signed certificate works too.
Re:Giving every IPv6 address a name by LeonM on Monday December 16, 2019 @01:10PM (#21805376)
I haven't looked at it from that angle yet, but you are right: If you share the whatever.has-a.name address with other people and tell them to trust it, then this is very dangerous.

However, the OP wrote this:

> but keep in mind that the operator can also get SSL certs for your site

Which made it sound as if they can get a cert for your domain, which they cannot.

Re:Giving every IPv6 address a name by yzmtf2008 on Monday December 16, 2019 @01:41PM (#21805730)
> Which made it sound as if they can get a cert for your domain, which they cannot.

Why? They own and operate the DNS server for has-a.name, so (if they wish to) they can just add any record that they wish, to any domain, right?

Of course this is true for any registrar, but that's also why not anyone can just become a registrar.

Re:Giving every IPv6 address a name by ownagefool on Monday December 16, 2019 @02:51PM (#21806493)
Obviously if you can sign a cert which is trusted by browsers, then you technically have the ability to impersonate anyone, but processes are used to fight against this.

PSL (https://publicsuffix.org/), DNS Certification Authority Authorization , and Certificate Transparency could be combined so browsers are allowed to know who can sign what, who's a registrar, and who's doing what.

Re:Giving every IPv6 address a name by yzmtf2008 on Monday December 16, 2019 @03:01PM (#21806592)
PSL protects the other way around: it can only prevent whatever.has-a.name to compromise has-a.name or another.has-a.name

DNS Certification Authority Authorization assumes trust of the DNS server. Doesn't work if the DNS server itself is compromised / malicious. (Maybe with DNSSEC, but DNSSEC has its own problems and definitely doesn't work when your TLD itself is compromised.)

CT is really the only thing that works in this scenario (attackers/third party gaining write access to DNS records), but not every CA has CT and not everyone has the means to monitor CT logs. CT isn't even required for every browser/certificate (only EV certs (dead) for Chrome, and you need HPKP (dead) or Expect-CT (no browser support) for this to work reliably). Plus, what are you supposed to do when you find out there's a bad cert for your domain out there? Yell at someone on Twitter? It's going to be hard to convince a CA that you're not doing business with that someone with write access to DNS does not own the domain. Attackers are already impersonating you while it takes hours to sort things out.

... all of this is not to say that these security measures are bad, just not enough. We really put more trust on DNS servers than we ought to.

Re:Giving every IPv6 address a name by tialaramex on Monday December 16, 2019 @06:01PM (#21808468)
You're a little out of date on Certificate Transparency.

Chrome and Safari both require SCTs (the signed timestamps which prove a certificate was logged) for all new certificates, have done for quite some time. There are CAs which issue certs without logging but largely it's for applications which themselves know about SCTs so they can do the fix-up at runtime not issuance, because again if you just added these certs to a generic web server Chrome and Safari, two very popular browsers, will reject the certificates outright.

Since they'd be next to useless to lay people without, all the certs offered to the general public these days have SCTs baked in by the issuer. Let's Encrypt were ironically among the last to do this.

Re:Giving every IPv6 address a name by yzmtf2008 on Monday December 16, 2019 @06:12PM (#21808578)
Wow, that's really good to hear. One of the chief complaints I have about CT is the lack of agency. Not that this solves all problems, but good on Chrome and Safari for enforcing it
Re:Giving every IPv6 address a name by ownagefool on Monday December 16, 2019 @05:16PM (#21807956)
PSL could/should also stop sub.has-a.name trusting signed certs such as wildcard.has-a.name, depending on the configuration of the PSL. I'm just not really sure any actual browsers implement it like this though, as reading the PSL "how this is used page" doesn't turn up any such thing.

CAA does rely on DNS working, which your registrar can probably hijack. Fair point.

CT would help protect against the registrar but not against a malicious CA who simply wouldn't log if they were going to sign a cert maliciously.

You're generally right though.

Re:Giving every IPv6 address a name by namibj on Monday December 16, 2019 @08:02PM (#21809443)
If a CA "forgets" to add a certificate to the CT log, they need a really good excuse to not get distrusted immediately. That's part of the reasoning: malicious certs are almost useless if you don't present them to a client. And if that client manages to exfiltrate the cert...
Re:Giving every IPv6 address a name by ownagefool on Saturday December 21, 2019 @04:14AM (#21850467)
You have a very good point.
Re:Giving every IPv6 address a name by stevekemp on Monday December 16, 2019 @02:34PM (#21806284)
They can get an SSL certificate for "example.has-a.name", i.e. your subdomain, in one of two ways:

1. They complete a DNS challenge and get a certificate for "\\*.has-a.name" - which obviously includes your subdomain.

2. They sneakily point "your-address-here.has-a.name" to an IP they control, get a certificate issued, then point it back to where it should go.

The second option is more hassle, and easier to notice, but the first makes it needlessly complex.

Of course if your actual domain is "bob.com" then this is just a distraction. We're using "your domain" in this case to refer to the subdomain that points to your IPv6 address.

Re:Giving every IPv6 address a name by treysis on Monday December 16, 2019 @03:26PM (#21806828)
And then they have a certificate. What are they going to do with it? It's still not installed on your server.
Re:Giving every IPv6 address a name by yzmtf2008 on Monday December 16, 2019 @03:35PM (#21806928)
Suddenly whatever.has-a.name is pointing to a different IP address and that server has the cert installed. Oops.
Re:Giving every IPv6 address a name by treysis on Monday December 16, 2019 @05:08PM (#21807875)
So same trust you put in any 3rd party DNS service. But I agree there's less contractual bindings to this service than an account somewhere that you even might pay some money for it.
Re:Giving every IPv6 address a name by yzmtf2008 on Monday December 16, 2019 @05:12PM (#21807922)
I guess the point of all this discussion is "don't trust a random guy on the Internet that offers to host DNS for you", but also we place way too much trust on DNS.
Re:Giving every IPv6 address a name by milankragujevic on Tuesday December 17, 2019 @02:25AM (#21811443)
Can all the nice people who have downvoted explain what I said wrong?
Re:Giving every IPv6 address a name by anaphor on Monday December 16, 2019 @12:32PM (#21804936)
I don't think they even need to point the A record somewhere else. They can just create a TXT record and some CAs will allow you to validate it that way, if I'm not mistaken.
Re:Giving every IPv6 address a name by LeonM on Monday December 16, 2019 @12:43PM (#21805059)
As far as I understand, all they are doing is resolving the ipv6 address in the domain name to an AAAA record that matches the IP address in the name.

The domain name will still be 'has-a.name', so I don't understand how the certificate part is supposed to work. If anything you'd have to get their TLS cert for this to work, not the other way around.

Re:Giving every IPv6 address a name by djsumdog on Monday December 16, 2019 @12:54PM (#21805171)
I think the implication is if there is a security breech at their end, someone could hijack the service to point IPv6 addresses to somewhere unexpected.

If it's only used in development, it's not too big a deal, but could still be use to compromise things.

Re:Giving every IPv6 address a name by takeda on Monday December 16, 2019 @12:53PM (#21805157)
Maybe that's restriction for LetsEncrypt (I haven't used it myself) but certificates aren't restricted to 2nd level.
Re:Giving every IPv6 address a name by LeonM on Monday December 16, 2019 @01:06PM (#21805323)
No, this is nothing specific for Lets Encrypt, this is how PKI works.

A certificate is for a domain name, not an IP address.

Anyone can point a (sub)domain that they own to an IP address that they do not own. And then get a valid certificate for that domain.

I can point an A record to [your-ip].[my-domain] and I will be able to get a valid cert for that address. However, the address in your address bar will still point to [my-domain], not yours.

Re:Giving every IPv6 address a name by shawnz on Monday December 16, 2019 @01:25PM (#21805540)
You can get a certificate for an IP address, but LetsEncrypt doesn't support it. So this might be somewhat specific for LetsEncrypt.
Re:Giving every IPv6 address a name by stkdump on Monday December 16, 2019 @02:53PM (#21806509)
The same amount of trust you put into any service managing domain names for you?
Re:Giving every IPv6 address a name by perlgeek on Monday December 16, 2019 @04:16PM (#21807290)
Usually when you use a service to manage domain names for you, you have a contract with the managing party, which puts your relationship on much firmer legal grounds than when you use a random service provided for free and without legal guarantees.