Hacker Newsnew | past | comments | ask | show | jobs | submit | erikerikson's commentslogin

The price is ridiculous but I've been happy with the design of https://www.ladiesfirstchickendoor.com/products/

In the city the door doesn't always shut but I think I could adjust that, I just haven't needed to.


How is a bantam helpful with eagles?

They're the only ones that seem to want to fight the eagles. They're HYPER aggressive. I don't get it.

Thanks so much, good to know. We want chickens in a place with eagle problems.

Non-introspection is a fantastic source of strategic vulnerability. It can facilitate a bias to action which has it's clear value. However, if you are creating a highly valuable asset then it puts you in a position where you are extremely easy to manipulate and harvest. Perhaps this serves VCs quite well.

How does this stance work with your CICD?

I suppose you would have to commit your node_modules, or otherwise cache your setup so that all prerequesite modules are built and ready to install without running post-install scripts?

Instead they took away TOTP as a factor.

Scaling security with the popularity of a repo does seem like a good idea.


Are there downsides to doing this? This was my first thought - though I also recognize that first thoughts are often naive.

You don't want "project had X users so it's less safe" to suddenly transition into "now this software has X*10 users so it has to change things", it's disruptive.

TOTP although venerable was better than no second factor at all.

TOTP isn't phishing resistant

No it's not but it's better than nothing. Don't let the perfect be the enemy of the good.

It's not much better than nothing. It basically solves "I reused my password across sites" exclusively, that's it. If you're going to go through the effort of TOTP, it seems odd that you wouldn't just use a unique password.

If you use a unique password it's questionable if it adds any value at all. Perhaps in very niche situations like "password authentication is itself vulnerable due to a timing attack/ bug" or some such thing... but we've rarely seen that in the wild.


I disagree.

I use a password manager and systemically use long random passwords. An attacker would need to compromise my password manager, phish me, wrench me, or compromise the site the credential is associated with to get that.

Using local only TOTP (no cloud storage or portability for me, by choice) they would have to additionally phish me, wrench me, compromise my phone, or compromise my physical security to get the code.

None of these are easy except the wrench which is high risk. My password manager had standard features which make me more phishing resistant, and together they are more challenging than either apart. For example the fact that my password manager will not fill in the password on a non associated site means I am much less likely to fill in a TOTP code on an inappropriate site. Though there are vulnerable scenarios they aren't statistically relevant in the wild and the bar is higher regardless.

Now I happen to have a FIDO key which I use for my higher security contexts but I'm a fairly low value target and npm isn't one of my high security contexts. TOTP improves my security stance generally and removing it from npmjs.org weakened my security stance there.


I'm confused. All an attacker has to do is phish you to get your password and TOTP.

TOTP would cover cases like a compromised password manager or a reused password. That's it, right?


My password manager, as is standard for most of them, will not fill or show a password if the URL bring visited doesn't match the credential. Thus, a credential not showing is a huge red flag. The workflow is pretty standardized so any deviation is a big red flag.

Maybe you can be more specific about the attack flow you are imagining and how it will work technically to bypass my controls.

To answer your question, no and I provided details. It literally provides a second, non portable factor with a different vulnerability surface.


> My password manager, as is standard for most of them, will not fill or show a password if the URL bring visited doesn't match the credential. Thus, a credential not showing is a huge red flag. The workflow is pretty standardized so any deviation is a big red flag.

I agree.

> Maybe you can be more specific about the attack flow you are imagining and how it will work technically to bypass my controls.

Can you be more specific about the attack that your password manager doesn't solve that your TOTP does? The attack I'm suggesting is already solved by your password manager.


I've believe I've already written that but it is that my password manager gets compromised. It is not perfectly secure and has failure points. Given that it is separate from the second factor a successful attack against the password manager still leaves an attacker unable to login without a separate compromise of my TOTP code. Of course that can also be compromised but two compromises is strictly more difficult than one.

Right, so it's "password manager is compromised" or "password is reused", right? I'm pretty skeptical of these mattering relative to phishing, which is radically more common.

TOTP seems effectively useless for npm so that seems fine to me

Yes, finding out how badly wrong you were is never fun. Of course the lack of ubiquitous Oxford comma use is itself and separately displeasing.

Doesn't sound like a close friend to me. If I tell them what I really think they may not be a friend? Close may not mean what you think it means.

The challenge is that these social choices have a strong stratification effect and those of us who can transit the cultures are statistically rare.


No. Those are the abusers of freedom who like to pretend their freedom doesn't stop at the tip of our collective noses. They are also a minority regardless of how vocal that small minority and the psyop saboteurs are that egg them on and keep them company.

Maybe we should just abandon the concept of "freedom" and embrace material values. Or is that too 19th-century progressive? Must we always ignore all discourse that happened after the bill of rights was scribbled?

And/or tarp to occultate the weeds and dormant seedstock

I appreciate that physics and math are simple, reductive, and first principles enough to be tractable. Solving easier problems always has better optics so long as all problems look equivalent. I'm guilty myself, only rising to neuroscience and relatively superficially at that...

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: