Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wodny
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
wodny
5y ago
And it's also worth noting that eg. Debian has been providing hybrid images for years. Hybrid meaning you can write them directly to block device like USB drive or burn on CD. They exploit the fact that ISO images have first blocks emp
2.
▲
by
wodny
5y ago
Why "yikes"? Note that doesn't mean I don't know how to use eg. gdb outside or inside IDE. My debugging record proves my methods are quite efficient but there's something even more important - there are ways to syst
3.
▲
by
wodny
5y ago
That is not the point I was trying to make here. I was talking about extreme cases of faulty code which luckily are not that common. I meant that as long as you couple with sane libraries and adhere to standards in your own team extreme mea
4.
▲
by
wodny
5y ago
> The big thing here is that you seem to only work with your own code, where you can arbitrary refactor it and keep the entire thing in your head, as well as quickly find which module does what. Not at all. Due to lack of documentation I
5.
▲
by
wodny
5y ago
Print debugging is not that different from setting logging level to DEBUG and those logging calls should already be there in code and give meaningful insight so I don't get printing being often ridiculed. For over ten years of commerci
6.
▲
by
wodny
5y ago
I think this is an oversimplification. Just look at the number and the history of PEPs: - The Theory of Type Hints - PEP 483 - Annotations - PEP 3107 - 3.0 - Type hints - PEP 484 - 3.5 - Variable annotations - PEP 526 - 3.6 - Postponed eval
7.
▲
by
wodny
6y ago
It requires a tektonik finish on top. https://www.youtube.com/watch?v=JqYhuwu614Y Yelle - A Cause Des Garcons
8.
▲
by
wodny
7y ago
On the contrary, I've worked with 8 and {32,64}bit x {LE,BE} chips many times and wrote quite a lot of network code in C. But you're mixing syntax with semantics.
9.
▲
by
wodny
7y ago
An abstraction where "positive" and "negative" mean the same just for safety so they can't be confused with each other.
10.
▲
by
wodny
7y ago
It isn't a great name, but: it doesn't bare a contradiction in itself (contrary to "serverless"), there was already a tradition of drawing unspecified networks or internet as a cloud in diagrams. So "running in the
11.
▲
by
wodny
7y ago
The Ministry of Serverless (Miniless) is working on it.
12.
▲
by
wodny
7y ago
There is a huge difference between a metaphor (resemblance) and contradiction (stating it is and isn't something at the same time).
13.
▲
by
wodny
7y ago
Nice. I've missed the static binaries on the homepage and should have tried static compilation myself. Now my little python2 and find-based scripts exporting ncdu-compatible outputs[1] on systems without ncdu seem a bit redundant. On t
14.
▲
by
wodny
7y ago
Indeed, it was awfully buggy a couple of months ago when I gave it a try. Hope to reiterate in a couple of months. It would be a very useful tool.
15.
▲
by
wodny
7y ago
No. "Z raku" would mean that "raku" accompanies you and the play on words would be gone because it would be either "programuje z raku" ("one is accompanied by raku the programming language") or "
16.
▲
by
wodny
7y ago
It will have quite interesting implications, especially for former Perl 5 syntax enthusiasts. One could say in Polish they "code in cancer" ("programuje w raku").
17.
▲
by
wodny
7y ago
Thank you very much for the SOCK_DESTROY. I have completely missed its addition to the kernel.
18.
▲
by
wodny
7y ago
Or even worse - someone could steal my identity and start answering to JavaScript questions just to frame me.
19.
▲
by
wodny
7y ago
Drew Neil also created great video tutorials, the vimcasts[1]. [1]: http://vimcasts.org/episodes/
20.
▲
by
wodny
8y ago
asciio is great, I use it a lot to document architecture of systems.
21.
▲
by
wodny
8y ago
> The guide is not intended to teach everything about security -- that would be too much. On the other hand, the objectives list contains: "this guide will attempt to cover as many of them as possible". Despite that, it still m
22.
▲
by
wodny
8y ago
It has been mentioned in one of the pull request that this guide was being discussed on HN right after it got here: https://github.com/imthenachoman/How-To-Secure-A-Linux-Serve... . There are two fresh threads on Reddit
23.
▲
by
wodny
8y ago
On the other hand, SSH gives you just that if you verify the fingerprint which is not mentioned in the guide. MITM-proof channel is needed if one gains any kind of shell access because then public key substitution can happen in various ways
24.
▲
by
wodny
8y ago
The fact you have the private key permits access, not possession of the public key even though the public key is the one you add to the file on the server side (asymmetric cryptography). The "secure way" may also suggest that you
25.
▲
by
wodny
8y ago
I see no point, there are enough guides already and I don't consider myself competent enough in that field to teach others. I think it shouldn't be about fixing every particular mistake in the guide. It's about changing attit
26.
▲
by
wodny
8y ago
Nice. I admit, I haven't read the whole thing.
27.
▲
by
wodny
8y ago
"No, one shouldn’t" suggests that you don't use public key when encrypting data. "Verifying a signature […] is […] “decrypting with the public key” is the part I meant when writing that the original statement is "cr
28.
▲
by
wodny
8y ago
This guide contains (at least) inaccurate statements. It's oversimplifying and omitting important things while putting emphasis on some exotic details where defaults would be sane enough. "One key, the public key, can only encrypt
29.
▲
by
wodny
8y ago
So I will answer myself. Experiments suggest it is like that: https://www.reddit.com/r/linux/comments/apmptq/cve20195736_r...
30.
▲
by
wodny
8y ago
The vulnerability description seems to be lacking an explanation why the /proc/$PID/exe symlink is so special and why using the #!/proc/self/exe hashbang will work while using #!/usr/sbin/runc pr
More ›