Open topic as PDF Version 1.7

Create a Custom Key

Keys are passwords for sessions.

The same default key is a part of every new show file. It is used unless a custom key is created and used instead.

The key is a long hexadecimal hash value generated by a seed word or a set of characters.

Keys can be Inserted/Created, Deleted, Imported, and Exported. Locked keys cannot be edited or deleted.

Keys are selected when a session is created.

All the described key operations are done from the Network Key Registry menu.

Open the Network Key Registry menu

1. Press the Menu key.
2. Tap the Network button.
3. Tap the Keys button on the left menu.

This opens a menu like the one in the image above.

There are a few important columns in the menu:

• Lock:
  This column indicates if the key is locked. The default key is locked as a default. When a seed is changed then the key is automatically locked. Edit this field to unlock a key.
• No:
  This is the key number.
• Name:
  This is a user-friendly name for the key. The name can be edited if the key is unlocked.
• Seed:
  The seed is a hash value. This can be edited on unlocked keys. Any text input can be used as a seed to create a hash value. The hash value cannot be manually input as this would create a new hash using the input as a seed. The original seed input needs to be known to be able to manually recreate the hash. The default value for a new key is the same seed value as the default key.
• MAnet:
  When this is set to Yes, then the key gives access to the MAnet area, this is for instance the possibility to join a session.
• Remote Call:
  When this is set to Yes, then the key gives access to the Remote Call area, this is for instance the possibility to use the webremote into a station, network updating the software, RemoteCommand, and other commands that affect other stations (for instance, reboot and shut down of other devices).
• Terminal:
  When this is set to Yes, then the key gives access to the Terminal area, this is for instance access to a station's terminal interface.

Using Keys in Sessions

The key is selected before the session is started. If a custom key is selected then other stations need to have the key in the registry list to be able to join or be invited into a session.

The keys can be exported to a USB memory stick and imported into other stations.

Or if the seed is known, then the custom key can be recreated on other stations using the same seed value.

If a station does not have the key that was used when the session was created, then it cannot be a part of the session. The joining station does not need to have the key selected in the Network Menu, but it needs to be in the Network Key Registry list.

Requirement for the next few operations:

The Network Key Registry menu is opened.

Create a new Key

Keys are created like most new elements.

1. Select the row where the key should be inserted.
2. Tap Insert.
3. (Optional) Edit the Name field to give the key a useful name.
4. Edit the Seed field and type a word or a random set of characters. This input is converted to a hash number.

Notice that the row is locked as soon as the seed field is changed. It can be unlocked and edited afterward. The lock is to prevent accidental change of the key.

Delete a Key

A locked key cannot be deleted. Follow these steps to delete a key.

1. Select the row with the key to be deleted.
2. Edit the Lock field to unlock the row - the field should be empty for unlocked.
3. Tap Delete.

The key is now deleted.

Export a Key

Keys can be exported and brought to other stations manually.

1. Select the row with the key to be exported.
2. Tap Export.
3. Select the desired drive in the pop-ups title bar.
4. Give the exported file a name.
5. Tap Export in the pop-up.

The key is now exported to the selected drive.

Import a Key

Keys can be imported into a station.

1. Select the "New Key" row.
2. Tap Import.
3. Select the desired drive in the pop-ups title bar.
4. Select the desired file.
5. Tap Import in the pop-up.

The key is now imported to the station.

Select different version- latest - 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0

  previous next

Open topic as PDF