I'm often asked how to turn a security-related interest or hobby into a job. For the longest time, I'd say pretty much the same thing written here: get a book, do some research, build some projects, talk to people in industry. I've been going to DEF CON for about 25 years now, and I've had this conversation countless times.
But in 2026, tptacek says it best in the comments here: At this point, who knows?
Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set.
That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated.
The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security.
Barracuda Networks posters at every airport stated "Security Solved."
As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us.
> I'd say pretty much the same thing written here: get a book, do some research, build some projects, talk to people in industry. I've been going to DEF CON for about 25 years now, and I've had this conversation countless times.
I use the "uni-ball - Jetstream SXN-210" (in 1mm), they are superb, don't smear, write smooth every time and are cheap enough if I lend one to someone and don't get it back I don't regret it, ergonomically they are comfortable as well, not a lot else to say about them beyond that - just a really well designed pen.
To grow food in a truly sustainable way, we need to really understand the laws of biology at a macro and micro level (soil biology, water cycle, carbon cycle, etc...). Our scientific systems are not working efficiently towards that necessary understanding. 2/3 of life forms by mass in soil are microbes and we know nothing about 99% of them. We just know that soil biodiversity and food production/quality are highly correlated. If we don't work on this correctly, in the end, we will end up in a dead end and join the 99% of species that disappeared since life exists on earth in the long term. Odds are against us but I'm working with scientists and professionals that are having incredible results.
> If we don't work on this correctly, in the end, we will end up in a dead end
We have over 10.000 years of agriculture already behind us so I think that's proof that it works well enough to support small communities in a sustainable fashion. It's simply not necessary to understand all the microbes etc..
If you are hinting on optimization so we can feed all of humanity, then I mean we are definitely not resource and knowledge limited but rather by more mundane things. I'd wager just the US defense budget is enough to feed to world without a problem.
I don't really agree with the person you responded to, but there is a lot of agriculture that is dependent on mined input, having long depleted the soil of whatever nutrients were there when we started. There are many places that are abandoned and barren because we did agriculture there. Land is still being dramatically degraded by many types of agricultural practices.
Meanwhile there are forests that were forest (and other ecosystems as well) 10s of thousands of years ago and just as lush and fertile (if not moreso) than they were to begin with.
Sustainable generally means we can maintain the fertility of the land indefinitely without mined inputs. Whether or not it's a completely achievable goal, it makes good sense to strive for it... Mines will become spent, theres only so much land to degrade, etc.
Often when people talk about sustainable agriculture they are talking about systems that mimic biological systems that keep those forests lush for millennia. These types of agricultural systems frequently look similar to agricultural systems of the past with more human labor involved, but less damaging waste products and fewer externalities. (Reducing pollution of the water downstream and minimizing ecosystem impact).
> There are many places that are abandoned and barren because we did agriculture there.
Totally but I'd argue nowadays it's not because we are missing the knowledge but rather ignorance and short-term economic gains.
Imo sustainability goes hand in hand with population (and lifestyle). We want a diverse ecosyaystem, this simply doesn't work if there are 10 billion people wanting to eat meat or produce tons of plastic. Our problem is not knowledge in agriculture that prevents us from sustainable living.
maybe he means it's too complex for science to rediscover. maybe rediscovering/using ancient wisdom regarding this domain is better. but this is just intuition
I was thinking of offering both subscription and once off options for private users so folks with subscription fatigue have an option. It'll be subscription only for business users, as that will come with ongoing support. Once off private user cost is likely to be around $79 US. What do you think about that?
Edit: How many machines would you expect to run it on? What would be your expectations for the licence use on multiple machines?
My use case is personal, although I could absolutely see a business use case. Charge a subscription for the enterprise license(s) so you get recurring revenue!
For personal software, though, I am very much opposed to subscription costs without a "lifetime" software purchase model. I think a single active license (transferable but only active on one machine at a time) is totally reasonable.
For the sake of discussion, I'm not sure it really matters if the agents are going rogue.
Yes, if someone directed them to hack external systems, that would (in my opinion) be a crime similar to a script kiddie pointing Metasploit at a vulnerable server.
If no one directed them to attack external systems and they "went rogue" because they decided it was the best way to accomplish the task, okay, fine -- but, in my opinion, the operator of the agentic swarm is still responsible.
The Morris Worm was famously not meant to wreak havoc on early computer systems -- Morris just wanted to see if it would work. How is this any different?
Morris was convicted for violating the Computer Fraud and Abuse Act.
Morris wasn't in charge of the companies that are propping up the US GDP, wasn't making tons of rich people even richer, and hadn't "promised" to eliminate like 50->90% of all payroll costs everywhere?
The operator is the CEO because they are the ones that decided to not pay employees to monitor these running services. No one else in the entire company has any authority.
This is a (very long and) well-written treatise against passkeys in their common and disparate forms. It's worth reading, and brings up several interesting and often concerning points.
I don't agree with the conclusion, though.
TOTP is great, flexible, and keeps the user in control; however, using a passkey in a flexible password manager (Bitwarden, keepass, 1Password, etc) really does continue to give the user control. And the user experience is dramatically easier than filling in TOTP codes.
To advocate for TOTP over passkeys, we're already relying on an application to generate those numbers (authenticator apps, password managers, etc). I see no reason to not simply continue using those pieces of software to manage passkeys, too.
> using a passkey in a flexible password manager (Bitwarden, keepass, 1Password, etc) really does continue to give the user control. And the user experience is dramatically easier than filling in TOTP codes.
See my comment here https://news.ycombinator.com/item?id=50049311 about userVerification: required. Passkey in 1Password used to be on par or slightly more difficult than filling in TOTP codes (need to click to approve rather than browser extension autofill and even auto-submit on a large number of websites) but that’s no longer true with a good number of websites requiring userVerification. Now you have to type in your login password on desktops without biometrics. Forum thread: https://www.1password.community/1password-at-home-31/user-ve...
That's entirely a problem with one implementation and not the standard. It's like complaining Torx is bad because one manufacturer adds stabby bits to the handles of their Torx screwdriver.
I can't use a passkey on a device unless I can install my password manager on that device and I am comfortable giving that device access to my passkeys. Passwords are simply unparalleled in their flexibility. You're never going to be locked out because isn't working today.
I think the bit about TOTP was mostly a joke, the problem with passkeys is that they're billed as a replacement for passwords but they mix lots of MFA concerns in and make interoperability essentially impossible a lot of the time.
> I can't use a passkey on a device unless I can install my password manager on that device and I am comfortable giving that device access to my passkeys.
That's simply not true. I'm able to log onto GitHub on my corporate device using a passkey that's kept in 1Password on my iPhone.
That's fine if you've got a couple of supported devices. The hardware support is however very bad. If my hardware is unsupported (and most hardware in the world is unsupported) that's not very helpful.
This "use a passcode from another device such as my phone" tech mentioned above is just Bluetooth LTE. Every phone and most laptops and desktops in the last decade or so has Bluetooth LTE support. Hardware support is very good.
Passkeys are built on Webauthn (and ultimately sort of synonymous with it) and that has always been the web standard for all physical key support such as Yubikey and is basically the same as it has been for decades when dealing with Passkeys only with updated UX on top. Hardware support here is pretty good, too.
Bluetooth is very hard to use. This just isn't about hardware support, it's about "how long does it actually take the average person to do a Bluetooth-mediated workflow, how consistent is it between devices, if someone is trying it with a new device, what is the learning curve?" If someone can't figure out how it's supposed to work between their iPhone and their Windows laptop, there might theoretically be support. Practically speaking it's broken most of the time.
The deeper problem is that the default behavior is storing a passkey directly on a specific device and hardware-locking it to that device. That's great if you're an enterprise or whatever and you've got SSO set up well. For the average person, "I lose my iPhone and it effectively resets all my passwords" is a hopelessly unusable workflow.
I store passkeys in a 3rd party password manager which has an app on my phone, so I'm only relying on Apple to handle the bluetooth mediation and they do that very well.
I maybe lucky, but outside of headphones bluetooth has never failed to work for me.
Now with a 3rd party password manager, I can install it on any device and all my passwords work there too. However, with Apple, it stores it on keychain so if you have an internet connection, your passwords are backed up.
If you don't have an internet connection, you're not the average person.
That is a hopelessly unusable workflow which is why the default behavior on iOS is storing Passkeys in iCloud Passwords and having cloud sync between devices and cloud backup/restore.
On Windows you can use Apple's iCloud Passwords app for Passkeys now directly, in supported browsers because for whatever reason Apple's engineers didn't want to build a Windows plugin for it (yet?) or you can use the Bluetooth option. Windows 11 makes it very easy to use the Bluetooth option and for better/worse some of the requirements that made Windows 11 stop supporting older hardware were also those making sure that Bluetooth LTE is reliable especially for Passkeys.
In the Bluetooth flow the "only" user facing mediation step is the QR code. Some of Microsoft, Apple, and Google's finest all worked together to make sure that UX is about as simple as it can be with just about no learning curve. If someone is used to pulling up a QR code in the camera app and clicking the default app it wants to pop up, "it just works".
If you hear Bluetooth and think of complex pairing dances, that is nothing like how Passkey signings over Bluetooth work. The devices don't need to be "joined" or "paired", they just need clear enough radios for a quick couple of messages, which a QR code kicks off.
I'm not sure I see the difference between a complex pairing dance and needing to install the iCloud Passwords app on Windows (I've used iTunes for Windows.) Writing down a password is much more reliable than expecting any of that to work.
I'm just trying to point out that you seem to be fighting strawmen and yelling about last decade's apps and technology as if that was the current state.
Writing down a password is simpler, but it is also stopped being reliable for the vast majority of users because it stopped being adequate security for the average user. Passwords are too easily stolen. Passwords are too easily reused because human memory is quite fallible. Passwords are too easily caught by a man-in-the-middle attack or a social engineering attack. Passwords are too easily leaked in a database breach. Even when properly hashed and salted, password hashes still are weak to rainbow tables and other such attacks.
Passkeys trade off a bit of supposed simplicity (if you ignore modern advice like use different passwords for everything and always use a password manager because you will never remember all your passwords, it's not humanly possible if they are also all secure enough passwords). But the tech is already at a very usable level of simplicity for average users. It's just like learning a password manager. For some average users it is even easier than learning a password manager the standards and standardized user flows have simplified a lot of the hard edges of the password manager, including the above mentioned "use a QR code to provide temporary access on some other device to your Passkey without syncing your full Password Manager".
Most people don't use password managers. I am not even sure that password managers really qualify as a reasonable amount of complexity for the average person. There's a cost/benefit and I think passwords + SMS 2-step-auth is a reasonable balance between usability and security for most people.
Obviously, I use a password manager and I use MFA where possible, but even that I find to be a little questionable from an availability standpoint because I have a hard time ensuring that I have multiple MFA devices located in different buildings, so a fire or a flood or something could totally lock me out of all my accounts, some of them possibly permanently, which is the thing that scares me more than getting hacked.
Passkeys (combined with full-disk-encryption by default) scare me because they make the assumption that most people would prefer to lose access to their photo library than risk someone breaking in and getting them, and I actually think most people would prefer the converse. If a burglar breaks into my house they can steal my TV, I can live without it, but please don't steal my photo albums (problem is they're the same thing.)
That's not really true, a QR code pops up, and you can use your other device to read it.
Even if your other device is a mainframe computer thousands of miles away, so long as you can photograph the QR code, you can decode it and send the data string for the passkey device needs to it.
The issue that many have with passkeys is that someone will tie a passkey to an ecosystem that they don't personally control like Apple's and then they can't get into their services without an apple device that's onboarded into Apple's ecosystem.
The other device has to respond "in nearby radio space" via Bluetooth LTE when using the QR code bootstrap, but that's about the only requirement and it can be just about any device.
But you can be locked out if the provider decides you need to change your password after a breach, or you forget the password, or you enter the wrong password in too many times.
They’re both equally disposable. You can reset a password just like you can reset a passkey.
I completely agree that KeePassXC and other password managers give you total user control, and they do support "passkeys" -- but crucially, not all kinds of passkeys. KeePassXC has no remote attestation support, nor hardware-backing support, and nor do I think it should.
My claim is not that passkeys couldn't give you control in principle. It's that the standard readily allows for websites to prevent you from being allowed to exercise that control, and the unclear messaging and UX around passkeys means most users will not even notice should this happen.
That has nothing to do with the standard. Any website can invent its own proprietary authentication extension and try to force it on its users. If a website wanted attestation and the standard didn't have it, they'd just make their own extension. See Apple with Thunderbolt.
> using a passkey in a flexible password manager (Bitwarden, keepass, 1Password, etc) really does continue to give the user control.
Sure, but if you read the article you would know that deal can (and will undoubtedly) be altered. The passkey issuer can demand that the passkey be hardware-backed, and I've already run into passkeys that cannot be stored in bitwarden out in the wild (i.e. they REQUIRE that I use a TPM-backed store in my computer). Eventually it will be a particular TPM-backed store running on an attested platform. Now that's not generally the case today, but make no mistake, that IS the ultimate goal... You will only access valuable services from devices that you fundamentally have no control over (e.g. locked down OS's with attestation before you can access X,Y,Z), so that you can't steal from netflix, skip the sponsor segments on youtube, block ads in your web browser, etc. etc. etc. If you want a preview of how this might all work from the technical side, just look into how TEE works for large-scale GPU deployments right now.
Unfortunately I can see Apple eventually getting onboard too. As in "Sorry your device is no longer secure for using passkeys. Please update to a newer device!" Nice little incentive to boost flagging iphone sells.
Except that banks can (and do) already require proprietary apps to generate one-time passwords, often requiring official iOS and Android phones. It's not some nebulous future, it's happening now.
And you can't really blame them. A TOTP 2FA from your password manager is not secure. It WILL be hacked sooner rather than later. And SMS is horrible, expensive, and unreliable.
So far, only FIDO keys provide hardware-backed security ("resident keys", not passkeys) that is nicely segregated into self-contained hardware module. And it does not require you to run a full end-to-end DRM-ed stack.
If you _want_ true privacy and security, that's pretty much the best case you can hope for.
Except that those "self-contained hardware modules" are actually rarely "self-contained" but usually an integral part of a smartphone running a huge bunch of mostly-untrusted code and that the containment keeps getting breached, of course.
The only difference is that banks will now blame you for any losses caused by hacked devices because it is on paper "unhackable" with a well-updated device, so it is now your fault that their crappy bank app's security was broken.
And you still don't get to use Passkeys with banks, of course.
I'm using a Yubikey that is permanently plugged into a USB-C port on my laptop and another one in my dock at home.
> Except that those "self-contained hardware modules" are actually rarely "self-contained" but usually an integral part of a smartphone running a huge bunch of mostly-untrusted code and that the containment keeps getting breached, of course.
And it actually doesn't matter if the secure device is designed correctly. Providing a secure channel over untrusted networks is something that we can do easily.
> And you still don't get to use Passkeys with banks, of course.
I can. I'm using US Bank and it supports my Yubikey-bound WebAuthn credential just fine.
It's unfortunately full of half-truths which are not even necessary to make the point it's trying to make about attestation, so it's the opposite for me: Bad article, (somewhat) valid conclusion.
> TOTP is great, flexible, and keeps the user in control
TOTP is vulnerable to MITM attacks, so it's at best acceptable.
Indeed, there's nothing wrong with, e.g., passkeys backed by KeePassXC. The problem is specifically that passkeys support attestation, so eventually no websites that you need to use will support passkeys from those pieces of software.
Could be.. zillionaires usually like mountains; I hear he can't drive; driving the boonies far from civilization is not that easy in the winter. He needs to buy a big shovel for the winter.
He needs a landing strip for an aircraft. Helicopters are dangerous at night. No uber eats delivery there. We will see. It will take a decade to set it up.
To properly curate and conserve wild land will take a lifetime, it's not a puppy for Christmas.
To be comfortably setup in life needs functioning set of buildings with five or six people can be done in a year with zillionaire budget.
Existing topographic and resource maps (it's Sweden, they likely have good records) can be supplemented with draped air geophysical survey to digitally map land surface and subsurface structure (geomagnetic).
After a discussion about location, heavy lift helicopters can bring in light one man excavation machines to cut out, build out a well drained stable level pad. While this sits, modular home components are factory assembled - the kind where three or four large semi trailer sized heavy concrete base lego blocks with fully plumbed and wired house sections are transported to site and slid together with hydraulic jacks to lock together.
These are flown in to the pad and fitted together, while septic tanks, wood sheds, battery banks, smaller staff units, etc. are also landed.
This is work that has to planned in advance with seasonal considerations, sure, but with people that do this work, local knowledge support, good logistics and funding it's possible to have a comfortable livable foot print to expand from.
Lol, if we're talking about a scenario like this, do you think these billionaires are like Noah with their arc, just collecting people to survive? I cannot see a sane person joining them or not ratting them out if things really go bad.
I guess he can afford it but why then would he move to boonies. Is he not going there to chop wood and take videos of the deer in the forest? Is it going to be a compound with people bending 90 degree and saying yes sir?
Yup it could be but speculation needs a cause.. Hard assets are the rage right now anyways for AI zillionaires. He has apparently bought a monastery in Colorado for $120M; Miami beach house for $55M; 500 acre land in New Hampshire. His net worth is about $20B, $22M is like buying a toy to him and it is not a major investment.
it definitely doesn't, as people buy shit all the time on impulse alone. when you have zillions of dollars, that impulse buying can look different, as you kind of say as well.
I don't understand why people have this silly take that billionaires somehow will hide in the bunker and be fine. Do you really think that if we get to that point, they will happily live in a bunker by themselves lol. These people are unable to survive by themselves, let alone in a bunker. Do you think food and shit will get delivered to some random location just like that when shtf.
they have food and water to last decades in the bunker without needing external supplies. Why would they need to be supplied from the outside world? that's the entire point! (agree with the rest of your point though)
> TLDR: it created program to decypher the string using opensource solutions related to enigma
It seems weird to me that a (relatively) straightforward workflow like that would elude crypto hobbyists for the last 21 years (since 2005 according to the article).
Most probably the framing "elude crypto hobbyists" is a not correct description of reality, rather a way to sell sesation.
I think they did not have access to all pleora of enigma-related bits and pieces. Or there were not enough autistic ones. Or this one was simply overlooked in favour of more interesting one.
The whole trick is possible only because bunch of people whote bunch of text and code about the subject, well-documented it and made public. For LLM all these bits and pieces are very "close" and easy to pull together unlike for people who have to deal with each bit and decision and information.
My understanding is that there's a bunch of short, probably unremarkable ciphertexts out there that if anyone spent a good amount of time on (days/weeks), they'd break, but nobody really has the incentive to do so.
These models/agents are quite good at that type of thing, working through the tedious bits with available information and tools.
But in 2026, tptacek says it best in the comments here: At this point, who knows?
Are we still telling kids to learn programming languages to become software developers? Perhaps system design is a more reasonable skill set.
That said, because this is the time to say it: security is still important, and it's not -- and shouldn't be -- fully automated.
The toolchain is changing just like it always has. I remember when interpreted languages replaced compiled ones, and people said that interpreters solved security. Then people went from writing their own codebases to implementing frameworks, and people said it solved security.
Barracuda Networks posters at every airport stated "Security Solved."
As long as people take risks, security is important. Now we just need to focus on designing resilient systems instead of finding bugs and vulns on the code-level. LLMs can do that part for us.
reply