zemnmez

10 ms·

61.
by zemnmez 6y ago
this approach tends to be a self-own. Bug bounty and responsible disclosure folks don’t usually have expertise in it, so you’re just making the real attack surface less visible until someone with the expertise comes a long and owns you deep
62.
by zemnmez 6y ago
i always wonder (and never seem to find out) how the authors of these normal people things (‘video game’ / ‘phone’ ) addiction ideas disambiguate with generalised executive function disorders, which seem almost more common?
63.
by zemnmez 6y ago
from a security engineer's perspective, these things seem great, but ultimately become really tricky where DOM nodes need to be produced safely. string concatenation doesn't cut it for obvious reasons, then you have mXSS from mism
64.
by zemnmez 6y ago
is there a reason to believe this isn’t already sandboxed / run in a VM?
65.
by zemnmez 6y ago
It’s a lot easier to just have a depth limit on such non-cyclic graphs than keep an in-memory list of previously seen nodes. its interesting for sure! but a much rarer edge-case imo
66.
by zemnmez 6y ago
i'm really struggling to find a great work of literature that this app doesn't think is terrible. the idea is conceptually neat, and the UX is nice though constructively, think a lot of these decisions are too strict, for example
67.
by zemnmez 6y ago
In my experience, it's that people without experience with security researchers tend to think of security issues as having been fundamentally been created by the researchers themselves, rather than already existing in the system. If yo
68.
by zemnmez 6y ago
OpenID Connect is a superset of OAuth 2.0 so I find this an odd comparison. Assumedly there'll be an authN OIDC OAuth 3.0 protocol too.
69.
by zemnmez 6y ago
really got me thinking with this one. I just assumed the us butter was just sliced from a standard sized block, but i actually have no idea
70.
by zemnmez 6y ago
as an english person, these tools all seem to be for working on butter that’s fresh out of the fridge; they’d be impossible to use on normal, room-temperature soft butter. There’s something funny about inventing a tool to solve a problem th
71.
by zemnmez 6y ago
is this a listicle? i don't really understand what the purpose of this article is. What makes hackers mindset useful to programmers? what makes these points the valuable takeaways. Not asking hn, it just seems missing from the article
72.
by zemnmez 6y ago
isnt the man pig the enemy from the DLC ‘a machine for pigs’? or is that coincidence
73.
by zemnmez 6y ago
Security by obscurity is harder to reason about. Heavily obfuscated code is always more insecure once the obfuscation is reversed. The other big difference is you can incrementally break it; you are not going to be privy to if someone is se
74.
by zemnmez 6y ago
this is because things aren’t ‘moving apart’— space itself is expanding (into what? nobody knows). it’s not that the galaxies are being propelled apart from a force in a particular place either; everything is expanding away from everythi
75.
by zemnmez 6y ago
This is true, except for scrypt, which is very tough to make ASICs for. As for bcrypt, it's true that ASICS can go very fast, but you ultimately have a massive advantage as defender here. An attacker needs to try billions of combinatio
76.
by zemnmez 6y ago
you really shouldn't be implementing your password hashing algorithm from basic crypto primitives. s/bcrypt works right out of the box with no config.
77.
by zemnmez 6y ago
The issue here isn't so much the password strength, but the algorithm used to hash the password. A good password hashing algorithm like scrypt takes a long time to make a single guess, even if the input is simple, and since every singl
78.
by zemnmez 6y ago
am I missing something here? the attacker still only needs to know the pepper to brute force all the passwords with this scheme. Since the pepper is deterministic, and especially with md5 which is already extraordinarily quick to reverse, t
79.
by zemnmez 6y ago
This comment was about Twitch :'( I guess you guys thought I was talking about something else
80.
by zemnmez 6y ago
While this article goes into the technical detail of how an attack from jwt.io to a developer might work, I think it most importantly leaves out what the potential threat actor in this threat model is, and what they hope to achieve. The act
81.
by zemnmez 6y ago
If we were living in a simulation, why would our perception of relative time be absolute relative to the simulation? Why wouldn’t the simulation just simulate slower at whatever level of abstraction it operates on, causing us to be none the
82.
by zemnmez 6y ago
All backend systems at save a few minor exceptions are written in Go :)
83.
by zemnmez 6y ago
2016-2017 flu deaths: 38,000 March 2019 - 15 Aug 2019 covid deaths: 176,000
84.
by zemnmez 6y ago
I am not fully sure what this comment is intended to mean, but if it intends to imply that covid-19 is ‘just as bad as’ a bad flu, the excess death statistics in virtually every country of the world pretty categorically show that to be untr
85.
by zemnmez 6y ago
I really like the way these proposals preserve file metadata
86.
by zemnmez 6y ago
as an fyi, csrf protection is not related to bot protection; the csrf protection failure means an attacker can execute this code in another user’s browser (and get no meaningful result)
87.
by zemnmez 6y ago
Github proxies all image requests, like GMail as a security measure. The cache busting technique the author refers to only ensures the security proxy doesn’t cache the image data, which would prevent the counter going up
88.
by zemnmez 6y ago
i havent seen / made one
89.
by zemnmez 6y ago
do you have a source on this? I've only seen assertions that recaptcha is against GDPR from US sources
90.
by zemnmez 6y ago
The author(s) got in contact with me about this post: it does appear that the APIs are exposed at the window level, meaning any iframe can access these functions. It's important to note that CSP does not traverse iframes, or at least,

More ›