bubblewrap
Our great sponsors
com.skype.Client | bubblewrap | |
---|---|---|
8 | 75 | |
14 | 3,641 | |
- | 3.5% | |
6.2 | 6.6 | |
about 2 months ago | 7 days ago | |
C | ||
- | GNU General Public License v3.0 or later |
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.
com.skype.Client
-
Red Hat considers Xorg “deprecated” and will remove it in the next RHEL
Screen sharing seems to be a difficult problem to resolve. Zoom only just resolved this recently[1], Webex has been promising a fix for a while[2], and Skype still hasn't done anything[3].
[1] https://support.zoom.us/hc/en-us/articles/6634039380877-Zoom...
[2] https://help.webex.com/en-us/article/9vstcdb/Webex-App-for-L...
[3] https://github.com/flathub/com.skype.Client/issues/142
- How Install & Use Microsoft Edge, OneDrive, Skype, Office 365 & Teams on Linux
- Installed Void on My New Work Laptop But Running Into some Issues
-
No camera or mic on Skype in both 15.3 and TW
If the device still works in the os and just not in skype. I would try the flatpak package. https://flathub.org/apps/details/com.skype.Client
-
Solus no longer runs Skype or Wickr, please help
https://snapcraft.io/skype or Flatpak https://flathub.org/apps/details/com.skype.Client
-
Can't start Skype flatpak on Fedora 33
I also found some old issue on Github Latest version of Skype won't run #70
-
Important info for Skype users on Fedora
Alternatively one can use the Flatpak packaged Skype.
-
Can we have an objective, non-FUD, user-centric comparison/discussion of Snap and Flatpak for 2021?
I have no idea if that is true or not, I haven't used Skype for more than a decade. But, an app running as a Flatpak can't directly create files in /etc/ even if that directory was exposed in the sandbox (which it isn't in the Skype flatpak, as you can see here), just like any other process running as a non-root user can't create files in /etc/ (unless your permissions on /etc/ are severely messed up). So if what you claim is true, it has nothing to do with Flatpak's sandbox or with portals. And since in the default configuration the pulseaudio daemon (which is running outside the sandbox) does not run as root either, I severly doubt that what you claim here is true at all.
bubblewrap
-
I Use Nix on macOS
Nothing nix specific but you may be interested in https://github.com/containers/bubblewrap
- I reduced the size of my Docker image by 40% – Dockerizing shell scripts
- Exploring Podman: A More Secure Docker Alternative
-
Using GitLab Kubernetes Runners to Build Melange Packages
Recently, I came across Chainguard and wrote the article How to build Docker Images with Melange and Apko. As a fervent supporter of Kubernetes and GitLab CI, I was eager to experiment with building images using Melange in this particular setup. GitLab's shared Runners work seamlessly with Bubblewrap, eliminating the need for additional configurations. This post is intended for enthusiasts like myself, interested in hosting their own Kubernetes Runners and leveraging the Kubernetes Runner Type of Melange.
- how strong is the steam (runtime) sandbox for games?
- Server-side sandboxing: Containers and seccomp
-
A Study of Malicious Code in PyPI Ecosystem
```
This is basically manually invoking what Flatpak does:
https://github.com/containers/bubblewrap
This is also useful for more than just security. E.G., you can test how your app would behave on a fresh install by masking your user configuration files. I personally also have a tool that uses it to basically bundle all dependencies from an entire Linux distribution in order to make highly portable AppImages— Been meaning to post that, will get around to it eventually maybe.
The flags above should hide your user data (`--tmpfs`), disable network access (`--unshare-all`), hide/virtualize devices and OS state (`--dev` and `--proc`), and make the rest of the root filesystem read-only (`--ro-bind`— Including the insecure X11 socket in `/tmp`, which you might want to expose for GUI apps).
Check them against `bwrap --help`; I might have omitted one or two more things you'd need.
- Bubblewrap – Low-level unprivileged sandboxing tool used by Flatpak
-
Firejail: Light, featureful and zero-dependency security sandbox for Linux
While trying to find out more comparison information, found this light on details issue:
https://github.com/containers/bubblewrap/issues/81
It mentions nsjail and minijail.
What are some alternatives?
pkg2appimage - Tool and recipes to convert existing deb packages to AppImage
firejail - Linux namespaces and seccomp-bpf sandbox
flathub - Issue tracker and new submissions
flatpak - Linux application sandboxing and distribution framework
com.microsoft.Teams
com.microsoft.Edge
nsjail - A lightweight process isolation tool that utilizes Linux namespaces, cgroups, rlimits and seccomp-bpf syscall filters, leveraging the Kafel BPF language for enhanced security.
fakeprovide - A tool for generating "fake" rpm packages to resolve otherwise intractable dependency issues.
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
ostree - Operating system and container binary deployment and upgrades
multipass - Multipass orchestrates virtual Ubuntu instances