HN user

cvwright

2,233 karma

Recovering academic. Security and privacy research engineer.

Posts25
Comments835
View on HN
www.microsoft.com 2y ago

Stuff I’ve Seen: A System for Personal Information Retrieval and Re-Use

cvwright
1pts0
github.com 3y ago

Frigate – NVR with Realtime Object Detection for IP Cameras

cvwright
33pts3
github.com 3y ago

Mother-of-All-Self-Hosting Ansible Playbook

cvwright
3pts0
waivek.github.io 3y ago

Smart Guy Productivity Pitfalls (2013)

cvwright
196pts130
dtinit.org 3y ago

Data Transfer Initiative

cvwright
1pts0
testflight.apple.com 5y ago

Circles: An End-to-end encrypted social network built on Matrix

cvwright
7pts1
spectrum.ieee.org 5y ago

SeKVM verified hypervisor based on KVM

cvwright
65pts37
github.com 5y ago

Show HN: Circles Is Open Source

cvwright
10pts0
www.kickstarter.com 5y ago

Show HN: I'm building an E2E encrypted social network app

cvwright
2pts0
thepublicdiscourse.com 6y ago

Lockdowns Don’t Work

cvwright
5pts6
web.cecs.pdx.edu 6y ago

Show HN: Crypto Crumple Zones: Enabling Limited Access Without Mass Surveillance [pdf]

cvwright
5pts4
www.lawfareblog.com 7y ago

A Roadmap for Exceptional Access Research

cvwright
1pts0
dl.acm.org 8y ago

A natural language approach to automated cryptanalysis of two-time pads (2006)

cvwright
2pts0
www.cameraftp.com 8y ago

CameraFTP

cvwright
1pts0
blockhash.io 8y ago

Blockhash: 256-bit perceptual hashes of images

cvwright
3pts0
list.zfsonlinux.org 8y ago

ZFS on Linux v0.7.0 released

cvwright
174pts88
schleuder.nadir.org 8y ago

Schleuder: A GPG-enabled mailinglist with remailing-capabilities

cvwright
81pts18
schleuder.nadir.org 9y ago

Schleuder: A GPG-enabled mailinglist with remailing-capabilities

cvwright
1pts0
www.drdobbs.com 9y ago

The Safe C Library (2009)

cvwright
94pts108
ivorylang.org 9y ago

Ivory: embedded domain-specific language for safer systems programming

cvwright
5pts0
www.tandfonline.com 9y ago

The non-zero counting attack on JPEG encryption

cvwright
3pts0
sel4.systems 9y ago

Genode OS Framework extends support for seL4 microkernel

cvwright
1pts0
trevorjim.com 10y ago

A public health campaign to stop C/C++

cvwright
6pts1
github.com 10y ago

Frank McSherry Responds to Differential Privacy Critics

cvwright
6pts1
www.forbes.com 10y ago

A 1200-Year-Old Hacking Technique Can Already Crack Tomorrow's Encrypted Vaults

cvwright
2pts0

Don’t use deterministic encryption unless your data is already highly random.

Any adversary who knows the distribution of the plaintext data can guess what your encrypted values are, with accuracy that improves as your sample size increases.

There were a bunch of papers on this 10-12 years ago. (Full disclosure: I was an author on some of them.)

You should try writing a design doc with the AI before you have it write the code. It will make random extrapolations from your first prompt, some good and some bad. Then you get a chance to argue back and forth with yourself with the robot as a helper.

The best early example of this is that Anthropic is already eating the lunch of all the new “AI security audit” companies. And they were only a few years old.

Those guys certainly thought they were being novel and creative, using AI to disrupt an expensive and labor intensive business model. But now with Claude Security, their own market share is going to be gobbled up before they can even get established.

Unfortunately even in the old days, a truly good programming book like you’re describing was depressingly rare.

Younger me really enjoyed some of the game programming books by Andre Lamothe.

Most “Learn Language X” books were terrible with over focus on syntax and very little thought into organization.

LLMs are bringing us back to all the “proper” software engineering stuff that we’ve always known we should be doing, but until now we never had enough time/people/money to do it right.

Brainstorming and research before writing a design.

Writing a design or spec before writing the code.

Comprehensive unit tests.

Etc etc etc.

Like you, I get vastly better output from the tool when I create a detailed spec in markdown before I let it start coding. And bonus, the LLM is pretty good at helping with the spec too.

The word “exploit” may be doing a lot of work here. In my experience Opus 4.6 is perfectly happy to provide test cases that trigger ASAN, even without the super secret squirrel security access.

But if you ask it to get you a shell it’ll probably tell you to get lost.

Waymo in Portland 3 months ago

And you don’t have to worry that some random passenger will piss, puke, or shit in the Waymo during your commute.

The first two happened to me within the span of a month during the three years that I rode Trimet in Portland.

It’s easy to find sketchy lines of code in any large C project.

The big advance that they are claiming with Mythos is the ability to triage all the hundreds of candidate vulns and automatically generate exploits to prove that the real ones are real. And if they’re really finding 27-yr-old 0-days in OpenBSD, then it’s not just hype.

Right. It’s things like Baltimore (when I lived there) requiring that high speed internet had to roll out in poor areas first, before it could go into the rich neighborhoods.

But this was the early 2000s and the internet was still “new”. Only the richer areas cared and were willing to pay the price. Letting them have first (or even equal!) access would have made it easier to fund the rollout in low income areas.

Or maybe this is like fondly remembering the busted economy car that you drove around with your friends? I have my first 386DX sitting on my desk right now and it looks exactly like the top left of that photo.

The hot car that we all lusted after was maybe something like a SGI Indy or an O2.

The closest thing we have is, in security / privacy / cryptography, you can write "attack" papers.

It's not perfect. You don't get any credit unless you can demonstrate a substantial break of the prior work. But it's better than in a lot of other fields.

Facebook is cooked 5 months ago

Several people have tried over the years. We all failed, because it doesn’t work.

The economics don’t work because no one is willing to pay.

The network effect doesn’t exist, because real people don’t post enough to get the flywheel started.

All the dark patterns exist because that is what users reward.

Sucks but it’s true.

Just burn the tokens. It’s an upfront cost that you pay once at the beginning of a project, or on a smaller scale at the beginning of a major feature.

For context, I’ve built about 15k loc since Christmas on the $20 plan, plus $18 of extra usage. Since this is a side project, I only hit the limits once or twice per week.

It’s really not. For anything substantial, the things that you do to manage an LLM are the same things that you should be doing to manage a team of human devs, even if the team is just yourself.

Documentation. Comments. Writing a plan and/or a spec before you begin coding. Being smart with git commits and branches.