HNHacker News
TopNewBestAskShowJobs

peanut-walrus

979 karma · joined December 31, 2018

submissionscomments
peanut-walrus··on Why might you run your own DNS server?
I have lately started to call dns "a global distributed database", rather than decentralized. Decentralized implies some properties that the dns system most definitely does not have.
peanut-walrus··on Using HTTP Basic Auth in 2022
And how exactly would having the hash in the log versus having the password in the log be an improvement? If someone gets that hash it's exactly the same as having the password, as it is the hash that gets sent to your server in the http request.

Edit: alright, I saw that you mentioned password reuse in another reply, fair enough, it does help against that.

peanut-walrus··on The state of external retina displays
I call bullshit on the $4000 scissors. The very very highest end goes to $1000 and most hairdressers use scissors around the $100 mark, which are still extremely good professional tools. Furthermore, if you have a very expensive pair of scissors, you are not going to be sharpening them twice a day... More like twice a year (and you take them to a professional, you don't do it yourself) .
peanut-walrus··on Why I stopped releasing EasyOS as an ISO file
And that is an absolutely insane state of affairs as well. I remember when my Packer playbooks stopped working because Linux kernel dropped floppy disk support and that was the method that was being used to inject the config on vmware.

99% of Linux installs are done on some hypervisor... ISO files are absolutely awful for this use case. Yet everyone keeps using them because the tooling is already jumping through thousands of hoops to make it work.

peanut-walrus··on What domain name to use for your home network
If you want to be a polite DNS resolver operator, root servers from B to G allow zone transfer, so you can just host the root zone locally. This way none of the typos or other bogus requests will leave your network.
peanut-walrus··on Probably Are Gonna Need It: Application Security Edition
I feel SSO should also be table stakes. Why even bother implementing your own account management if you can just use Keycloak or something even simpler to do it for you. This way your users can easily connect your app to whatever identity provider they are using.
peanut-walrus··on IPv6 Watch
To add to this, what I would like to see in IPv6 personally:

1) Ability to get a personal prefix as a private individual or a small company (not a LIR or LIR-sponsored)

2) Ability to use that prefix with any ISP I choose - similar to how a consumer can migrate their cellphone number to a different provider.

3) RFC 6275 actually implemented

There are other bits and pieces, but I believe if these with 3 things were done, IPv6 would actually have a "killer app" which would make a strong argument for migrating over to v6.

peanut-walrus··on IPv6 Watch
None of that is actually true though?

> It simplifies aspects of address configuration

I assume this is referring to SLAAC? SLAAC is...fine. Most managed networks will want the extra control offered by DHCP though and DHCPv6 is currently in a much much worse state than DHCPv4. Also a single interface having at least 2, usually 3 or more (link-local, autogenerated, privacy) v6 addresses on the network is definitely not simpler in any way. Also clients still have not figured out which configuration methods they should actually support - Linux network managers generally default to SLAAC-only and DHCP needs to be explicitly enabled, for Windows setting managed flag in RA works, I believe. Android does not support DCHPv6 at all.

> network renumbering and router announcements when changing network connectivity providers.

Absolutely not. Network renumbering is a breeze when all you need to change is the public address of your gateway and the local network keeps the same local addresses. Prefix translation is awful and no firewalls have good tools to handle changing your v6 prefix.

> It simplifies processing of packets in routers by placing the responsibility for packet fragmentation into the end points.

With respect to fragmentation - yes, but overall this statement is blatantly false. v6 packet processing by routers is much much harder due to the variable length headers.

> The IPv6 subnet size is standardized by fixing the size of the host identifier portion of an address to 64 bits.

Ok, this one is true. Not entirely sure why the author considers this better, but sure, I'll agree.

peanut-walrus··on The Actual OSI Model
Session - TLS

Presentation - HTTP

Checkmate, OSI-haters.

peanut-walrus··on The Ghost in the MP3 (2014)
Sure, but...

Have you seen the size of disks and network bandwidth recently? There is absolutely no reason to bother with lossy audio compression.

peanut-walrus··on Android In a Box – Run Android applications on any GNU/Linux operating system
> To install Anbox your system need to support snaps.

Go away.

peanut-walrus··on # of days since the last alg=none JWT vulnerability
Because people think their app will immediately scale to a billion users and their database is unable to service all those users. (It won't and the database can)

Alternatively, they have drank the microservice kool-aid and think that making a request to an AAA service every time the user wants to do something is just too much overhead (It isn't).

peanut-walrus··on Etcd, or, why modern software makes me sad
> the worst thing to happen to system administration since systemd

Cool, I need to look into Kubernetes way more then! There hasn't been any single development in the Linux world that has made my job as a sysadmin easier than systemd. Services, Timers and Networking that just works, is concisely defined and can be used across all relevant distros? Hell yeah, I don't ever want to go back into init.d/ifupdown/crontab world filled with bad configuration files, strange footguns and bugs that won't ever get fixed because someone's legacy system might depend on them.

peanut-walrus··on Configs suck? Try a real programming language
As a sysadmin, my main requirements for configs are:

* Human-readable and writable, including on systems where you have only very basic text editing tools * Easy to template (for example mass deployments via Ansible or other such tool) * Easy to use with grep/sed/etc

The format I've found that is easiest to work with is what sysctl and OpenWRT use for their configs. You can have complex hierarchies, but every line stands on its own. This means you don't have to be careful about where in the config a particular line is, if it is in the proper block, etc. Also getting information on a particular sub-item is as easy as running a single grep command.

peanut-walrus··on A cartoon intro to DNS over HTTPS (2018)
Honestly, I don't see why people keep bringing this up. Malware has millions of ways of creating covert channels and you will never be able to block/detect all of them. It's also well within the capability of major DoH server operators to detect and shut down malware domains pretty fast.
peanut-walrus··on A cartoon intro to DNS over HTTPS (2018)
So they start with talking about ESNI and then kinda completely gloss over it afterwards. Yeah you can reuse the TLS session if several sites are using the same CDN, however, this is again relying on centralization for privacy.

The cool thing about DNS architecture is the fact that it is decentralized. Mozilla's plan with DoH tries to fix missing features in DNS by getting rid of arguably the biggest killer feature DNS has.

Furthermore, several governments use DNS right now to block websites deemed illegal in their country. Not just authoritarian states that attempt to censor material critical to the regime, but also western countries (copyright infringement, child porn, gambling, etc). Does Mozilla and Cloudflare seriously think they will just go "oh ok, I guess everything is unblocked again now". No, they will either force Cloudflare to do the same or force local ISPs to implement even stronger filtering controls.

peanut-walrus··on Potholes to avoid when migrating to IPv6
RFC 1123 specifies the preferred format, not what is mandatory. This is clarified in RFC 2181:

"The DNS itself places only one restriction on the particular labels that can be used to identify resource records. That one restriction relates to the length of the label and the full name. The length of any one label is limited to between 1 and 63 octets. A full domain name is limited to 255 octets (including the separators). The zero length full name is defined as representing the root of the DNS tree, and is typically written and displayed as ".". Those restrictions aside, any binary string whatever can be used as the label of any resource record. Similarly, any binary string can serve as the value of any record that includes a domain name as some or all of its value (SOA, NS, MX, PTR, CNAME, and any others that may be added). Implementations of the DNS protocols must not place any restrictions on the labels that can be used."

You are correct that it can not be used in a hostname and I am not sure how it should be encoded when used in a URI, but for a domain name it is perfectly valid.

Indeed, I tested this on my local DNS server running Knot and I can create a domain name with colons in it and it also resolves using dig.

peanut-walrus··on Potholes to avoid when migrating to IPv6
':' is also a perfectly valid character in a domain name, so the naive splitting already does not work in the IPv4 ecosystem.
← PreviousPage 7 of 7