Skip to content

Latest commit

 

History

History
91 lines (72 loc) · 2.77 KB

SETUP.md

File metadata and controls

91 lines (72 loc) · 2.77 KB

PAM SETUP

Requirements:

  • GDM (GNOME Display Manager)
  • gcc compiler

SETUP: Instructions are for Debian based systems that have GNOME.

  1. Need to install all the dependencies for PAM and the deauthentication server:
cd pam
sudo make install

It'll install various dependencies such as:

#PAM libaries
sudo apt-get install libpam0g-dev
sudo apt-get install libglib2.0-dev

#Install bluez
sudo apt install bluez
sudo apt-get install libbluetooth-dev

make install will also create the directory /lib/security (or lib64/security on Fedora) if it does not exist and /etc/proxy_auth.

  1. Compile: Assuming you are in the pam directory of the project (i.e. $(INSTALLATION FOLDER)/proxyAuth/pam)
sudo make
  1. Change PAM GDM Password Configuration:
sudo vi /etc/pam.d/gdm-password

and add the following near or at the top of the file:

#proxyAuth
auth sufficient pam_proxy.so
auth required pam_warn.so

To add Trusted Device

  1. Create the directory if it does not exist: /etc/proxy_auth/
    • This is where all the user's MAC Addresses are stored
  2. Create a file that lists the user's trusted bluetooth devices: echo <bluetooth_address> >> /etc/proxy_auth/$USER

Running Bluetooth Server

Requirements:

  • Follow the instructions from here. I'll list the steps though:

  1. sudo vi /etc/systemd/system/dbus-org.bluez.service

  2. Change ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --compat

  3. Add the following line to the file: ExecStartPost=/bin/chmod 777 /var/run/sdp

The permissions of /var/run/sdp changes on each reboot which is why we add the following line to update the permission each time we boot up.

This is to avoid segmentation fault when running sdp tools. According to the link above, sdptool is broken in Bluez 5.

  1. Restart bluetooth:
sudo systemctl daemon-reload
sudo systemctl restart bluetooth

Note: If you are still encountering issues, it may be due to the fact that your bluetooth service is looking at another configuration file:

sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: active (running) since Wed 2020-04-01 00:34:23 EDT; 7s ago
     Docs: man:bluetoothd(8)
 Main PID: 8903 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 1.1M
   CGroup: /system.slice/bluetooth.service
           └─8903 /usr/lib/bluetooth/bluetoothd

As you can see, you will need to edit /lib/systemd/system/bluetooth.service instead.

Running:

  • Compile the server: gcc -o server rfcomm-server.c -lbluetooth