namespaced-openvpn
systemd
namespaced-openvpn | systemd | |
---|---|---|
8 | 518 | |
302 | 12,516 | |
- | 1.6% | |
0.0 | 10.0 | |
about 2 years ago | 2 days ago | |
Python | C | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
namespaced-openvpn
-
Linux - namespaces: Network namespace
Network namespaces are a really nice feature for me. I use them for a few things. They are a simple and foolproof way of running programs in VPNs without having the whole system use the VPN, and you can have multiple of them, and even chain/nest them (foolproof as long as you remember to run it in the network namespace, such as a wrapper script or systemd service). WireGuard remembers the namespace it was created in and uses it for connecting to the VPN endpoint, so if you create it in your init namespace, then move it to a different namespace, programs in that different namespace can use the WireGuard interface which connects to the VPN endpoint using the original connection. Programs have no direct access to the internet if the VPN interface disappears. (https://www.wireguard.com/netns/#ordinary-containerization). There is also https://github.com/slingamn/namespaced-openvpn for OpenVPN.
- Use expressvpn on per-process basis?
-
How to run multiple minecraft clients on one computer with different IP for each client?
namespaced-openvpn can do this.
-
Before I get a VPN I have a question: How do I define what programs go through the VPN and what programs don't? (Linux)
Even found namespaced-openvpn, a ready-made solution for this problem.
- DNS for wireguard interface inside netns (with systemd-resolved)
-
VPN through Hotspot
It would depend of your device but on linux you can use namespaced-openvpn (https://github.com/slingamn/namespaced-openvpn). It would let you connect to vpn1 and running vpn2 over vpn1 for example.
-
Is there a way to use a VPN for only certain programs?
There are ready-made solutions like namespaced-openvpn for OpenVPN. See #27 when using with libtorrent-rasterbar. For WireGuard, you can read up on https://www.wireguard.com/netns but it might be a bit confusing. I've easily made my own script which implements this so that it creates a network namespace, creates a WG interface, moves the WG interface into the new network namespace, then configures the WG interface (which is now in the new network namespace).
-
With The Office leaving Netflix for a, apparently, crappy streaming service I think the entertainment companies need this reminder.
If you don't feel like using docker, this is an awesome script to seamlessly launch OpenVPN and spawn a new network namespace with only the tun interface in it. Handy af.
systemd
-
PoC to demonstrate root permission hijacking by exploiting "systemd-run"
No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.
And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.
Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.
-
Run0 – systemd based alternative to sudo announced
> 3. even `adduser` will not allow it by default
5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.
7. POSIX allows it:
* https://github.com/systemd/systemd/issues/6237#issuecomment-...
-
Systemd Rolling Out "run0" As sudo Alternative
> I for one love to type out 13 extra characters
FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.
> I wonder what random ASCII escape sequences we can send.
According to the man page source[0]:
> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`
and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.
In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.
(Happy to be shown if that's a mistaken expectation though.)
[0] https://github.com/systemd/systemd/blob/main/man/run0.xml
[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...
- Crash-only software: More than meets the eye
-
Systemd Wants to Expand to Include a Sudo Replacement
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...
-
"Run0" as a Sudo Replacement
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237
PS: https://pwnies.com/systemd-bugs/
-
Linux fu: getting started with systemd
https://github.com/systemd/systemd/issues/32028#issuecomment...
There are some very compelling arguments made there if you care to read them
-
Ubuntu 24.04 (and Debian) removed libsystemd from SSH server dependencies
Maybe it was because you weren't pointing out anything new?
There was a pull request to stop linking libzma to systemd before the attack even took place
https://github.com/systemd/systemd/pull/31550
This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.
-
Systemd minimizing required dependencies for libsystemd
The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.
https://github.com/systemd/systemd/pull/31550
- Going in circles without a real-time clock