uvisor | mbed OS uVisor -- device security layer for ARMv7M | Security library

by ARMmbed C Version: v0.26.0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | uvisor Summary

uvisor is a C library typically used in Security applications. uvisor has no bugs, it has no vulnerabilities and it has low support. However uvisor has a Non-SPDX License. You can download it from GitHub.

mbed OS uVisor -- device security layer for ARMv7M microcontrollers

Support

Quality

Security

License

Reuse

Support

uvisor has a low active ecosystem.

It has 125 star(s) with 70 fork(s). There are 92 watchers for this library.

It had no major release in the last 12 months.

There are 69 open issues and 84 have been closed. On average issues are closed in 55 days. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of uvisor is v0.26.0

Quality

uvisor has 0 bugs and 0 code smells.

Security

uvisor has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

uvisor code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

uvisor has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

uvisor releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of uvisor

Get all kandi verified functions for this library.

uvisor Key Features

No Key Features are available at this moment for uvisor.

uvisor Examples and Code Snippets

No Code Snippets are available at this moment for uvisor.

Community Discussions

Trending Discussions on uvisor

global variables on mbed uvisor

mbed client build error

mbed uvisor dynamically load binary

mbed uvisor and EthernetInterface overflowed

QUESTION

global variables on mbed uvisor

Asked 2017-Mar-30 at 16:28

I have an aplication running on a K64F board with ARM Mbed OS. I takes advantage of the RTOS capabilities and is runnign some different threads to perform various actions. Communication between threads is done using queues defined as global variables on the first part of the code (as defined in the RTOS examples).

...

ANSWER

Answered 2017-Mar-30 at 16:28

You cannot share memory between boxes, uVisor boxes run in isolated memory spaces (which is the whole point of using uVisor).

The only way to communicate between boxes is through RPC channels. See this article under the 'Expose public secure entry points to the secure box' section.

I think you can only pass primitives and struct's (because they're fixed size) over the RPC channel, but that's worth an experiment.

Source https://stackoverflow.com/questions/43120886

QUESTION

mbed client build error

Asked 2017-Feb-20 at 12:18

I am trying to compile the mbed client example on a windows machine for the K64F board. I have installed all the required software as described in the guide https://github.com/ARMmbed/mbed-client-quickstart.

The commands I have run are the following commands:

...

ANSWER

Answered 2017-Feb-20 at 12:18

That's the old example code based on mbed OS 3. Use the example for mbed OS 5 instead.

Source https://stackoverflow.com/questions/42297012

QUESTION

mbed uvisor dynamically load binary

Asked 2017-Feb-16 at 13:06

I have a NXP FRDM-K64F board where I have uvisor running diferent modules in boxes. Is there a way to load the code of one box from an external file? Can uvisor handle boxes dynamically? I would want to create an aplication that can get a binary and set it on a box. Is that supported?

...

ANSWER

Answered 2017-Feb-16 at 13:06

uVisor at the moment does not support modular applications, where each box has its own firmware that can be loaded independently from others.

As Jan pointed out, boxes are determined at compile and link time and end up in a unique, monolithic firmware. Boxes' capabilities are expressed via static ACLs, which are enumerated at runtime and checked for consistency and compatibility (e.g. two boxes cannot claim exclusive ownership of the same peripheral).

A future implementation might allow a more modular setup, as there would be ways to check the integrity of a newly provided box firmware and to reconcile the new ACLs with the existing ones. We don't have plans for it yet, but the current implementation does not exclude that capability.

Source https://stackoverflow.com/questions/42250411

QUESTION

mbed uvisor and EthernetInterface overflowed

Asked 2017-Feb-09 at 16:41

I am quite new to mbed and uvisor so maybe my problem is about understanding how things work. I have a NXP FRDM-K64F board where I am trying to learn about mbed and uvisor. I have succesfully compiled an run some basic examples of tasks running on different boxes. I am trying to connect to the net one of the boxes in uvisor but something is not working correctly.

This is the main file code:

...

ANSWER

Answered 2017-Feb-09 at 16:41

In your main box, change the value for UVISOR_SET_PAGE_HEAP.

With UVISOR_SET_PAGE_HEAP(8 * 1024, 3) in the main box; and 8K heap in the secure box and UVISOR_BOX_STACK_SIZE stack size in the secure box it compiles and links for me (mbed OS 5.3, GCC ARM on K64F).

Source https://stackoverflow.com/questions/42141709

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install uvisor

The basic uVisor example shows how secure interrupts and C++ objects are instantiated in the context of secure boxes.
The uVisor threaded example demonstrates the configuration of multiple boxes containing secure threads.
The secure number store example demonstrates secure communication between boxes and implementation of secure APIs. The example shows how a called box can infer the caller's identity and ownership of secure objects across boots and firmware updates.

Support

The uVisor core supports the following platforms:. To use uVisor on a specific OS, you must complete the porting process for that OS. This requires an additional porting step, which the uVisor porting guide for Mbed OS documents. Currently, uVisor only supports Mbed OS. The Launchpad GNU Arm Embedded Toolchain builds the uVisor prelinked binary images. Currently, uVisor only supports applications built with this toolchain. The minimum required version is 5.4-2016q3.

Find more information at: