View source for Talk:BeagleBoard/GSoC/Bonescript remote deployer

From eLinux.org
Jump to: navigation, search

Contents

Thread titleRepliesLast modified
Need security first409:44, 29 March 2017

Need security first

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

 

Return to Thread:Talk:BeagleBoard/GSoC/Bonescript remote deployer/Need security first.

With a level of security what do you think about? If a user want, he can change the SSH username and password on the board and configure the remote deployer with custom username and password or with an SSH Key (I added this thing in my last review of proposal)

Francesco guardiani (talk)01:45, 22 March 2017

If we can simply use ssh, then a simple shell script on top of 'scp myscript.js debian@beaglebone.local:/var/lib/cloud9/autorun/' will actually already do the trick. I was thinking we needed to do something to secure the BoneScript web server and that it would be handling the connection. At one point, I was building up my testbanch to do BoneScript RPC testing: https://github.com/jadonk/bonescript/blob/master/test/TODO/remote_bonetest.js. With the PRC, you can simply do "b.writeTextFile("/var/lib/cloud9/autorun/myscript.js", MYSCRIPT_JS);".

13:57, 22 March 2017

Okay so you think I have to switch to Bonescript RPC and add a security layer on Bonescript Web Server? For the script management, I have to use a procedure created ad hoc inside the Bonescript Web Server or can I use the systemd remote manager?

Francesco guardiani (talk)01:05, 23 March 2017

What is the "systemd remote manager"? Is this the '-H' argument? That seems helpful. Why is anything special needed to do that? Sounds like a nice blog post, not a GSoC project.

09:44, 29 March 2017