Package Details: skype-secure 3.1-1

Git Clone URL: (read-only, click to copy)
Package Base: skype-secure
Description: Restricting Skype for Linux access
Upstream URL:
Licenses: custom
Provides: sskype
Submitter: alium
Maintainer: alium
Last Packager: alium
Votes: 12
Popularity: 0.28
First Submitted: 2016-03-02 13:46
Last Updated: 2018-05-17 19:39

Latest Comments

1 2 3 Next › Last »

alium commented on 2018-07-22 21:20

@Astaoth: yes, a special user is used for running Skype within one's normal environment. Permissions will have to be set to ensure your home directory is not readable by the special Skype user.

Astaoth commented on 2018-07-21 11:56

Hi, How is restricted Skype ? With a special user ?

alium commented on 2018-05-18 06:56


I am install newest version of skypeforlinux ( and skype-secure (i have not installed) and all works normally, without problems with login/logout.

Try uninstall skypeforlinux-stable-bin, skype-secure, delete _sskype (if still exist) and install again.

Marc.2377 commented on 2018-05-18 06:22

@alium thanks for updating quickly!

I already upgraded, but still - sadly - it keeps logging me out. It's weird because, when launched, the window loads as if I'm logged in, but a second or two latter, it logs out.

I'll try to investigate this next week; if you have any clues on where to look, please let me know ;) regards

alium commented on 2018-05-17 19:35


  1. Thanks for info about icon name, i am changed it.

2.+3 - entry in /etc/sudoers.d will do it, that you need not every time typing your password to unlock - i will change it for wheel group users only, not for ALL

Marc.2377 commented on 2018-05-17 19:13

@Utini See here:

Marc.2377 commented on 2018-05-17 19:11

Dear @alium, first of all, thanks for your package.

I have a couple of points...

  1. In the .desktop file, the icon name should be skypeforlinux.

  2. Since my last system upgrade, a week ago, when I launch skype-secure, it won't ask for my password to unlock the _skype user keyring. As a result, I have to login again to Skype every time. Do you have any suggestion on how to fix this?<br> [edit] I launched Seahorse as the _skype user and unlocked the keyring manually; the passwords are there, but Skype ignores them. Also deleted the existing entries but they were not re-created. Launching Skype with my own user account still works OK.

  3. Is an entry in /etc/sudoers.d really needed?

alium commented on 2018-02-25 18:03

@Almindor: show me your config, please

cat ~/.config/pulse/

Almindor commented on 2018-02-25 16:50

@alium: updated to latest skype gain. Deleted .config in /home/_skype

Devices are detected ok now however actual call audio doesn't work (incoming). My microphone works but I can't hear the other side. Oddly tho I can hear "system" sounds like an incoming call alert or if I call out the ringing sound. But as soon as the call is started no incoming audio (other side does hear me).

If I use skype directly everything works ok.

alium commented on 2018-02-18 18:09

@Almindor: still all works for me, sorry

try delete all in /home_skype and run sskype again