Skip to main content ↑ ↓
Topic: To Build From Source: Xiphos...For Success, What's Needed? (Read 347 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

To Build From Source: Xiphos...For Success, What's Needed?

I would like to build Xiphos.
When I have tried in the past it failed, I'm not sure why, that was awhile ago.
The instructions from: xiphos.org/download/

Check out the current GIT source tree with:

git clone https://github.com/crosswire/xiphos.git

Then build under Linux using:

cd xiphos
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DGTKHTML=ON
make -C build
sudo make -C build install

Seems so easy...but when you look at the dependencies at github...
https://github.com/crosswire/xiphos/blob/master/INSTALL.md

Code: [Select]
chmcmd                 Creates a Compressed HTML help file (chm)
CMake                  Cross-platform make system
Gtk+-2.0 or GTK+-3.0   The GIMP Toolkit
WebKit1 or Webkit2     Port to Gtk+ of the WebKit rendering engine
appstream-util         Utility to validate AppStream metadata
biblesync>=1.2.0       Protocol to support Bible software shared co-navigation
dbus-glib              API for use of D-Bus from GLib applications
desktop-file-validate  Validates a desktop file
gcc                    GCC, the GNU Compiler Collection
gconfmm                C++ wrappers for GConf
gtkhtml                Lightweight HTML rendering/editing engine
intltool               An internationalization tool
intltool               Set of tools to centralize translation
itstool                Translates XML documents with PO files
libgsf                 The G Structured File Library
libuuid                universally unique identifier library
libxml2                XML C parser and toolkit
make                   A GNU tool which simplifies the build process for users
minizip                Minizip contrib in zlib
sword >= 1.8.1         CrossWire Bible Society's Bible software
xmllint                Validates an XML file against an XSD schema
yelp-build             Creates HTML, EPUB, and other files from help files

Is this possible to build on Artix.

Could you explain the steps to build this?
Do you see any potential problems before beginning?

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #1 –
You can install xiphos from arch's extra repo, I just tried and it works all right. Or you can adapt PKGBUILD from there and makepkg locally. As far as I can see there is no systemd needs so it should normally compile in Artix.

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #2 –
Trying offline installation : Offline installation of packages  wiki.archlinux.org/title/Offline_installation

I downloaded xiphos-4.3.1-3-x86_64.pkg.tar.zst and the .sig file using Epihpany Browser from Rackspace Mirror Extra.
note: many repo's viewed in Epiphany Browser crash the tab. bubblewrap is cool, firejail for the browser process, might make tab process fuzzing difficult for they. :D and OOPS! for me. ;-(

cp'd the files into /var/cache/pacman/pkg/
then
Code: [Select]
$ sudo pacman -U /var/cache/pacman/pkg/xiphos-4.3.1-3-x86_64.pkg.tar.zst
loading packages...
error: '/var/cache/pacman/pkg/xiphos-4.3.1-3-x86_64.pkg.tar.zst': invalid or corrupted package (PGP signature)

I'm trying to learn how to do offline package installs.
This only installs one thing at a time, but if I saved my upgrade files, wipe and reinstall artix, How do I install all of the packages offline?

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #3 –
Quote from: tsedek1 – on
and the .sig file using Epihpany Browser from Rackspace Mirror Extra.
Probably this:
Without the .sig file it would have worked. 'pacman -U' will install without the signature file.
However if the .sig file is present (I'm guessing pacman looks in the current working dir?) pacman will verify it.  But it can't because you don't have the arch keyring installed.

Just deleting the .sig file will work but going from your previous threads you probably wont want to do that.
You could also install (and populate) https://archlinux.org/packages/core/any/archlinux-keyring/ but that gets you into the same situation where you'll have to install archlinux-keyring without the .sig file.

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #4 –
Xiphos is one of the programs they attack.
(I hate team sports. I like poker, 1 vs 10, and I win. :D ).

The .sig file is important because I want to ensure file integrity.

These are the most common files assaulted during upgrades:
Firefox (or their forks)
GCC
Linux Firmware
Kernels

Outside of downloading upgrades, firefox and primary social media login tabs, is the most attacked. Using the process to run code until I'm out of memory, sometimes fuzzing, leaving me love messages in the log files...
How do you 'echo 3747 c's' inside a firefox process over a LAN?

As an example: Blocking Youtube Comment Server
You can watch videos but the comments are MITM'd and prevented.
I'm not sure if it's automated or active ctf, capturing composed messages from say mousepad and then blocking the YT Comment Server. When I compose an original message on the fly, something simple, it passes their checks. Then I edit...is how I work around they blocking the comment server.

My current solution is to offline install all of my software before connecting to the internet. I am using Xiphos to learn the process.

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #5 –
Whatever. I'm just telling you why it didn't work.

Re: To Build From Source: Xiphos...For Success, What's Needed?

Reply #6 –
Quote from: gripped – on
Whatever. I'm just telling you why it didn't work.
Yes. Keyring.

The devlopers publish their individual keys, sometimes on their website, or their github repo,
Is it possible to add individual developer keys without the entire arch-keyring?

edit: Can you recommend any LAN-CTF resources? So I can learn what and how and then I can ask better questions.
 
Artix forum uses a single cookie to remember youOK