Re: [Sugar-devel] Sugar-Server enhancement

replies inline > On April 18, 2016 at 5:24 AM James Cameron wrote: > > > Tony, when you hold down those four game keys you are installing > software from OLPC. Assuming you haven't set up your own firmware > keys and signed your own images. > It's not that hard, installing

Re: [Sugar-devel] Sugar-Server enhancement

Tony, when you hold down those four game keys you are installing software from OLPC. Assuming you haven't set up your own firmware keys and signed your own images. When you refer to "Build 85" or "13.2.5", that is OLPC OS. It was built by OLPC by combining Fedora, Sugar, and Gnome. While we

Re: [Sugar-devel] Sugar-Server enhancement

Hi James, 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 * I found this from the source code of ds-backup you provided

Re: [Sugar-devel] Sugar-Server enhancement

ssh is the tool for administration of deployed servers. However, 'rm -f ~/.ssh/known_hosts' is a simple workaround. Tony On 04/18/2016 05:38 PM, James Cameron 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

Re: [Sugar-devel] Sugar-Server enhancement

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 >

Re: [Sugar-devel] Sugar-Server enhancement

@ Tony, the GUI changes have been reverted to the original "Register / Register again" buttons. :) On Mon, Apr 18, 2016 at 9:29 AM, Tony Anderson wrote: > Jerry, > > I apologize for the word absurd. That was emotional. I should have used > the 24 hour rule. > > The

Re: [Sugar-devel] Sugar-Server enhancement

Jerry, I apologize for the word absurd. That was emotional. I should have used the 24 hour rule. The backup capability is limited to the XO since it is based on its serial-number. If may become applicable to SOAS by providing a generated serial-number for non-XO platforms. "Please tell me

Re: [Sugar-devel] Sugar-Server enhancement

Hi Tony, > On April 17, 2016 at 9:06 PM Tony Anderson wrote: > > > Hi, Dave > > It is absurd for reasons I have specified the first time James made this > statement. Please don't use language such as 'absurd' please, I would personally find that offensive if it were

Re: [Sugar-devel] Sugar-Server enhancement

Hi, Dave It is absurd for reasons I have specified the first time James made this statement. The two scripts are in /usr/bin. They are invoked by the installed Sugar image. The scripts are enabled by /usr/lib/python2.7/site-packages/jarabe/The status is specified in

Re: [Sugar-devel] Sugar-Server enhancement

Sounds good. Make sure not to use the word connect - this refers to making a connection between the client and the server. Using it in this context could create confusion. "He just has to register with the server as normally he would do by: 1. setting the server ip 172.18.96.1 in the network

Re: [Sugar-devel] Sugar-Server enhancement

Let me write the known_hosts file's content again with new line gaps as it might become difficult to read in word warp. : 172.18.96.1 ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBHS52tbpYsMRj24QhsDac9viwiv9pbCyFUYGknxlpsUWvgOxVCBg+vOasdasdSAaSomethingaa=

Re: [Sugar-devel] Sugar-Server enhancement

Hi, Manash After sending the previous e-mail, I got thinking the following situation. An admin goes to a deployment which reports a problem. Each of the deployments for that admin has the schoolserver address 172.18.96.1. This is the case for the three schools in Rwanda and also for the three

Re: [Sugar-devel] Sugar-Server enhancement

Regarding SSH. I think I have found a good solution. (I have tested it.) Thanks @Tony for telling where exactly the problem occurs. Commit : https://github.com/sugarlabs/sugar/pull/679/commits/930726741744ebdf6d464b84b31210aa0897124a Commit message : ds-backup works independently on its own by

Re: [Sugar-devel] Sugar-Server enhancement

In the current backup system, the only involvement of the user is to register. The ds-backup script uses the serial-number of the XO. The 'known_host' check must pass in order for this to work. Normally, this is not a problem because a given deployed XO only ever sees one server. It is usually

Re: [Sugar-devel] Sugar-Server enhancement

Hi, Here are some updates. *ssh:* I found from the source code for ds-backup provided by James http://dev.laptop.org/git/users/quozl/ds-backup/ and while searching along the lines of Tony (*The script stores and retrieves using sftp with authentication by public/private key.*) that communication

Re: [Sugar-devel] Sugar-Server enhancement

The operative code on the school server is /usr/libexec/create_user. What Manash describes is apparently using the db setup by idmgr to list the registered laptops. I don't think you will break compatibility. What I hope we can look at is implementing LDAP as a central authentication for all

Re: [Sugar-devel] Sugar-Server enhancement

> On April 15, 2016 at 6:56 PM Manash Raja wrote: > > > @Jerry, > I haven't modified anything for this feature on the server side. I found > that it uses both idmgr and xs-authserver. But the 5000 port is used by > xs-authserver to display a list of registered laptops. I

Re: [Sugar-devel] Sugar-Server enhancement

On Sat, Apr 16, 2016 at 08:36:22AM +0800, Tony Anderson wrote: > On 04/16/2016 05:51 AM, James Cameron wrote: > >Looks good. A few points on first review; > > > >1. you're changing "Register" and "Register again" to "Connect to > >server", but it isn't clear in the commit message why it is

Re: [Sugar-devel] Sugar-Server enhancement

Re OwnCloud The software is included in xsce; however, the last time I tried it was not configured. The key in OwnCloud is configuration (db, etc.). One concern I have is that we have a way to authenticate users. We are growing the number of server 'services' which require a username and

Re: [Sugar-devel] Sugar-Server enhancement

On 04/16/2016 05:51 AM, James Cameron wrote: Looks good. A few points on first review; 1. you're changing "Register" and "Register again" to "Connect to server", but it isn't clear in the commit message why it is necessary; Register has nothing to do with connect. The word 'connect' should

Re: [Sugar-devel] Sugar-Server enhancement

On Sat, Apr 16, 2016 at 05:26:37AM +0530, Manash Raja wrote: > @James, > > 1.  you're changing "Register" and "Register again" to "Connect to > server", but it isn't clear in the commit message why it is necessary; > > I felt as "Register" refers to an action done for first time (Add new

Re: [Sugar-devel] Sugar-Server enhancement

@James, > 1. you're changing "Register" and "Register again" to "Connect to > server", but it isn't clear in the commit message why it is necessary; I felt as "Register" refers to an action done for first time (Add new laptop entry in the server), while "Register again" means to redo the same

Re: [Sugar-devel] Sugar-Server enhancement

Hi, Jerry /library/user/ refers to the directory on the school server. Currently, the store on the school server is a metadata file and a document file in the Journal directory per Journal object. The Log directory contains the metadata file for Journal objects without a document. The

Re: [Sugar-devel] Sugar-Server enhancement

On Fri, Apr 15, 2016 at 04:02:39PM +0800, Tony Anderson wrote: > Hi, James > > This thread was getting long so I replied only to the most recent > communication. I am sure you have the full thread which shows the > scope of the discussion. You're making it longer, yes, by hijacking it. You can

Re: [Sugar-devel] Sugar-Server enhancement

> On April 15, 2016 at 3:37 AM Tony Anderson wrote: > > > Hi, Jerry > > I am not sure what you mean by 'remote network datastore'. > The objects that are not stored as part of the local journal would need to live somewhere, you have being referring to

Re: [Sugar-devel] Sugar-Server enhancement

Hi, Jerry I am not sure what you mean by 'remote network datastore'. What I am doing now is looking at each Journal object. If is is new (doesn't have Journal in the metadata - Journal showing the item has been backed up to the school server), the script uses sftp to upload it to

Re: [Sugar-devel] Sugar-Server enhancement

> On April 15, 2016 at 12:36 AM James Cameron wrote: > > > On Fri, Apr 15, 2016 at 10:25:59AM +0800, Tony Anderson wrote: > > Hi Manash > > > > The registration process is awkward but not the problem. > > This is unfair scope creep. Manash began by asking about bug #362

Re: [Sugar-devel] Sugar-Server enhancement

Hi, James This thread was getting long so I replied only to the most recent communication. I am sure you have the full thread which shows the scope of the discussion. According to trac bug #362 was opened seven years ago against 0.82 and last looked at three years ago. Several competent

Re: [Sugar-devel] Sugar-Server enhancement

On Fri, Apr 15, 2016 at 10:25:59AM +0800, Tony Anderson wrote: > Hi Manash > > The registration process is awkward but not the problem. This is unfair scope creep. Manash began by asking about bug #362 and has been working to fix that. Now you're asking him to consider a much larger task; not

Re: [Sugar-devel] Sugar-Server enhancement

Hi Manash The registration process is awkward but not the problem. The problem is that rsync is used to create backups of the Journal and no effective means is offered to restore. However, the ultimate problem is thinking of the problem as one of backup. If you try to solve the wrong problem,

Re: [Sugar-devel] Sugar-Server enhancement

Good summary, Manash. 1. a UUID is generated when an OLPC XO laptop is manufactured, then stored in our database and used in our cryptographic firmware security anti-theft feature [1], but for non-OLPC devices it is generated by Sugar, and I've no idea how the server itself uses it, 2. perhaps

Re: [Sugar-devel] Sugar-Server enhancement

Jerry Yes, of course. At the moment, it is proposed for implementation in the GSOC. The use of OwnCLoud is a possibility. Currently, it is down by backup to the /library/users via sftp by a customized version of ds_backup. OwnCloud might make the process more visible and more useful to the

Re: [Sugar-devel] Sugar-Server enhancement

On Wed, Apr 13, 2016 at 09:15:40PM -0500, Jerry Vonau wrote: > Tony, > > What about your remote datastore that you were taking about? What was the > owncloud integration that you were talking about? Is that not a way of > backing up some data? > > > On April 13, 2016 at 8:07 PM James Cameron

Re: [Sugar-devel] Sugar-Server enhancement

Tony, What about your remote datastore that you were taking about? What was the owncloud integration that you were talking about? Is that not a way of backing up some data? > On April 13, 2016 at 8:07 PM James Cameron wrote: > > > On Thu, Apr 14, 2016 at 08:39:10AM +0800,

Re: [Sugar-devel] Sugar-Server enhancement

On Thu, Apr 14, 2016 at 08:39:10AM +0800, Tony Anderson wrote: > Hi, James > > Deployments without a school server obviously do not use the backup. > Deployments without access to the internet vie GSM do not > use that support either. > > I suppose ds_backup.sh and ds_backup.py come from the

Re: [Sugar-devel] Sugar-Server enhancement

Adam The original proposal was to provide a method for an XO to be registered to multiple school servers simultaneously. That doesn't seem to relate to any of your use cases. My concern is increasing the complexity of use by our students. We shouldn't force a configuration decision or action

Re: [Sugar-devel] Sugar-Server enhancement

So what you are saying Tony is that you don't need the feature and you don't care for it. Fine, leave us to it then. We know it is needed, as Daniel first identified in the ticket (on behalf of Argentina), and as Adam has just pointed out. I know the history of the menu option, thanks. On Thu,

Re: [Sugar-devel] Sugar-Server enhancement

Hi, James Deployments without a school server obviously do not use the backup. Deployments without access to the internet vie GSM do not use that support either. I suppose ds_backup.sh and ds_backup.py come from the tooth fairy and not from flashing a Sugar image. The server software was

Re: [Sugar-devel] Sugar-Server enhancement

On Wed, Apr 13, 2016 at 8:17 PM, Tony Anderson wrote: > James > > I can't think of a use case for an XO to access multiple school servers. Apologies am not following all the details of this conversation, but just to point out some of our newer work in Haiti will

Re: [Sugar-devel] Sugar-Server enhancement

James I can't think of a use case for an XO to access multiple school servers. If a school is so large (> 200 XOs), the easy solution is two school servers. However, the XOs access the schoolserver based on SSID and so users can be divided to their own schoolserver by the connection -

Re: [Sugar-devel] Sugar-Server enhancement

OLE Nepal has from the beginning registered the server at each connection eliminating the registration option from the main menu. A second registration recognizes that the laptop is registered and takes no action. Moving from one server to another causes a 'known hosts' issue. This can be

Re: [Sugar-devel] Sugar-Server enhancement

On Thu, Apr 14, 2016 at 02:44:25AM +0530, Manash Raja wrote: > Hi Jerry, > > Please don't forget jarabe/desktop/schoolserver.py is involved, I > personally would prefer that code to be moved into control-panel/network. > Others please chime with your thoughts on this one. > > Yes, if

Re: [Sugar-devel] Sugar-Server enhancement

Hi Jerry, Please don't forget jarabe/desktop/schoolserver.py is involved, I > personally would prefer that code to be moved into control-panel/network. > Others please chime with your thoughts on this one. Yes, if register option is brought to network section, then it will provide better space

Re: [Sugar-devel] Sugar-Server enhancement

Manash, > On April 13, 2016 at 1:58 PM Manash Raja wrote: > > > Hello Jerry, > > Thank you for your help. It worked! As you said, the _REGISTER_URL was > getting overridden by what was set in network control panel. > Cool, glad it was that easy to fix. > I am visiting

Re: [Sugar-devel] Sugar-Server enhancement

Hello Jerry, Thank you for your help. It worked! As you said, the _REGISTER_URL was getting overridden by what was set in network control panel. I am visiting IRC chat room through http://webchat.freenode.net/ in browser as I am facing some troubles with clients due to my proxy enabled internet

Re: [Sugar-devel] Sugar-Server enhancement

Just had a thought, SoaS might have the collaboration server already set in the control-panel -> network, this is different from XOs that have this field blank. Having that field populated would cause jabber_server to override the predefined _REGISTER_URL in src/jarabe/desktop/schoolserver.py. I

Re: [Sugar-devel] Sugar-Server enhancement

Hello Manash, I'll have a bunch of questions, because my crystal ball is in the repair shop. ;) > On April 13, 2016 at 10:45 AM Manash Raja wrote: > > > I have installed XSCE schoolserver on CentOS running in Virtualbox. > I saw your question in the chat-room, please be

Re: [Sugar-devel] Sugar-Server enhancement

I have installed XSCE schoolserver on CentOS running in Virtualbox. 1. Sugar running on another Virtualbox instance can visit http://schoolserver from its browser, but server registration is failing in Sugar if I try clicking on "XO" and then "Register". 2. It seems that sugar

Re: [Sugar-devel] Sugar-Server enhancement

The ticket is up to date. Your task would be to set up a server, e.g. XSCE, http://schoolserver.org/ and then register to it; which is a UI step. Then set up a second server, and register to it; which is a manual process. Then design a UI and UX for either switching registration or detecting

[Sugar-devel] Sugar-Server enhancement

Hello everyone, I was looking at this bug https://bugs.sugarlabs.org/ticket/362 , but I couldn't understand its status quite well. I am interested to work on this enhancement as it is related to my proposed GSoC 2016 proposal and would give me a head start on understanding the present