Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synergy: Run as user, add crypto support #29220

Closed
wants to merge 4 commits into from

Conversation

benley
Copy link
Member

@benley benley commented Sep 10, 2017

Motivation for this change

Sending keystrokes over the network unencrypted makes me sad.

Details on setting up x509 certs are at https://github.com/symless/synergy/wiki/Security#Generating_Certificate_and_Fingerprint

 - Run synergy client and server as user services instead of root
 - Add optional crypto support
@mention-bot
Copy link

@benley, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @MarcWeber and @wkennington to be potential reviewers.

serviceConfig.Restart = "on-failure";
};
})
(mkIf cfgS.enable {
systemd.services."synergy-server" = {
systemd.user.services."synergy-server" = {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This requires the user to be logged in (so that a systemd --user instance is spawned). Is this desired for this kind of service?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's how I use it, at least. If we want to have synergy working on the display manager login screen, it would probably have to run as root. My guess is that nearly all synergy users will find it acceptable to have synergy start after login, but I suppose I don't know that for certain.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@benley
Copy link
Member Author

benley commented Sep 19, 2017

Anyone object to merging this?

@Mic92
Copy link
Member

Mic92 commented Sep 19, 2017

Sorry, I just forgot about this.

ExecStart is not executed by a shell, hence && cannot be used
@Mic92
Copy link
Member

Mic92 commented Sep 20, 2017

Have you tested that you can still connect to the client with this configuration?

@Mic92
Copy link
Member

Mic92 commented Sep 20, 2017

wiki link shows 404.

@orivej
Copy link
Contributor

orivej commented Nov 2, 2017

The wiki is at https://github.com/symless/synergy-core/wiki/Security now.

@benley
Copy link
Member Author

benley commented Nov 2, 2017

I'll finish up this PR soon - I had kinda forgotten about it.

@soredake
Copy link

soredake commented Apr 6, 2018

Any progress?

@benley
Copy link
Member Author

benley commented Apr 6, 2018

I haven't been using Synergy recently so I once again forgot about this PR. If anyone is anxious for these features I can finish it up at some point.

@aanderse
Copy link
Member

@benley any motivation to continue with this PR?

@benley
Copy link
Member Author

benley commented May 21, 2019

This is probably a deadend now, because they removed support for crypto in synergy upstream. It's a non-free feature now.

If anybody else wants to pick up this PR please feel free, of course.

@benley benley closed this May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants