see-sock-serv, see-stdioe-serv, see-stdioesock-serv, see-stdoe-serv
see-sock-serv -p <PUBL-NAME> | -o <KEYID> | -M <MACHINE>.sar
see-stdoe-serv -p <PUBL-NAME> | -o <KEYID> | -M <MACHINE>.sar
see-stdioe-serv -p <PUBL-NAME> | -o <KEYID> | -M <MACHINE>.sar
see-stdioesock-serv -p <PUBL-NAME> | -o <KEYID> | -M <MACHINE>.sar
see-*-serv
utilities activate or enable standard IO and socket connections for SEE machines using the glibc
architecture.
Ensure that you select the appropriate utility for your SEE machine, because running a host-side utility with more provisions than the SEE machine was linked against causes the SEE machine to abort.
-
see-sock-serv
, for SEE machines that require only sockets. -
see-stdoe-serv
, for SEE machines that require only standard output and error streams. -
see-stdioe-serv
, for SEE machines that require standard input, output, and error streams.
If you are using a nShield Connect, you must set the--no-feature-check
option when running thesee-stdoe-serv
utility. -
see-stdioesock-serv
, for SEE machines that require sockets in addition to standard input, output, and error streams.
Each utility can:
-
Load the SAR file for the SEE machine
-
Load the mandatory
userdata
file -
Provide a selection of socket and I/O streams
SEE machines that require the standard I/O streams or INET domain sockets must be serviced by one of the described host-side utilities. Without an appropriate host-side utility, SEE machine operations requiring any of these streams are blocked until the appropriate service becomes available.
All the see-*-serv
host-side utilities take the same arguments.
Option | Description |
---|---|
Loading the SEE machine |
|
|
The SEE machine is encrypted with key IDENT. |
|
The SEE machine is signed with key whose hash is HASH.
Use this option together with the |
|
Specifies a SEE machine file (packed as a SAR). If you do not specify this option, the SEE machine must have been loaded previously by, for example, running loadmache. |
Starting the SEE world |
|
|
An unpacked |
|
The |
|
Starts the SEE world, passing remaining arguments, which should include an |
Pre-started SEE world |
|
|
The |
|
The |
Tracing |
|
|
Polls the security world’s trace buffer.
The contents are printed to |
|
Functions like the |
HSM options |
|
|
Suppresses the default behavior of the |
|
This option is for debugging.
For the host-side utilities that provide a single service (that is, |
|
The HSM onto which the SEE machine is to be loaded. |
|
Only permits userdata and machine-image files from the |
Help options |
|
|
Displays help for the utility. |
|
Displays a brief usage summary for the utility. |
|
Displays the version number of the Security World Software that deploys the utility. |
Error output from SEE machine with SEElib architecture
You cannot use the see-*-serv
host-side utilities to load SEE machines built with the SEElib
architecture.
If you try to do so, the utility returns a message similar to
FATAL: SeeHostCallProvision_Init (prefix `nC/HC/sock/INET ') failed:
SeeHostcallProvisionFailed
This is the expected behavior caused by the host utility sending SEEJob
s that the SEE machine cannot understand or to which it cannot respond correctly.
You can use the loadmache
command-line utility to manually load SEE machines built with the SEElib
architecture.