[Sugar-devel] Sugar-Server enhancement
mpdmanash at gmail.com
Mon Apr 18 06:15:03 EDT 2016
The feature will ensure that ds-backup will work. Here is how:
ds backup runs rsync over ssh using this command
* /usr/bin/ssh -o "PasswordAuthentication no" -o "StrictHostKeyChecking no"
-i ~/.sugar/default/owner.key -l <serial> <server_address>*
I found this from the source code of ds-backup you provided (ds-backup.py)
It ignores known_hosts file using "StrictHostKeyChecking no", and use
private/public key instead. So, we just have to ensure that it gets proper
<serial_number> and <server_address>.
<serial> is taken from /ofw in case of XOs (static serial machines) or from
/desktop/sugar/soas_serial schema variable.
<server_address> is taken from /desktop/sugar/backup_url schema variable.
Hence we set the appropriate values into /desktop/sugar/soas_serial and
/desktop/sugar/backup_url during registration from schoolserver.py to
ensure ds-backup functionality.
On Mon, Apr 18, 2016 at 3:08 PM, James Cameron <quozl at laptop.org> wrote:
> On Sun, Apr 17, 2016 at 02:54:54AM +0530, Manash Raja wrote:
> > Hi,
> > [...]
> > I have tested that we can add to .ssh/config
> > Host custom_server_name
> > HostName 10.105.57.97
> > PasswordAuthentication no
> > StrictHostKeyChecking no
> > IdentityFile ~/.sugar/default/owner.key
> > User <serial>
> > [...]
> > 3. How do we expect a human user to use ssh? the longer command or
> > .ssh/config based command? or simply ssh user at server with
> > constant modifications to known_hosts.
> Human users of SSH would be rare.
> Perhaps the human user of SSH may be ignored, concentrating instead on
> ensuring the ds-backup will complete even if the host key has changed.
> James Cameron
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel