WibuKey Help

Contents

  WibuKey

WkLAN Network Server

     
 

WibuKey - A protection system

WibuBox Versions

RunTime Installation

WibuBox Remote Programming

Configuration with WkConfig

User Tool wku

WkLAN Network Server

Configurations

WibuKey FAQ

General

The WibuKey network server enables the access to WibuBoxes over the network. This allows copy protection of an application as well as limitation of the number of users that access the application at the same time. Such a WibuKey network server can run on any computer in the network, it is not necessary to run it on a primary network server, like your mail or file server.

WibuKey offers two different methods to protect an application in the network with the WkNet and WkLAN. network subsystems. On Linux and Mac OS X only the WkLAN protocol is supported.

WkLAN is protocol based, data is transferred synchronously between server and clients. WkLAN is based on TCP/IP. The current implementation runs on Mac OS&unbsp;X, Linux and Microsoft Windows™.

Depending on the operating system the WibuKey WkLAN network server is called:

  • WkSvMac, on Mac OS 8/9.

  • WkSvMacX, on Mac OS X.

  • WkSvLin, on Linux.

  • WkSvW32, on Microsoft Windows™.


WibuKey Network Server (WkSvLin)

Please note that only one instance of the WibuKey network server can be running at the same time on one system.

On Mac OS X and Linux you can start the WibuKey network server as daemon or as application. The features of both are equal, but the daemon will run as UNIX like background service without screen output.

If you want to start the WibuKey network server as application than it is possible to start as console based application with the additional comand line option -c or with a graphical frontend (default).

On Linux you start or stop the WkSvLin daemon by using the init script:

 /etc/init.d/wksvlin {start|stop|status}

On Mac OS X you start or stop the WkSvMacX daemon by using the application link inside yours WibuKey application folder or by using the SystemStarter:

sudo SystemStarter start "WibuKey Server"
sudo SystemStarter stop "WibuKey Server"

WibuKey WebMonitor

The WibuKey WebMonitor provides information about the running WibuKey network server. The WibuKey WebMonitor is only available if the WibuKey network server is running.

The number of users currently accessing a WibuKey server, at what time they logged on and at what time they did the last access can be viewed from any network station. You can cancel users retrieve internal status information of the network server process and the driver that handles the WibuBox access.

The WibuKey WebMonitor is available as HTTP frontend for any internet browser like Mozilla, Konqueror, Firefox or Safari. To access the WibuKey WebMonitor use the URL http://127.0.0.1:22347 . (Remember: The number 22347 meaning the TCP port configured in Server.ini.)


WibuKey WebMonitor

Configuration

All configuration for the WibuKey network server is stored in the Server.ini configuration file. The location of the configuration file is on Mac OS X /Library/Preferences/com.wibu.WIBU-KEY.Server.ini and on linux it is stored at /etc/wibu/WIBU-KEY/WIBUKEY.INI. Most settings can also be changed by using the prefered application WkConfig.

If you modify the Server.ini configuration file the WibuKey network server must not run.

The configuration options for the WibuKey network server are divided into five sections:

  • Settings

  • HTTP

  • HlmFiles

  • RemoteAccess

  • WkLAN

Settings Section

The basic configuration settings of the WibuKey network server are stored in the [Server] section of the Server.ini file. The following values can be specified:

 Entry Key Word 

Meaning

 BindAddress  

Specifies the IP address which is used by the WibuKey server.

 WkLAN 

Enables (1) or disables (0) the WkLAN functionality.

 Logging 

Activates (1) or deactivates (0) the logging of all actions to a file.

 LoggingPath 

Specifies the location of the logfile. The server process must have write permissions for this location.

 StartDaemon 

Specifies if WkLan network server will be start automatically if you restart your computer.

 AccessFsb 

If this option is active (1), access to Firm Codes in the range of 90-99 is possible from the network. This range is reserved for Firm Security Boxes (FSB). This option has to be activated if a Firm Security Box is connected to a WkLAN server and every network user should have access to this FSB to program WibuBoxes.

 NoBoxPgm 

Must be activated (1) to avoid the reprogramming of the WibuBoxes connected to this WkLAN server from other stations.

 WkLanTimeOut 

Specifies the timeout value in minutes. An allocated slot in the WkLAN client list is freed automatically if the allocating process has not accessed its slot in the specified time. If this entry is not set, a default timeout value of 1440 (24 hours) is used.


WkLAN Section

The WkLAN configuration settings of the WibuKey network server are stored in the [WkLAN] section of the Server.ini file. Following values can be specified:

 Entry Key Word 

 Meaning

 IpPort  

Specifies the TCP/UDP port number to be used for the WkLAN communication. WkLAN uses the default port 22347 for communication. If this port is already used by another process it can be changed here. This change also has to be done for the WkLAN clients. Otherwise there will be no communication between clients and server. (See also WIBUKEY.INI).


RemoteAccess Section

Access rights to control the access to the WibuKey server can be specified in the [RemoteAccess] section. The corresponding entries are "ip_address = Permission" where 'Permission' can be:

 Permission   

Meaning

 1  

Read content.

 2  

Read content (Details) (not implemented yet).

 4  

Allocate license.

 8  

Delete user.

 16  

Delete all users (not implemented yet).


Combinations are possible, e.g. 7 = 'Read content and Allocate license' is permitted, 'Delete user' is denied. The entry "Default"=31 specifies the rights of users which aren't explicitly declared. These rights can be restricted, too. Due to compability reasons all these actions are permitted by default.

HlmFiles Section

HLM control files are specified in the Server.ini configuration file in the [HlmFiles] section. Each variable in this section has the following form (and is a argument for a path of the HLM Control File):

FileN=hlm_file

Note, the N behind the File is a number from 1 to 9.

The HLM setting is interpreted only when the WibuKey Server is started. If the HLM settings are changed, the server process must be stopped and restarted to read the new settings.

HTTP Section

The HTTP configuration settings of the WibuKey network server are stored in the [HTTP] section of the Server.ini file. Following values can be specified:

 Entry Key Word 

 Meaning

 HtmlArchive 

Path to WebMonitor HTTP interface container.

 RemoteRead 

Enables (1) or disables (0) remote read access to the WebMonitor.

 RemoteWrite 

Enables (1) or disables (0) support for RemoteCommand operations.

 RemoteCommand  

Enables (1) or disables (0) support for remote commands from the WebMonitor (i.e. for cancelling of users from remote computers).