Copyright (C) 2015-2017, Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/.
The vsomeip stack implements the http://some-ip.com/ (Scalable service-Oriented MiddlewarE over IP (SOME/IP)) protocol. The stack consists out of:
- a shared library for SOME/IP (
libvsomeip.so) - a second shared library for SOME/IP's service discovery (
libvsomeip-sd.so) which is loaded during runtime if the service discovery is enabled.
Secure SOME/IP introduces security functionalities on top of vsomeip through
the design and development of a two-phase security protocol tightly integrated
within SOME/IP and strongly based on the usage of well-established cryptographic
algorithms to provide the actual protection.
In particular, the two characterizing steps of the protocol are:
-
session establishment, independently performed at start-up time between the application offering a service and each requester by means of asymmetric cryptography mechanisms, to guarantee that only authorized parties can start the communication and to share the necessary information for the subsequent protection phase;
-
message protection, which provides the actual protection to the messages exchanged across the network: symmetric cryptography algorithms and the previously exchanged session parameters are exploited to authenticate and/or encrypt the packets according to the requested security level.
Every service instance can be assigned to a different security level, to allow for a trade-off between the requests in terms of protection and the increase in latency. Available possibilities are:
-
nosec, corresponding to vanilla SOME/IP;
-
authentication, assuring that only allowed applications can send messages associated to a specific service: it attests data authentication, integrity and prevents message replay;
-
confidentiality, guaranteeing all the security properties offered by the authentication level and, additionally, data confidentiality, to preclude unauthorized parties from accessing the exchanged information.
Additional information concerning the configuration of the the different security functionalities can be found in the vsomeip user guide.
- A C++11 enabled compiler like gcc >= 4.8 is needed.
- vsomeip uses CMake as buildsystem.
- Secure vsomeip uses openssl >= 1.1.0
- vsomeip uses Boost >= 1.55:
Ubuntu 14.04:
sudo apt-get install libboost-system1.55-dev libboost-thread1.55-dev libboost-log1.55-dev
Ubuntu 12.04: a PPA is necessary to use version 1.54 of Boost:
-- URL: https://launchpad.net/~boost-latest/+archive/ubuntu/ppa
--sudo add-apt-repository ppa:boost-latest/ppa
--sudo apt-get install libboost-system1.55-dev libboost-thread1.55-dev libboost-log1.55-dev
For the tests Google's test framework https://code.google.com/p/googletest/[gtest] in version 1.7.0 is needed. -- URL: https://googletest.googlecode.com/files/gtest-1.7.0.zip
To build the documentation asciidoc, source-highlight, doxygen and graphviz is needed:
--sudo apt-get install asciidoc source-highlight doxygen graphviz
For compilation call:
mkdir build
cd build
cmake ..
makeTo specify a installation directory (like --prefix= if you're used to autotools) call cmake like:
cmake -DCMAKE_INSTALL_PREFIX:PATH=$YOUR_PATH ..
make
make installTo predefine the unicast address, call cmake like:
cmake -DUNICAST_ADDRESS=<YOUR IP ADDRESS> ..To predefine the diagnosis address, call cmake like:
cmake -DDIAGNOSIS_ADDRESS=<YOUR DIAGNOSIS ADDRESS> ..The diagnosis address is a single byte value.
To compile vsomeip with signal handling (SIGINT/SIGTERM) enabled, call cmake like:
cmake -DENABLE_SIGNAL_HANDLING=1 ..In the default setting, the application has to take care of shutting down vsomeip in case these signals are received.