Difference between revisions of "User Experience"

From Balthazar
 
Line 4: Line 4:
  
 
After the initial hardware initialization sequence and after powering on ''' Balthazar'', the first '''GUI''' that is presented is '''Secure Boot Environment''' from where the user can choose an encrypted boot device or a bootable volume.  
 
After the initial hardware initialization sequence and after powering on ''' Balthazar'', the first '''GUI''' that is presented is '''Secure Boot Environment''' from where the user can choose an encrypted boot device or a bootable volume.  
After the password is given, '''VSBE''' allows the boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process, the keyboard's firmware is initialized and provides secure compression of an input stream. The usual window manager's log-in dialog is presented as one more password is required to finish the whole boot sequence into the user's GUI desktop. '''Veronica''' sits between hardware, kernel, keyboard, and a userspace and manages booting and most of the '''Balthazar''''s internal encrypted communication.   
+
After the password is given, '''VSBE''' allows the boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process, the keyboard's firmware is initialized and provides secure compression of an input stream. The usual window manager's log-in dialog is presented as one more password is required to finish the whole boot sequence into the user's GUI desktop. '''Veronica''' sits between hardware, kernel, keyboard, and a user space and manages booting and most of the '''Balthazar''''s internal encrypted communication.   
  
 
== Classroom and office user-case scenarios ==
 
== Classroom and office user-case scenarios ==
Line 26: Line 26:
 
[[File:Park security.png|center]]
 
[[File:Park security.png|center]]
  
Afterschool activities can be performed in city parks where there is no network. The local network can be made or an access point could be set on a mobile device.
+
After school activities can be performed in city parks where there is no network. The local network can be made or an access point could be set on a mobile device.

Latest revision as of 10:11, 11 February 2022

User Experience

"Veronica" Secure Boot Environment

After the initial hardware initialization sequence and after powering on Balthazar, the first GUI' that is presented is Secure Boot Environment from where the user can choose an encrypted boot device or a bootable volume. After the password is given, VSBE allows the boot sequence to be continued and the whole system is initialized. This ensures proper encryption between hardware and a currently mounted volume or a device. During the boot process, the keyboard's firmware is initialized and provides secure compression of an input stream. The usual window manager's log-in dialog is presented as one more password is required to finish the whole boot sequence into the user's GUI desktop. Veronica sits between hardware, kernel, keyboard, and a user space and manages booting and most of the Balthazar's internal encrypted communication.

Classroom and office user-case scenarios

Different scenarios on what BPCD could do for different users are illustrated to show what is at stake, starting from the classroom to the outdoor activities out of the schools, organizations and just an average user's environments.


Classroom monitor security.png

A teacher is monitoring students while they play with robots.
Each student's screen is also shown on the teacher's display.
It is a feature called a "classroom control in a trusted networked environment".


Street security.png

Young users are playing on the street in a public outdoor area in an untrusted networked environment.


Park security.png

After school activities can be performed in city parks where there is no network. The local network can be made or an access point could be set on a mobile device.

Nlnet banner.png NGI0 tag.png NGI0Entrust tag.png