pritambaral
- https://discourse.ubuntu.com/t/security-advisory-critical-vu...
Or improves. With third-party fine-tuning.
Same boat here, though I also get to enjoy some of the benefits of libghostty, via ghostel in Emacs. Ghostel is noticeably faster when there's a lot of output being dumped, but I don't often need the speed and use it only because it's integrated rather well into the rest of my Emacs.
> tmux -CC integration
If you can stomach Emacs, there are at least two packages that implement this, one via eat and another via vterm, though none via ghostel just yet. Shouldn't be difficult to port, though.
Sure, Ferrari might refuse to sell me a second car, but I wasn't going to buy a first one either. OTOH, if a ruler company refuses to sell me rulers ... I'll just get one from another company. Like how I use local LLMs today.
> ... I am just honored to be in the presence of a soon-to-be Nobel prize winner. When are you going to publish your findings ...
I'm not going to fall for this bait or follow this asinine line of argumentation. Perhaps you should reconsider how your reactions are, to quote you, "a sign of poor impulse control. It reflects poorly on you and you should practice not snapping".
Apart from South Africa (which gave up its nukes voluntarily), the other contenders were basically only held back due to military intervention (Iraq, Libya, Syria) or economic sanctions (Iran).
I mean, this is a setup that ships with a default password that's the same as the username, and the first thing I do on all my server installs is disable all default user accounts and enable passwordless sudo.
From reading other docs of Ubuntu Server, it appears they relax the root/non-root distinction in other ways too. But I'd probably never have suspected this particular vector of vulnerability.
No, it does not[1]. LXD:
- explicitly warns against this mode of vulnerability. Of course, there's no protection against people who blindly run commands copied from the internets, but the official documentation, at least, for as far back as I can recall, has had clear warning boxes against this, with explanations.
- does not have the track record of bad design that docker has had (IMO).
- supports fine-grained ACLs and user management.
----
[1]: https://ubuntu.com/blog/shared-development-environment-with-...
Psst. There's also this, in typical KDE style: https://github.com/aeroshell-desktop/uac-polkit-agent
However, one still SHOULD NOT allow untrusted software arbitrary read/write access to their $HOME, even on a completely secure (and thus, imaginary) OS. No reason why every App X should have access to the files of every App Y.
Public domain software is free to "copy, redistribute, and modify", so ... where's the disfavour?
So, one can put in the minimal effort of removing one div.
> being associated
There's no requirement of association of any kind. See above and below.
> request
Cool. Pay for your own branding. Request fulfilled. No? Then it's a demand, not a request.
Perhaps you should check if anybody else sees what you see. After browsing through every image I could find in the history of this project, I, at least, am convinced: any "sexualization" _you_ see is entirely in your head.
> ... in judeo christian societies
I really hope you're not trying to whitewash your own bias by alluding to those religions. From everything I've read of their texts, and interacted with practioners of those religions, I'm unaware of any bias that classifies _cartoon depictions of children_ as "sexual".
Perhaps you should try whitelabeling instead. Don't like the packaging? Package it yourself!
It does, to me. Been burned enough times that I now, at minimum, audit the source code of third-party libraries before I use them.
Yes, now you get my point. Do you run rootless containers (with the Docker backed) or do you run "root" containers?
1. Docker (or any Linux container runtime, for that matter) is not intended for, designed for, or effective as a security boundary. 2. Root containers run as root on the host. The "sandboxed" processes have full capabilities, as far as the kernel is concerned with them.
Does your Docker backend run commands in rootless containers? I skimmed the code but didn't see anything to confirm this.
ProxyJump is a special case of `ProxyCommand ssh -p <port> <user>@<host>`. Can't replace the `ssh` in there when using ProxyJump.
"It was the Hyundai Corpo that broke the law! They're stealing American jobs! That's why ICE targeted them! No, I have no evidence, only blind belief. Why are you even asking me for evidence?! What about when Hyundai did bad things in the past???!!?1?"
----
If it:
1. Repeats the arguments of fascists.
2. Defends fascists.
3. Attacks the victims of fascists.
What do you think it is? A duck?!
In fact, this party has a — by now well-established — track-record of precisely this bad behaviour. They haven't even tried to hide their actions, only their individual faces. They've been public about their disdain for the law, for humanity, and their general evil plans.
And here you are accusing their victims of crimes you, like them, have no evidence of.