Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mothershipper
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
Dishwasher Salmon
(en.wikipedia.org)
466 points
by
mothershipper
3y ago
|
371 comments
2.
▲
Kubernetes, GitOps and Odd Jobs
(medium.com)
3 points
by
mothershipper
4y ago
|
0 comments
3.
▲
Minor Sabotage
(en.wikipedia.org)
2 points
by
mothershipper
5y ago
|
0 comments
4.
▲
by
mothershipper
5y ago
As others have pointed out, there is a big difference between self-modifying in-memory and on-disk. The article seems to be talking about on-disk modification. We have an internal CLI for our developers that auto-updates itself by replacin
5.
▲
Dishwasher Salmon
(en.wikipedia.org)
5 points
by
mothershipper
5y ago
|
1 comments
6.
▲
by
mothershipper
6y ago
Should also be using a KDF or PBKDF to generate the key from a password, instead of using the text of the password as the key.
7.
▲
Crossplane Community Day
(events.crossplane.io)
1 points
by
mothershipper
6y ago
|
0 comments
8.
▲
Why Computers Beep
(twitter.com)
1 points
by
mothershipper
6y ago
|
0 comments
9.
▲
by
mothershipper
6y ago
So much this. At a previous company (Go/Python/Ruby), we used gRPC almost exclusively, and the experience was pretty good. We're just now hitting a growth point where we need stronger contracts between our services and unfort
10.
▲
by
mothershipper
6y ago
related: https://news.ycombinator.com/item?id=24994624
11.
▲
by
mothershipper
7y ago
Not sure how I feel about the comparison to the shadow passwords file -- the shadow file doesn't contain the raw password, but a hashed version. If someone steals the shadow password file, they still have quite a bit of computation to
12.
▲
by
mothershipper
7y ago
Assuming one byte per character, you'd have to have a 17 character password before you're using multiple blocks. For any password shorter than that, this cipher is pretty much operating in ECB mode due to the re-used IV.
13.
▲
by
mothershipper
7y ago
source: https://snyk.io/vuln/SNYK-JS-YARN-537806
14.
▲
by
mothershipper
7y ago
There seems to be a typo in the blog post -- yarn needs to be updated to 1.21.1, not 1.12.1