search

haiwen / seafile-client

Seafile desktop client.
http://seafile.com
Apache License 2.0
471 stars 279 forks source link

Problems on the terminal server #29

Closed kama3 closed 10 years ago

kama3 commented 10 years ago

We use seafile client on a terminal server with multiple users. When the first user launch client, seaf-daemon.exe starts on his behalf. On other users seaf-daemon.exe doesn't start. Synchronization task run as first user who does not have access to the resources of others. Task list of all users available to others.

lins05 commented 10 years ago

Hi,

Seafile client has two component: seaf-daemon and ccnet daemon, communicating with each other using a local port.

When each user use "seaf-cli init" to initialize his client configuration, the port in the configuration is the same. That's why your seafile client conflict.

To fix your problem:

  1. use "seaf-cli stop" to stop running ccnet/seafile processes.
  2. Modify each user's ccnet configuration file, "ccnet/ccnet.conf", find this section:

[Client] PORT = 13419

And change the port number, so that each user has different ports.

  1. Now each user can start his own client without problems.

Regards.

On Fri, Nov 1, 2013 at 5:05 PM, kama3 notifications@github.com wrote:

We use seafile client on a terminal server with multiple users. When the first user launch client, seaf-daemon.exe starts on his behalf. On other users seaf-daemon.exe doesn't start. Synchronization task run as first user who does not have access to the resources of others. Task list of all users available to others.

— Reply to this email directly or view it on GitHubhttps://github.com/haiwen/seafile-client/issues/29 .

kama3 commented 10 years ago

Thank you, everything works. But what about when I have more than 30 users?

lins05 commented 10 years ago

You can assign the port value increasingly, can't you?

epe commented 9 years ago

good to know. maybe find a solution that works automatically. Also relevant when several people use one notebook together.

nascheme commented 7 years ago

It this port number sharing still an issue with the current software (version 6.0.0)? It seems like on a multi-user Windows system, the seaf-daemon port still gets shared between users by default (port 13419). That seems really bad. Isn't there a security issue if every user is allowed to connect to the default port and issue commands to the daemon? I'm not familiar with the daemon's protocol but it seems like a security problem.

I can think of a few improvements. First, at least the seaf-daemon process could remember the user ID of the user starting it. If the connecting GUI client doesn't match the user ID, show a warning or disallow it from using the daemon.

Better would be to generate a random unused port and save it to the ccnet folder somewhere. Then the client to read the file to find which port to connect to.