Background
IPA SecurityCamp 2014
● Raspberry pi IDS Development
https://github.com/kendemu/embeddids● Furniture Injection
Robot Operating System
・ visualization・ IPC・ Package management・Multithread/Process/Clustering・ Image/PointCloud Processing ・ Robot Modeling / Simulation・ Cross-platform
・ Navigation・ Program Scalability
ROS Technical Overview
・Message : XML-RPC(HTTP-based)
・ runs through TCP usually
・ The namesystem of process called “Master”
manages the services http://wiki.ros.org/ROS/Technical%20Overview
1. a service register a Name to the Master
2. a service query other services through Master
3. a service establishes TCP/IP connection with other
services
4. the services exchange the connection header
5. a service require the serialized message
6. the other service respond with the serialized message
Connection of ROS Node(Process/Service)
Background of meeting @jitomesky
Repairing the Intel Edison which I had made a
fatal error on the Operating System side
Test Environment:Gazebo Simulator with Turtlebot
http://qiita.com/kendemu/items/f915c7c2498b04e097cc
Negative effects
1. Remote Control is possible just by spoofing packets
2. How to spoof packets : TCP Spoofing
3. The robots nowadays connect to the Internet → critical problem for robots
SolutionSSH,IPSec,SLL/TLS Encryption
Problem : Slow for Robot Control
→Needs of fast encryption※Using IPSec,VPN make network connection more than 6 times slower
http://d.hatena.ne.jp/nori_no/20100919/1284875253
※ROS XML-RPC Packet length is about
400~600 bytes(496±99.8 bytes)
(by my calculation & datasets)
Pepper : Cross DevelopmentBut wanted to do in native
environment
Normally, just the GUI Software abovePepper OS is NaoQiOS, customized Gentoo※
Login Pepper with tty
gcc/g++, openni,opencv,gdb,wget,pulseaudio is usable
No X environment, package manager