Live data from Hacker News

🥺: the best sudo replacement

xeiaso.net

91–100 of 559 posts

Re: 🥺: the best sudo replacement

#91
post #68

Wait, HN renders emojis?

Technically speaking, no, HN doesn't render any titles. Your browser is displaying U+1F97A, which is sent over-the-wire as the bytes \xF0\x9F\xA5\xBA (UTF-8 encoding).

By "render" they probably meant "didn't strip"; HN will strip emoji from comments/titles, generally.

E.g., the emoji of the article: "" but I suspect there won't be anything between the quotes.

(An exception was made for the title, in this case; dang mentions that in a comment in the comments here.)

Re: 🥺: the best sudo replacement

#92
post #81
post #69

Earlier quoted context omitted.

Honestly, I don't think you should take anything the author of this wrote seriously, the most charitable interpretation is that most of their work is a form of satire.

Speaking as the author of the work, most of _this post_ is satire meant to make you think about the existing security boundaries involved in privilege escalation. It is a false problem. The part about being annoyed that sudo is still written in C is coming from a sense of exasperation that there's still more predictable memory safety bugs involved with sudo because it's still written in C. The comment about python-cr…

I feel that where I work. I'm outnumbered in wanting to write web servers with high-level, non-performance-sensitive business logic in something other than C++. We keep having memory safety problems, but more importantly, it's really slow to develop this way and doesn't match the skillset we're hiring. However, these people are being paid.

The common reason our most senior engineers tell me isn't even that it's too late to switch, it's that "C++ is perfectly fine as long as you use it right" and "it doesn't matter what the outside world uses" and "performance."

Re: 🥺: the best sudo replacement

#93
post #63
post #37

Earlier quoted context omitted.

The ironic part is that I didn't break any RSS readers! I broke URL parsers in chat apps, scp, and for command line arguments to `tailscale serve`.

I have a poem that I published which has a Japanese title (宝石の十字架). The journal that published it put that in the URL: https://www.invisiblecitylit.com/poetry/宝石の十字架/ and not surprisingly, many URL parsers don’t like the Japanese text.¹ I really need to get around to changing the link that I have in my publications list to use the URL encoded version of the title so that it's easier to share on systems that don’t lik…

Boy do I have news for you:

https://en.wikipedia.org/wiki/Internationalized_domain_name

https://en.wikipedia.org/wiki/Country_code_top-level_domain#...

Pretty soon you'll be able to do this instead:

https://www. 宝石の十字架 .jp/poetry/invisiblecitylit

(https://www.xn--u9j516hprf6h574cs4w.jp/poetry/invisiblecityl...)

Is that... good? ¯\_(ツ)_/¯

Re: 🥺: the best sudo replacement

#94
post #81
post #69

Earlier quoted context omitted.

Honestly, I don't think you should take anything the author of this wrote seriously, the most charitable interpretation is that most of their work is a form of satire.

Speaking as the author of the work, most of _this post_ is satire meant to make you think about the existing security boundaries involved in privilege escalation. It is a false problem. The part about being annoyed that sudo is still written in C is coming from a sense of exasperation that there's still more predictable memory safety bugs involved with sudo because it's still written in C. The comment about python-cr…

[dead]

Re: 🥺: the best sudo replacement

#95

I mean clearly this is all quite tongue in cheek but: > It's also debatable if the entire concept of privilege separation as implemented in Linux and UNIX was a bad idea to begin with but we're stuck with it because of an endless ball of legacy programs controlled by egotistical open source people that refuse to change […] Not a very charitable way to describe volunteers who don’t want to learn the flavor-of-the-mont…

It wasn't very charitable, but neither is the "flavor-of-the-month language" dig

Re: 🥺: the best sudo replacement

#96
post #81
post #69

Earlier quoted context omitted.

Honestly, I don't think you should take anything the author of this wrote seriously, the most charitable interpretation is that most of their work is a form of satire.

Speaking as the author of the work, most of _this post_ is satire meant to make you think about the existing security boundaries involved in privilege escalation. It is a false problem. The part about being annoyed that sudo is still written in C is coming from a sense of exasperation that there's still more predictable memory safety bugs involved with sudo because it's still written in C. The comment about python-cr…

[flagged]

Re: 🥺: the best sudo replacement

#99
post #85

I replaced "sudo" in all my systems a long time ago with an alias to "machinectl shell .host" which is IMHO far superior to it, as it doesn't just spawn a new shell as a privileged process, but instead initializes a full user-session and then spawns a shell in this user-session. This doesn't carry the risk of tainting the new session with the context of the initiating shell (pwd, env, ...) and doesn't only feel like…

Sudo's -i option is able to provide you with a shell in the same state that it'd be if it were a fresh login. I've burned this into my fingers a long time ago. Also, in most configurations you have to specifically whitelist environment variables for them to surivive a "sudo" call.

Is there another way of opening a root shell other than "sudo -i"? That's what I've been using for a decade. How do other people do it?
Post reply on HN