HN user

kkl

491 karma

he/him

https://kel.bz

https://argemma.com

Posts26
Comments75
View on HN
argemma.com 3mo ago

You don't want long-lived keys

kkl
79pts62
blog.cryptographyengineering.com 3mo ago

Anonymous credentials: an illustrated primer (Part 2)

kkl
37pts0
argemma.com 5mo ago

Go's filepath.Clean does not prevent path traversal

kkl
2pts0
kel.bz 6mo ago

String comparison timing attacks in Go

kkl
1pts0
confer.to 7mo ago

Confessions to a Data Lake

kkl
37pts13
kel.bz 7mo ago

Control planes are a useful concept

kkl
2pts1
kel.bz 6y ago

Authenticated Dictionaries with Skip Lists and Commutative Hashing

kkl
3pts0
kel.bz 7y ago

RSA-Based Key Encapsulation Mechanisms

kkl
1pts0
kel.bz 8y ago

Building lattice reduction (LLL) intuition

kkl
81pts7
kel.bz 9y ago

The Goldreich–Goldwasser–Halevi (GGH) Cryptosystem

kkl
2pts0
blog.cr.yp.to 9y ago

Some challenges in post-quantum standardization

kkl
3pts0
cryptosense.com 9y ago

Why PKCS#1v1.5 Signature Should (Also) Be Put Out of Our Misery

kkl
1pts0
blog.portswigger.net 10y ago

Executing non-alphanumeric JavaScript without parentheses

kkl
123pts19
moderncrypto.org 10y ago

Encrypted Email Obstacles and Experiments

kkl
1pts0
blog.portswigger.net 10y ago

Web Storage: the lesser evil for session tokens

kkl
195pts69
blog.invisiblethings.org 10y ago

Security challenges for the Qubes build process

kkl
64pts17
github.com 10y ago

BLESS: SSH Certificate Authority for Ephemeral SSH Sessions

kkl
54pts18
www.praetorian.com 10y ago

Signal Protocol and Deniable Authentication

kkl
3pts0
eprint.iacr.org 10y ago

A Systematic Analysis of the Juniper Dual EC Incident

kkl
1pts0
googleonlinesecurity.blogspot.com 10y ago

Scalable vendor security reviews

kkl
1pts0
www.gregosuri.com 10y ago

Go Proverbs Illustrated

kkl
3pts0
www.agwa.name 10y ago

Duplicate Signature Key Selection Attack in Let's Encrypt

kkl
71pts4
www.agwa.name 10y ago

Duplicate Signature Key Selection Attack in Let's Encrypt

kkl
5pts0
kel.bz 10y ago

Secure Password Hash Algorithm Migrations

kkl
3pts0
geer.tinho.net 11y ago

Where the Science Is Taking Us in Cybersecurity

kkl
1pts0
www.praetorian.com 11y ago

Why You Should Add Joern to Your Source Code Audit Toolkit

kkl
2pts0

"we can't have service accounts"

To be clear: This is not my position! I advocate for service accounts in my post:

It is much harder to reason about, say, the security of an arbitrary Engineer's laptop than it is an EC2 instance that exists exclusively to tell KMS to sign something.

So every time we fire or lay off the person whose name is on the automation, we need to rotate the keys?

If a person previously had access to the key and knowledge of the key gives you control over that automated workflow, is that key (and by extension that workflow) still worth trusting?

Part of the threat model for an Engineering team is that people come and go. They move teams which have different levels of access. They leave the organization, in most cases, on good terms. I want to set up infrastructure where I don't need to remember that your SSH pubkey is baked into production configuration after you leave the company.

There are several options for setting up per-connection keys that are dispensed to users through the company SSO. That setup means you don't need to maintain separate infrastructure for (de-)provisioning SSH keys.

"Had the engineer that acted on that known better, or did other checks, this would have been avoided."

<insert takes long drag tweet[1] here>

I personally find "LLMs can do $THING poorly" and "LLMs can do $THING well" articles kinda boring at this point. But! I'm hopeful that stories like this will shift the industry's focus towards robustness instead of just short-term efficiency. I suspect many decision making and change management processes accidentally benefited from just being a bit slow.

[1] https://waffles.fun/amy.png

The job of a code reviewer isn't to review code. It's to figure out how to obsolete their code review comment, that whole class of comment, in all future cases, until you don't need their reviews at all anymore.

Making entire classes of issues effectively impossible is definitely the ideal outcome. But, this feels much more complicated when you consider that trust doesn't always extend beyond the company's wall and you cannot always ignore that fact because the negative outcomes can be external to the company.

What if I, a trusted engineer, run `npm update` at the wrong time and malware makes its way into production and user data is stolen? A mistake to learn from, for sure, but a post-mortem is too late for those users.

I'm certainly not advocating for relying on human checks everywhere, but reasoning about where you crank the trust knob can get very complicated or costly. Occasionally a trustworthy human reviewer can be part of a very reasonable control.

It’s also the case that someone you trust makes an honest mistake and, for example, gets their laptop stolen and their credentials compromised. I do trust my team, and want that to be the foundation to our relationship, but I also recognize that humans are infallible and having guardrails (eg code review) is beneficial.

Congratulations! Fish is such a wonderful shell. It’s been my daily driver for many years now but I’ve had a renewed appreciation for it now that I’m working in several different development environments. The default fish install Just Works so well that I don’t bother with trying to schlep my dotfiles around.

I could also buy that the free domains were ran up by scammers which could have caused some of the hair trigger Safe Browsing denylisting.

While there are compliance/security benefits it is not the primary motivation.

If you have fairly complicated infrastructure it can be way more efficient to have a pool of ready to go beefy EC2 instances on a recent commit of your multi-GB git repo instead of having to run everything on a laptop.

Most interesting e2e projects have abandoned email, specifically SMTP, as a secure messaging platform. I would look outside SMTP-based solutions if I were to start using a different project (assuming doing so is an option... I hope it is!).

My recommendation here is Signal: https://whispersystems.org/

Praetorian | Security Engineer | Austin, Texas | REMOTE (For principal and staff positions)

Praetorian is different. We are a collective of highly-technical engineers focused on helping our clients solve their most difficult security problems. Rather than break things over and over, our goal is to have an actual impact in making the world a better place. 100% privately owned and self-funded, we are focused on doing the right thing over short term profits. Where other companies pay lip service to vision statements and principles, we are unwaveringly guided by our core values, which are:

* Put the client first - Everything else will work out.

* Enjoy the work you do - Passion eats education and experience for breakfast.

* Be humble - True significance is only achieved as a team.

* Embrace the wobble - There is existential urgency to our work. We need to move and adapt quickly.

* Walk with a swagger - Relish the new challenge.

* Default to open - The right decision is in the data. Share all of it.

* Orient to action - Do not wait to be directed. Engage.

* Performance matters - We are a small company intent on doing big things. Every individual effort counts.

* Stop evil - Our mission is to make the world a safer and more secure place.

* Make craters - Our time on this earth is short. Leave an impact.

Although small, we are growing rapidly, with 50% YOY growth for the past three years. That growth is based on fantastic clients and their support. Our annual net promoter score is consistently over 80%. By comparison, Apple is typically in the mid 70s, and Amazon is usually in the high 60s.

We are looking for experienced engineers that share our values. We offer our staff a generous benefits package, including:

* Competitive salaries

* Quarterly bonuses, 4% 401k matching, stock options

* Health insurance, and options for vision, dental, ADD, Short term disability, and life

* 20% Bench time for research, tool development, or training

* Flexible vacation policy

* Low travel requirements. Seriously. No more than 20% for those in network security and nearly 0% for those in application security.

* Company contributions to training and conferences

* Opportunities for rapid growth and advancement based on merit.

If you’d like to learn more, please visit our career page at: https://www.praetorian.com/company/careers. Take a look at our tech challenges too, as we’ll ask you to complete one early in the interview process: https://www.praetorian.com/challenges/

I think a password manager (minus some of the scary bits like browser plugins) is a much better option than a mental password generation scheme. Maybe some folks can handle this but I think this is a non-ideal general recommendation.

This is a common theme in this thread but I'll re-state it here:

Web browsers cannot reliably distinguish between a configuration mistake and an attack.

For this reason, I think hard HPKP fails are a good thing. For those who opt-in to HPKP, this is a risk one takes in exchange for greater control over certificate validation.

As far as I know almost all browser security warnings are overridable. The only one that comes to mind that does not have a click-through option is when a HSTS-enabled site fails a validation check.

I do not think your analogy applies here. Finding 8 critical-risk bugs in a project from an audit is bad news. It is highly suggestive that the codebase is riddled with flaws.

Smoke, fire, yadda yadda.

I am bummed that you got the impression that you felt ignored for not having security expertise. I am not certain when you applied but I know our focus lately has been on senior engineers so that likely contributed to our response. Regardless, if we didn't do a good job relaying that information to you that is not good and I personally apologize (it was likely my fault as I handle a good chunk of the initial responses to applicants).

Thanks for the feedback though. It is appreciated.

Praetorian | Austin, Texas | REMOTE (For principal and staff positions)

Praetorian is different. We are a collective of highly-technical engineers focused on helping our clients solve their most difficult security problems. Rather than break things over and over, our goal is to have an actual impact in making the world a better place. 100% privately owned and self-funded, we are focused on doing the right thing over short term profits. Where other companies pay lip service to vision statements and principles, we are unwaveringly guided by our core values, which are:

    * Put the client first - Everything else will work out.
    * Enjoy the work you do - Passion eats education and experience for breakfast.
    * Be humble - True significance is only achieved as a team.
    * Embrace the wobble - There is existential urgency to our work. We need to move and adapt quickly.
    * Walk with a swagger - Relish the new challenge.
    * Default to open - The right decision is in the data. Share all of it.
    * Orient to action - Do not wait to be directed. Engage.
    * Performance matters - We are a small company intent on doing big things. Every individual effort counts.
    * Stop evil - Our mission is to make the world a safer and more secure place.
    * Make craters - Our time on this earth is short. Leave an impact.
Although small, we are growing rapidly, with 50% YOY growth for the past three years. That growth is based on fantastic clients and their support. Our annual net promoter score is consistently over 80%. By comparison, Apple is typically in the mid 70s, and Amazon is usually in the high 60s.

We are looking for experienced engineers that share our values. We offer our staff a generous benefits package, including:

    * Competitive salaries
    * Quarterly bonuses, 4% 401k matching, stock options
    * Health insurance, and options for vision, dental, ADD, Short term disability, and life
    * 20% Bench time for research, tool development, or training
    * Flexible vacation policy
    * Low travel requirements. Seriously. No more than 20% for those in network security and nearly 0% for those in application security.
    * Company contributions to training and conferences
    * Opportunities for rapid growth and advancement based on merit.
If you’d like to learn more, please visit our career page at: https://www.praetorian.com/company/careers. Take a look at our tech challenges too, as we’ll ask you to complete one early in the interview process: https://www.praetorian.com/challenges/

Praetorian | Austin, Texas | REMOTE (For principal and staff positions)

Praetorian is different. We are a collective of highly-technical engineers focused on helping our clients solve their most difficult security problems. Rather than break things over and over, our goal is to have an actual impact in making the world a better place. 100% privately owned and self-funded, we are focused on doing the right thing over short term profits. Where other companies pay lip service to vision statements and principles, we are unwaveringly guided by our core values, which are:

    * Put the client first - Everything else will work out.
    * Enjoy the work you do - Passion eats education and experience for breakfast.
    * Be humble - True significance is only achieved as a team.
    * Embrace the wobble - There is existential urgency to our work. We need to move and adapt quickly.
    * Walk with a swagger - Relish the new challenge.
    * Default to open - The right decision is in the data. Share all of it.
    * Orient to action - Do not wait to be directed. Engage.
    * Performance matters - We are a small company intent on doing big things. Every individual effort counts.
    * Stop evil - Our mission is to make the world a safer and more secure place.
    * Make craters - Our time on this earth is short. Leave an impact.
Although small, we are growing rapidly, with 50% YOY growth for the past three years. That growth is based on fantastic clients and their support. Our annual net promoter score is consistently over 80%. By comparison, Apple is typically in the mid 70s, and Amazon is usually in the high 60s.

We are looking for experienced engineers that share our values. We offer our staff a generous benefits package, including:

   * Competitive salaries
   * Quarterly bonuses, 4% 401k matching, stock options
   * Health insurance, and options for vision, dental, ADD, Short term disability, and life
20% Bench time for research, tool development, or training * Flexible vacation policy * Low travel requirements. Seriously. No more than 20% for those in network security and nearly 0% for those in application security. * Company contributions to training and conferences * Opportunities for rapid growth and advancement based on merit.

If you’d like to learn more, please visit our career page at: https://www.praetorian.com/company/careers. Take a look at our tech challenges too, as we’ll ask you to complete one early in the interview process: https://www.praetorian.com/challenges/

Praetorian | Austin, Texas | REMOTE

Praetorian is different. We are a collective of highly-technical engineers focused on helping our clients solve their most difficult security problems. Rather than break things over and over, our goal is to have an actual impact in making the world a better place.

100% privately owned and self-funded, we are focused on doing the right thing over short term profits. Where other companies pay lip service to vision statements and principles, we are unwaveringly guided by our core values, which are:

  * Put the client first - Everything else will work out. 
  
  * Enjoy the work you do - Passion eats education and experience for breakfast. 

  * Be humble - True significance is only achieved as a team. 

  * Embrace the wobble - There is existential urgency to our work. We need to move and adapt quickly. 
  
  * Walk with a swagger - Relish the new challenge. 
  
  * Default to open - The right decision is in the data. Share all of it. 
  
  * Orient to action - Do not wait to be directed. Engage. 

  * Performance matters - We are a small company intent on doing big things. Every individual effort counts. 

  * Stop evil - Our mission is to make the world a safer and more secure place. 

  * Make craters - Our time on this earth is short. Leave an impact.
Although small, we are growing rapidly, with 50% year-over-year growth for the past three years. That growth is based on fantastic clients and their support. Our annual net promoter score (a measure of customer satisfaction, see more here: https://en.wikipedia.org/wiki/Net_Promoter) is consistently over 80%. By comparison, Apple is typically in the mid 70s, and Amazon is usually in the high 60s.

We are looking for experienced engineers that share our values. We offer our staff a generous benefit package, including:

  * Competitive salaries Quarterly bonuses, 4% 401k matching, stock options Health insurance, and options for vision, dental, ADD, Short term disability, and life 

  * 20% Bench time for research, tool development, or training 

  * Flexible vacation policy 

  * Low travel requirements. Seriously. No more than 20% for those in network security and nearly 0% for those in application security. 

  * Company contributions to training and conferences 

  * Opportunities for rapid growth and advancement based on merit.
To Apply: Please apply through our portal here (All emails go directly to me): https://www.praetorian.com/company/careers. Part of the interview process involves the completion of one of our technical challenges. If you would like to get a head start, please view our tech challenges at http://www.praetorian.com/challenges/.

Considering:

* Golang's TLS stack is far less complex in comparison to other projects.

* Golang's TLS stack is written in a "safe" language.

* Golang's TLS stack is written by individuals with lots of experience in SSL/TLS (and its flaws!).

* Contributions to the project are held to very high standards.

Why do you believe the inverse is true?