OpenKiosk manages kiosks across multiple platforms in one integrated software.
OpenKiosk is a multi-platform, open-source kiosk system that aims to be one of the best in the open-source community. It's perfect for use in places like libraries, offices, schools, internet cafes, airports, and conference rooms. OpenKiosk's evolution towards simplicity and elegance in kiosk terminals can be seen in the following prototype screenshots of its client.
OpenKiosk is a centralized management software for kiosks, made up of a collection of programs that work together in a local network. It assumes that resources are shared and centralized, including the Internet connection. This implies that the shared Internet connection to the outside world is assumed always to be on at some point within the local network, maybe a NAT server. The client program automatically limits customers individually from accessing the Internet.
When a user logs in to a kiosk or workstation, the client program sends the login information to the server. The server verifies this data and, if valid, returns the access rights and duration of use for the customer back to the client program. The client program handles the restrictions transparently, including preventing running new programs and making it appear that the Internet connection is down if the time limit is reached or if the administrator stops a customer from using a kiosk/workstation.
OpenKiosk is designed primarily with the multi-user network in mind. From a library containing 20 public browsing terminals to a large internet cafe or convention center containing hundreds to thousands of kiosks or workstations, OpenKiosk is built to scale up. It is not for single stand-alone computers.
The OpenKiosk system has two parts: NodeView, acting as the central server containing the client information database, and the client, the program that sits between the customer and the operating system interface. For automatic usage, it can take in membership card login or interface with more advanced hardware readers like smart card readers. The client is also capable of simple but important tasks such as remote shutdown, instant messaging, and file updates.
There are two versions of clients: the X11 Linux/Unix version, which is an applet that sits on top of the KDE panel, and the Windows version. Requirements for this software include Qt 3.x and Berkeley DB. This release fixed a critical bug in which unclosed socket connections left over time can crash the server.
OpenKiosk is a centralized management software for kiosks, made up of a collection of programs that work together in a local network. It assumes that resources are shared and centralized, including the Internet connection. This implies that the shared Internet connection to the outside world is assumed always to be on at some point within the local network, maybe a NAT server. The client program automatically limits customers individually from accessing the Internet.
When a user logs in to a kiosk or workstation, the client program sends the login information to the server. The server verifies this data and, if valid, returns the access rights and duration of use for the customer back to the client program. The client program handles the restrictions transparently, including preventing running new programs and making it appear that the Internet connection is down if the time limit is reached or if the administrator stops a customer from using a kiosk/workstation.
OpenKiosk is designed primarily with the multi-user network in mind. From a library containing 20 public browsing terminals to a large internet cafe or convention center containing hundreds to thousands of kiosks or workstations, OpenKiosk is built to scale up. It is not for single stand-alone computers.
The OpenKiosk system has two parts: NodeView, acting as the central server containing the client information database, and the client, the program that sits between the customer and the operating system interface. For automatic usage, it can take in membership card login or interface with more advanced hardware readers like smart card readers. The client is also capable of simple but important tasks such as remote shutdown, instant messaging, and file updates.
There are two versions of clients: the X11 Linux/Unix version, which is an applet that sits on top of the KDE panel, and the Windows version. Requirements for this software include Qt 3.x and Berkeley DB. This release fixed a critical bug in which unclosed socket connections left over time can crash the server.
What's New
Version 2.0.6: N/A