This is the website for the Linux Vendor Firmware Service
[ ~ Dependencies scanned by pyup.io ~ ]
If your device is missing a firmware update that you think should be on LVFS please file an issue against this project and apply the Github label missing-firmware.
The official instance is set up using puppet on RHEL 7, on which you could use:
yum-config-manager --add-repo https://copr.fedorainfracloud.org/coprs/rhughes/lvfs-website/repo/epel-7/rhughes-lvfs-website-epel-7.repo
yum install epel-release libgcab1 puppet
git clone https://github.com/hughsie/lvfs-puppet.git
cd lvfs-puppet
hostname admin
puppet module install puppetlabs-vcsrepo --version 2.2.0
cp keys.pp.in keys.pp
vim keys.pp
puppet apply .
You can set up the development database manually using:
$ su - postgres
$ psql
> CREATE USER test WITH PASSWORD 'test';
> CREATE DATABASE lvfs OWNER test;
> quit
Remember to edit /var/lib/pgsql/data/pg_hba.conf and add the md5 auth
method for localhost.
Then create the schema using:
FLASK_APP=lvfs/__init__.py flask-3 initdb
FLASK_APP=lvfs/__init__.py flask-3 db stamp
FLASK_APP=lvfs/__init__.py flask-3 db upgrade
The admin user is set as sign-test@fwupd.org with password Pa$$w0rd.
python3 -m virtualenv env
source env/bin/activate
pip3 install -r requirements.txt
FLASK_DEBUG=1 ./app.wsgi
You may also need to install introspection dependencies.
For example on Ubuntu the following is required:
sudo apt install -y python3-gi gcab gir1.2-libgcab-1.0
On Fedora:
sudo dnf install \
bsdtar \
cairo-gobject-devel \
GeoIP-devel \
gnutls-utils \
gobject-introspection-devel \
postgresql-devel \
postgresql-server \
python3-devel \
python3-pip \
python3-psutil \
python3-virtualenv
You can then set up the default site settings by logging in as the admin, and
then visiting http://127.0.0.1:5000/lvfs/settings/create to set all the unset
config values to their defaults.
./env/bin/celery -A lvfs.celery worker --queues metadata,firmware,celery,yara
./env/bin/celery -A lvfs.celery beat
IMPORTANT: The LVFS needs to be hosted over SSL.
If you want to use LetsEncrypt you can just do certbot --nginx.
Use the test GPG key (with the initial password of fwupd).
gpg2 --homedir=/var/www/lvfs/.gnupg --allow-secret-key-import --import /var/www/lvfs/stable/contrib/fwupd-test-private.key
gpg2 --homedir=/var/www/lvfs/.gnupg --list-secret-keys
gpg2 --homedir=/var/www/lvfs/.gnupg --edit-key D64F5C21
gpg> passwd
gpg> trust
gpg> quit
If passwd cannot be run due to being in a sudo session you can do:
gpg-agent --homedir=/var/www/lvfs/.gnupg --daemon
or
script /dev/null
gpg2...
Use the secure GPG key (with the long secret password).
cd
gpg2 --homedir=/var/www/lvfs/.gnupg --allow-secret-key-import --import fwupd-secret-signing-key.key
gpg2 --homedir=/var/www/lvfs/.gnupg --list-secret-keys
gpg2 --homedir=/var/www/lvfs/.gnupg --edit-key 4538BAC2
gpg> passwd
gpg> quit
If the firmware is already signed with a PKCS-7 or GPG signature and is going
to be shipped out-of-band from the usual LVFS workflow then local.py can be
used to generate metadata for /usr/share/fwupd/remotes.d/vendor/firmware/.
An example of generating metadata:
./local.py --archive-directory /usr/share/fwupd/remotes.d/vendor/ --basename firmware --metadata /usr/share/fwupd/remotes.d/vendor/vendor.xml.gz
This assumes that the firmware CAB files are already in /usr/share/fwupd/remotes.d/vendor/firmware
and will be run on that system.