Hanover Public Library Libki Install

1) Libki Server Install

2) Libki Client Install
3) Extra Client Side Applications to make Libki run smoother
-All needed files for Libki-Client and Client side applications are located on the “Library
Installers” USB stick (Green Tag, Black Memorex USB)

Libki Server(1)
Install Debian from the debian-jessie DVD’s. Follow along with the prompts and choose
defaults for all options. Do not install the GRUB boot loader on top of the MBR if you intend to
use this computer primarily as a windows machine. Set up a user account and a root password.
The ones used for the old install are in the form of Username: Password

librarian:hanover and root:hello

Backup librarian:hanlib1 and root:hanoverlib21

Root: Hanover and librarian: hanover21

Once the install is complete run the following commands:

sudo nano /etc/apt/sources.list

modify the file so that it looks like this:

deb http://httpredir.debian.org/debian jessie main contrib non-free

deb-src http://httpredir.debian.org/debian jessie main contrib non-free

deb http://httpredir.debian.org/debian jessie-updates main contrib non-free

deb-src http://httpredir.debian.org/debian jessie-updates main contrib non-free

 deb http://security.debian.org/ jessie/updates main contrib non-free

deb-src http://security.debian.org/ jessie/updates main contrib non-free

Once the file is modified run the following commands:

Apt-get update

Apt-get install curl

Now we will follow along with this guide on installing libki-server:

https://github.com/Libki/libki-server/blob/master/README.md

Remember to install docker-engine and docker-compose first. The guides for these are listed on
the github page as well.

https://docs.docker.com/engine/installation/linux/debian/

https://docs.docker.com/compose/install/

With Docker installed successfully go back to the libki readme and continue with the
installation. With docker installed the remaining steps are simply:

Apt-get install git

sudo mkdir -p /var/libki/app

sudo chown $USER:$USER /var/libki/app
git clone https://github.com/Libki/libki-server.git
/var/libki/app
cd libki-server/
cp libki_local.conf.example libki_local.conf
patch <docker/libki_local.conf.patch
##double check that Libki_local.conf is pointing to the right place:

<connect_info>
dsn dbi:mysql:database=libki;host=libki_mysql

docker-compose up -d
docker-compose exec libki perl /libki/installer/update_db.pl
## Create a new user account, make sure that you change the username
## and password
docker-compose exec libki perl
/libki/script/administration/create_user.pl -u libkiadmin -p
some_password -s -m 999

sudo cp docker/ensure_libki_running /etc/cron.d/

sudo chown root:root /etc/cron.d/ensure_libki_running

##ensure Libki is running and create a backup scripts.

sudo cp docker/backup_libki /etc/cron.d/
sudo chown root:root /etc/cron.d/backup_libki

Once installed and running verify that it is working by looking up the ip address of eth0 with:

Ifconfig

Then look up the server with another computer on the network. Search it with the ipaddress
that you just found and the port number that it is running on. Ie:

http://192.168.0.150:8080 If you can see this page libki server is up and running. Next
remove the server from where it is and install it onto the 192.168.0.0/24 network and modify
its ip address:

Set your libki servers ip address to static: I used 192.168.0.150 choose any ip address on the
192.168.0.0/24 range. Do this by either modifying the /etc/network/interfaces file to look
something like this:

auto eth0

iface eth0 inet static

address 192.168.0.150

netmask 255.255.255.0

gateway 192.168.0.1

or run a command like this:

 ifconfig eth0 192.168.0.150 netmask 255.255.255.0

Verify internet connectivity by pinging a machine you have setup on the 10.0.1.0/16 network
that has icmp allowed. Remember that the 192.168.0.0/24 network has no internet
connectivity so make sure you have everything else setup before completing this step.

Once the server is up and running, run the commands:

cd libki-server/
docker-compose up -d

to bring libki-server up.

Double check crontab –e make sure there are full path names! Ie.
* * * * * /usr/bin/perl -I /home/libki/perl5/lib/perl5
/var/Libki/app/script/cronjobs/libki.pl > /home/libki/libki-crontab-minute.log
2>&1

0 0 * * * /usr/bin/perl -I /home/libki/perl5/lib/perl5
/var/libki/app/script/cronjobs/libki_nightly.pl > /home/libki/libki-crontab-
day.log 2>&1

TRIPLE CHECK ALL CRONTABS!!!!!!!!!!!!!!!!!! Check crontab on server(root and librarian), and
crontab in the dockerised container.

Crontab –e

Double check all paths are complete and all permissions are set properly.

Check /var/mail/ for any crontab errors from mail

docker exec –ti libki /bin/bash

crontab –e

put this inside the dockerised crontab:

PATH=/root/perl5/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

0 0 * * * perl /libki/script/cronjobs/libki_nightly.pl && date>>libki_nightly.log

 Non Dockerized crontab (normal crontab)
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

0 18 * * 6 cd /var/libki/app && docker-compose exec mysql sh -c 'mysqldump -uroot -

p"$MYSQL_ROOT_PASSWORD" libki' > /var/libki/$(date +"%Y%m%d").sql 2>$

20 0 * * * bash /var/libki/app/mysql_script

0 19 * * 6 bash /var/libki/app/copier

Libki-Client(2)
Use the libki client from:

https://bitbucket.org/libki-kms/libki-client/downloads

use the libki_client_2.0.2.0 (Leela)

any clients passed Leela are unstable and should not be used unless it is clear A LOT of work has
been put into them to bring them up to date.

Before installing point your browser at 192.168.0.150:8080 if you see the libki screen then
proceed to install and set-up libki.

Download(also on a usb) and install the client. During setup use these options:

Client name: PC name, ie CAP15, 1, 2, 3, etc

Backdoor Password: 68dd3cff1c320076dcfa20e49dc06889

Actual password is “hello001” what you see above is the md5 hash of this string.

Server address: 192.168.0.150

Server port: 8080

Don’t bother with the other password at the end, that feature no longer exists.

Double check these settings by running command prompt and entering the following
commands: cd c:/ProgramData/Libki then more “libki kiosk management system.ini”

Make sure all settings are correct, double check the md5 password especially. Use the
command notepad “libki kiosk management system.ini” to edit the file if anything is wrong or
missing. An example of a correct setup is as follows:

[server]

host=192.168.0.150

port=8080

scheme="http"

[windows]

EnableStartButton=1

[node]

logoutAction=logout

onlyStopFor=

onlyRunFor=

location=Hanover

password=68dd3cff1c320076dcfa20e49dc06889

username=Username or library card number

name=Joe

[Note re Client settings files - Libki Kiosk Management.ini – two, one in appdata and one in
programdata/libki – the latter has the important client settings.]

Everything Else(3)
 KeyTweak
Once Libki is setup, it’s time to lock your machine down. Download and install KeyTweak
to change some of the keyboard buttons to prevent unauthorised access. Changes are in the file
KeyTweak_settings.ktw or as follows:

Left-windows=z

Left-alt=x

Right-alt=.

Right windows=/

F8=left alt

Also turn off sticky keys. Press shift 5 times quickly and toggle sticky keys off.

Autoit & Task Scheduler

Install AutoIt.exe and implement the logout.au3 script to run in the task scheduler. Or if
you are confident of your window size feel free to implement the correct logout.exe(1400x900),
or logout1366x768.exe, etc.

Either do 1 or 2. 1) Open task scheduler and import the task “logoutlibki.xml”

2) Open Task scheduler and create a new task called name=“log out”, description=“Logout after
15 minutes of inactivity”. Under the General Tab tick the box for “Run with highest priviledges”
and change the “configure for:” tab to Windows 10.

Under the triggers tab click “New...” set the trigger to “When computer is idle”. Create another
trigger and change it to “At log on of any user”.

Under the actions tab click “New...”, the action is “Start a program”, Details are select
logout.au3 script from wherever you have placed it.

Under conditions toggle the buttons “Start the task only if the computer is idle for:”. You can
uncheck all the other boxes. Set the idle time to 15 minutes and below that to “Do not wait”.

Under Settings check “Allow task to be run on demand”, “If the task fails, restart every:” 1
minute. “Attempt to restart up to: 5 times”. “Stop the task if it runs longer than: 1hour”.

All other boxes should be unchecked.

Windows Settings
 Make sure application notifications are on. The setting is located here on windows 10:
Notifications and action centre -> Show app notifications -> On

Change the login screen background on windows 10. This is fairly simple on win10, and a
pain on win7. On windows 10 simply open Settings->Lock-Screen then change the type from
windows spotlight to picture. The image file we are using is called login.png

LOCK IT DOWN!!!!!!
We are going to use startup-delayer for this. Install it and run it, choose to disable Libki
on start.

Run regedit. Direct it to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Modify userinit REG_SZ from C:\Windows\system32\userinit.exe to C:\

Program Files (x86)\Libki\libkiclient.exe,C:\Windows\system32\userinit.exe or

C:\ProgramFiles\Libki\libkiclient.exe,C:\Windows\system32\userinit.exe

depending on where you have installed Libki to. What these two settings combine to do
is to stop Libki from starting later (and being exploitable) and instead start Libki before userinit.
This will hopefully keep the system secure and will prevent people from getting around logging
on to Libki.

Another way we accomplished this goal was by launching a shell after userinit. Its code
looks something like this:

##Sleep 4;

##Launch libki;

ping –n 4 127.0.0.1 >nul && c:\”Program Files (x86)”\libki\libkiclient.exe

This was done on computer 1 to avoid the taskbar that was popping up over top of libki 95% of
the time.

It is called in the regedit after userinit.exe as c:/Windows/login.exe