I'm not a paranoid... but prefer to run closed spyware^W software in a jail. Yeah, it is easy to start it like `firejail skype`, but after r KDE (for example) going to restore it without jail... My solution is to replace `skype` binary with a wrapper script, so execution will always will be in a jail. I'm going to attach a patch to run skype under `firejail`. Reproducible: Always
Created attachment 457334 [details, diff] patch to add USE=firejail
Created attachment 457338 [details] a wrapper script to replace binary
Wrapper script looks good to me, reassigning to actual Skype maintainer to decide and apply patch.
Created attachment 457788 [details, diff] patch to add USE=firejail Also added a desktop file patch at src_prepare step...
Created attachment 457790 [details, diff] patch for desktop file to force running in a jail
Idea has merit. I'm going to merge this and turn in a PR as soon as I've tested it. Holiday stuff IRL has kept me super busy.
Upstream is EOLing this version of skype next month. Furthermore, it has a hard dependency on the soon to be removed qt4. There will be no further enhancements to skype classic.
Can you elaborate on "Upstream is EOLing this version of skype next month."? I clearly see the linux version at https://www.skype.com/en/download-skype/skype-for-linux/
Yeah, let's just say microsoft is being...creative. The new "skypeforlinux" intended as an upgrade for this version of skype is so different architecturally its practically a completely separate application. The differences necessitated a split of skype into a separate package called "skypeforlinux", to which firejail is not compatible. The current version of skype is the classic version and has nothing to do with the skypeforlinux package, and I've just been informed that microsoft is officially deprecating the classic version, and it will be end-of-life'ed in july.
