HNHacker News
TopNewBestAskShowJobs

ivlad

316 karma · joined January 1, 2015

submissionscomments
ivlad··on Buried Apple feature turns an iPhone into the perfect kids' dumb phone
Native Apple Maps allow downloading map regions for offline use.
ivlad··on Dostoyevsky isn't difficult
Dostoyevsky was originally published in magazines chapter by chapter, so he would end the December’s on a cliffhanger so that the readers re-subscribed
ivlad··on Vulnerability reports are not special anymore
Really. Back in the days, the majority of “researchers” sent scan results. The term “beg bounty” didn’t come about for nothing.
ivlad··on Vietnam plans to discontinue IPv4 by 2030
It turned out, they were talking about it since quite some time: https://conference.apnic.net/60/assets/presentation-files/39...
ivlad··on Vietnam plans to discontinue IPv4 by 2030
Current customer penetration is at 63% with 86% of government agencies have migrated their online portals to IPv6.
ivlad··on Google Hits 50% IPv6
> Would you give your personal phone number to random strangers on the internet, or even publish it on a website? Probably not, due to the possibility of harassment, right? IP addresses aren't any different

1. The claim that IP addresses aren’t different from the phone numbers requires proof

2. Until very recently, just before the Covid pandemic people regularly exchanged physical business cards with their mobile phone numbers. So, yes, people do that.

ivlad··on Google Hits 50% IPv6
> Realistically nobody outside some devoted HN readers are going to self host their own content.

P2P is not “self hosting”.

It’s video/audio conferencing working with less latency. It’s the ability to send a file directly and not via some file sharing site. It’s multiplayer gaming simplified. It’s faster software updates via BitTorrent.

ivlad··on Google Hits 50% IPv6
NDP is not simpler than ARP. For one, NDP relies on link-local addresses to work which in turn relies on MAC multicast where ARP relies on MAC broadcast only.
ivlad··on What is the purpose of the lost+found folder in Linux and Unix? (2014)
Because you need to pre-allocate space and indies for it in case things go wrong and the disk is almost full
ivlad··on IPv6 zones in URLs are a mistake
Not really.

Nothing prevents host from configuring a static link-local address, like fe80::1234. Not only that, some networks choose to have some standard link local address as a default gateway. For example, a router or a L3 switch can have fe80::1 on its downstream interfaces. This way, all hosts on all networks have fe80::1 as the default gateway and the router will have fe80::1 address on multiple interfaces.

Furthermore, you can (and some say, should) use link local addresses on transit links between your network devices, eg, between layers of switches in a hyperscale-sized data center network. Typically, the addresses will be deterministically configured, for example, consider

-(e1.0)[switch1](e1.1)—--(e2.48)[switch2](e2.25)-(eth0)[server1]

We have server1 connected to top-of-rack switch2 connected to aggregator switch1. Link between switch1 and switch2 is point-to-point transit. You can use exclusively link local addresses there. There are a few approaches:

- e2.48 gets fe80::2, e1.1 gets fe80::1 - all upstream ports are always fe80::2 in all network, all downstream ports are always fe80::1. A good thing is that link configuration is the same on all switches regardless of the Clos layer.

- switch1 serial number is 1001, switch2 serial number is 2002. Then, e2.48 gets fe80::2002, e1.1 gets fe80::1001. This way, all interfaces on a switch N have address fe80::N

You then can set up BGP session between the link local addresses and it either will always be either fe80::1 <-> fe80::2 or fe80::N <-> fe80::M. Switches also have a loopback address for ping, and other ICMP traffic. Either has advantages and disadvantages.

This is discussed in more details in RFC 6164, and a more high level overview is provided in RFC 7404.

ivlad··on Safe curves for Elliptic Curve Cryptography [pdf]
I am sorry, I should’ve read it twice before posting. I meant, QC to attack longer keys should be bigger proportionally. Number of operations is logarithmic. Silly me.
ivlad··on Safe curves for Elliptic Curve Cryptography [pdf]
I am not NSA, but I think their idea is something along the “once Shor’s algorithm is practical for key sizes of hundreds of bits, it’s only a matter of a few years of engineering effort to make it feasible for thousands bits long keys”. In other words, there is no sufficient safety margin for larger keys.
ivlad··on Safe curves for Elliptic Curve Cryptography [pdf]
… because?

Edit: yes, I read it and it is.

ivlad··on Safe curves for Elliptic Curve Cryptography [pdf]
He is not wrong on the main claim, which is “All ECC (X25519-P521) will be broken by private sector quantum chips before RSA-2048 due to the physical limitations of stabilizing qubits.”

Shor’s algorithm is polynomial, however the number of qubits required is in order of O(log(n)^2), where n is the length of the key. Because ECC keys are much shorter (e.g., 256 to 521 bits) than RSA (2048 to 4096 bits), a smaller quantum computer would be needed to attack ECC.

ivlad··on The New Internet
IPv6 + transport mode IPsec + opportunistic encryption with TOFU or other topologies of trust (including WoT, DNSSEC and PKI). All that is standard, most of it is available and only requires configuration (and, ideally, being turned on by default).

There is very little use for companies like Tailscale in this setup, it’s scalable and works.

ivlad··on CrowdStrike will be liable for damages in France, based on the OVH precedent
I acquainted with a guy at a conference in US and he was genuinely surprised I had no idea, how long US mile is. I explained him, we use metric system and his response was “but don’t you learn *the standard* system in ache school?” I did not know, how to respond.
ivlad··on The six dumbest ideas in computer security (2005)
> You will probably spent some time "teaching" them first

SELinux works well out of the box in RHEL and its derivatives since many years. You comment shows, you did not actually try it.

> fight with them every time you install something or make other changes in your system

If you install anything that does not take permissions into account, it will break. Try running nginx with nginx.conf permissions set to 000, you will not be surprised, it does not work.

ivlad··on The six dumbest ideas in computer security (2005)
> disallow users to choose a password they used previously (never understood that one)

That’s because you never responded to an incident when user changed their compromised password because they were forced to only to change it back next day because “it’s too hard to remember a new one”.

ivlad··on The six dumbest ideas in computer security (2005)
Dear user with password “password11111111111” logging in from a random computer with two password stealers active, from a foreign country, and not willing to use MFA, incident response team will thank you and prepare a warm welcome when you are back to office.

Honestly, this comment shows, that user education does not work.

ivlad··on Microsoft AI spying scandal: time to rethink privacy standards
This is a lie created by webmail providers. There is nothing difficult in self hosting email, abd ensuring email delivery.
ivlad··on Microsoft AI spying scandal: time to rethink privacy standards
You choose to have Google spying devices at home. You choose to have Gmail. You may have no choice for Internet search for quite some time, but you certainly choose your browser.

Start there.

ivlad··on How Ahrefs Gets a Billion Dollar-Worth Infrastructure with a 90% Discount
You can ask and they will ask for a Netflix size commitment in turn. Volume prices (they are essentially volume discounts) are often public.
ivlad··on Big Tech passkey implementations are a trap
Nope. Non-resident keys work differently. You register the public key with the service, then you encrypt the private key (via wrapping but that’s beyond the point here) with private key stored on your hardware token and send the encrypted blob to the service, too.

When you need to authenticate, service sends you the encrypted blob, you decrypt it using the key on hardware token and obtain the private key. Than you do (more or less traditional) public key authentication.

So, you don’t need to manage your private keys. Services do it for you.

ivlad··on Big Tech passkey implementations are a trap
For our corp environment we initially embraced software-backed FIDO authenticators (aka passkeys), but now I am almost ready to start enforcing only hardware authenticators via attestation.

The worst offender is (of course!) Google. In Chrome they bend the interface as much as they could to lure people into using Android as a key holder (and to sync it later on) even when platform authentication is available. Apple was very unfriendly by making their WebAuthn API private, so Safari used Keychain, Chrome did not have access to it (and forced Android) and Firefox only could use Yubikeys.

And now password managers are jumping into this, so when a user tries to enroll the device in a browser with password manager extension (looking at you, Bitwarden) on a platform with software authenticators good luck finding the right combination of clicks to choose Yubikey.

Enshittification of FIDO auth happened unbelievably fast.

ivlad··on XZ backdoor: "It's RCE, not auth bypass, and gated/unreplayable."
I am trying to figure out if auditctl is expressive enough to catch unexpected execve() from sshd: basically anything other than /usr/bin/sshd (for privsep) executed with auid=-1 should be suspicious.
ivlad··on XZ backdoor: "It's RCE, not auth bypass, and gated/unreplayable."
We witnessed Juniper generating their VPN keys with Dual EC DRGB, and then the generator constants subverted with Juniper claiming of now knowing how did it happen.

I don’t think it affected Juniper firewall business in any significant way.

ivlad··on XZ backdoor: "It's RCE, not auth bypass, and gated/unreplayable."
This is literally what the top post link is about. The backdoor functionality has been (roughly) figured out: after decryption and signature verification it passes the payload received in the signing key of the clients authentication certificate to system().

C/C++ is not a problem here because sshd has to run things to open sessions for users.

ivlad··on XZ backdoor: "It's RCE, not auth bypass, and gated/unreplayable."
This would be execve() that did not go through PAM dance and end up being privileged process.

I _think_ it’ll look very different in ps —-forest output.

ivlad··on XZ backdoor: "It's RCE, not auth bypass, and gated/unreplayable."
Doesn’t certificate verification occur in PrevSep process? If so, this would only grant RCE with nobody’s privilege.
ivlad··on Passkeys – Under the Hood
> Since you don’t want to have account enumeration, this means doing a primary authentication, e.g. passwords.

Nothing prevents site from sending a blob of random data when real key is not found.

> While hardware backed Security Keys for 2FA is great 2FA, there’s a tangible cost, both in UX and $ that leaves many users left out (not everyone can afford $20 for a security key)

Both major desktop operating systems come with WebAuthn support - Windows via Windows Hello and macOS with Secure Enclave backed key store. That not a problem at all in corp environment. Buying a Yubikey (or two) for each employee in the company is minimal cost comparing to laptop, desk, chair, software licenses

We use WebAuthn as the first factor, and we love it because it completely eliminated password brute force problem. Password attacks (brute force and stuffing) is a much bigger problem, than account enumeration, especially in corp environments where usernames follow a name-based pattern and everybody is on LinkedIn.

BTW, we are paid Bitwarden customer, and our Helpdesk was not too happy when Bitwarden update resulted unexpected prompt interrupting WebAuthn authentication flow for users. )

← PreviousPage 2 of 5Next →