HowTo: Easy Build LKRG Debian Package without Signature Verification
This page is archived.
Here are easier instructions on how to build the LKRG Debian Package from source code without verifying software signatures. Instructions with better security and more explanation can be found here.
Donate
The build process for any of the packages by Kicksecure developers is very similar. This wiki page explains how to build the package lkrg. By replacing the package name lkrg
with the name of any other package you might be interested in building, that other package would be built. You have two options.
- A) Instructions on this page about how to build the
lkrgpackage from source code without verifying software signatures for simplicity.
OR
Get Build Dependencies
[edit]Update your package lists.
sudo apt update
Install from the Debian repository.
sudo apt install build-essential devscripts git
Change Directory to Build Folder
[edit]This chapter is recommended for better usability, but is not strictly required. [1]
Create folder ~/lkrg-build.
mkdir -p ~/lkrg-build
Change directory to folder ~/lkrg-build.
cd ~/lkrg-build
Get the Source Code
[edit]Get the the package's source code.
git clone START_WIDGET"'-b9a17ac2fd90c44eEND_WIDGET
Remember it is Kicksecure, not kicksecure! If you are prompted for a username for github, it means you have mistyped the web address.
Change Directory to Source Code Folder
[edit]Enter the package's source code folder because later on package build commands are expected to be run from the root of the source folder.
cd lkrg
Choose Version
[edit]This is optional if you want to build from the master branch.
Do not use version 0.1; choose a sensible version number.
git checkout 0.7.1-1
Build the Package
[edit]dpkg-buildpackage -b
Build Result
[edit]When a package is built using dpkg-buildpackage the resulting packages will be created in the parent folder. That is, in this case in the ~/lkrg-build folder.
ls ../
Should show something like this.
lkrg lkrg0.7.1-1-1_amd64.buildinfo lkrg0.7.1-1-1_amd64.changes
Installation
[edit]sudo dpkg -i ../lkrg_0.7.1-1-1_amd64.deb
Clean Up
[edit]Delete temporary debhelper files in the package source folder as well as debhelper artifacts (.deb file etc.) in the parent folder.
1) Show extraneous temporary debhelper files.
git clean -ndff
2) NOTE: Read the above output carefully if you added your own files to that folder.
If that looks good, actually remove.
git clean -dff
3) Delete debhelper artifacts (.deb file etc.) in the parent folder.
TODO: document
Footnotes
[edit]- ↑
When a package is built using
dpkg-buildpackagethe resulting packages will be created in the parent folder. It is better for usability if this is not the user's home folder since many other files may already reside there. This makes the build result files more difficult to find or delete. This is a missing Debian feature. See: dpkg-buildpackage: support output directory other than ..
A secure by default operating system with the latest security research in place.
At
Kicksecure we value freedom and trust, supporting Open Source and Freedom Software
2012-
2025 ENCRYPTED SUPPORT LLC
We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!
Credits and Source Code
[edit]The original source software is maintained by Adam "pi3" Zabrocki. See also authorship
This website with Debian package build instructions and LKRG Debian Package Website is the software fork homepage for LKRG, with a focus on easy installation, added user documentation, and integration with Whonix, Kicksecure, Debian, and other distributions. The software fork source code can be found here.
Footnotes
[edit]
A secure by default operating system with the latest security research in place.
At
Kicksecure we value freedom and trust, supporting Open Source and Freedom Software
2012-
2025 ENCRYPTED SUPPORT LLC
We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!