PFFW | source tree has links to OpenBSD install sets
kandi X-RAY | PFFW Summary
kandi X-RAY | PFFW Summary
PFFW is a PHP library. PFFW has a Strong Copyleft License and it has low support. However PFFW has 243 bugs and it has 1 vulnerabilities. You can download it from GitHub.
However, the source tree has links to OpenBSD install sets and packages, which should be broken, hence need to be fixed when you first obtain the sources. Make sure you see those broken links now. So, before you can run createiso, you need to do a couple of things:. Note that you can strip down xbase and xfont install sets to reduce the size of the iso file. Copy or link them to the appropriate locations under openbsd/pffw. Now you can run the createiso script which should produce an iso file in the same folder as itself.
However, the source tree has links to OpenBSD install sets and packages, which should be broken, hence need to be fixed when you first obtain the sources. Make sure you see those broken links now. So, before you can run createiso, you need to do a couple of things:. Note that you can strip down xbase and xfont install sets to reduce the size of the iso file. Copy or link them to the appropriate locations under openbsd/pffw. Now you can run the createiso script which should produce an iso file in the same folder as itself.
Support
Quality
Security
License
Reuse
Support
PFFW has a low active ecosystem.
It has 29 star(s) with 3 fork(s). There are 2 watchers for this library.
It had no major release in the last 12 months.
PFFW has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of PFFW is v6.9
Quality
PFFW has 243 bugs (0 blocker, 0 critical, 155 major, 88 minor) and 1446 code smells.
Security
PFFW has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
PFFW code analysis shows 1 unresolved vulnerabilities (0 blocker, 1 critical, 0 major, 0 minor).
There are 111 security hotspots that need review.
License
PFFW is licensed under the GPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
PFFW releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
It has 38619 lines of code, 1382 functions and 215 files.
It has high code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed PFFW and discovered the below as its top functions. This is intended to give you an instant insight into PFFW implemented functionality, and help decide if they suit your requirements.
- Private key exchange .
- Parse key type
- Generates an inline encryption function based on the mode .
- Convert a file_name to an array .
- Append a string
- Sign a subject .
- Utility function to calculate the SHA256 hash
- Divide two values .
- Sets up the inline encryption mode .
- Run a command
Get all kandi verified functions for this library.
PFFW Key Features
No Key Features are available at this moment for PFFW.
PFFW Examples and Code Snippets
No Code Snippets are available at this moment for PFFW.
Community Discussions
No Community Discussions are available at this moment for PFFW.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install PFFW
Download the installation iso file mentioned above and follow the instructions in the installation guide available in the iso file. Below are the same instructions.
Thanks to a modified auto-partitioner of OpenBSD, the disk can be partitioned with a recommended layout for PFFW, so most users don't need to use the label editor at all.
All install sets including siteXY.tgz are selected by default, so you cannot 'not' install PFFW by mistake.
OpenBSD installation questions are modified according to the needs of PFFW. For example, X11 related questions are never asked.
512MB RAM and an 8GB HD should be enough.
INSTALL.amd64 in the installation iso file.
Supported hardware.
OpenBSD installation guide.
The purpose in this section is to build the installation iso file using the createiso script at the root of the project source tree. You are expected to be doing these on an OpenBSD 6.9 and have installed git, gettext, and doxygen on it.
However, the source tree has links to OpenBSD install sets and packages, which should be broken, hence need to be fixed when you first obtain the sources. Make sure you see those broken links now. So, before you can run createiso, you need to do a couple of things:. Note that you can strip down xbase and xfont install sets to reduce the size of the iso file. Copy or link them to the appropriate locations under openbsd/pffw. Now you can run the createiso script which should produce an iso file in the same folder as itself.
Clones the git repo of the project to a tmp folder.
Generates gettext translations and doxygen documentation.
Prepares the webif and config packages and the site install set.
And finally creates the iso file.
Install sets: Obtain the sources of OpenBSD. Patch the OpenBSD sources using the patch-* files under openbsd/pffw. Create the UTMFW secret and public key pair to sign and verify the SHA256 checksums of the install sets, and copy them to their appropriate locations. The installation iso of PFFW uses the same install sets as UTMFW, hence the same secret key. If you want to use a different key pair, you should change the references to the UTMFW key pair in the source code as well. Build an OpenBSD release, as described in release(8) or faq5. Copy the required install sets to the appropriate locations to fix the broken links in the sources.
Packages: Download the required packages available on the OpenBSD mirrors. Copy them to the appropriate locations to fix the broken links in the sources.
The following are steps you can follow to build PFFW yourself. Some of these steps can be automated by a script. You can modify these steps to suit your needs.
Install OpenBSD: Download installXY.iso from an OpenBSD mirror Create a new VM with 60GB disk, choose a size based on your needs Add a separate 8GB disk for /dest, which will be needed to make release(8) Start VM and install OpenBSD Create a local user, after reboot add it to /etc/doas.conf During installation mount the dest disk to /dest Add noperm to /dest in /etc/fstab Make /dest owned by build:wobj and set its perms to 700 Create /dest/dest/ and /dest/rel/ folders
Fetch the PFFW sources and update if upgrading: Install git Clone PFFW to your home folder Bump the version number X.Y in the sources, if upgrading cd/amd64/etc/boot.conf meta/createiso meta/install.sub src/create_po.sh Doxyfile README.md src/lib/defs.php cd/amd64/X.Y/ openbsd/X.Y/ .po files under src/View/locale/ Bump the version number XY in the sources, if upgrading README.md openbsd/pffw/expat/amd64/xbaseXY.tgz openbsd/pffw/fonts/amd64/xfontXY.tgz Update based on the release date, project changes, and news, if upgrading config/etc/motd meta/root.mail README.md Update copyright if necessary
Make sure the signify key pair for UTMFW is in the correct locations: Save utmfw-XY.pub and utmfw-XY.sec to docs/signify Copy utmfw-XY.pub to /etc/signify/, the utmfw-XY.pub file is copied into the bsd.rd file while making release(8), to verify install sets during installation
Update the packages: Install the OpenBSD packages Set the download mirror, use the existing cache if any export PKG_PATH=/var/db/pkg_cache/:https://cdn.openbsd.org/pub/OpenBSD/X.Y/packages/amd64/ Save the depends under PKG_CACHE, which will be used later on to update the packages in the iso file export PKG_CACHE=/var/db/pkg_pffw/ isc-bind symon symux pftop php, php-cgi, php-curl, php-pcntl Update the links under cd/amd64/X.Y/packages/ with the OpenBSD packages saved under PKG_CACHE
Update meta/install.sub: Update the versions of the packages listed in THESETS
Make release(8): Extract src.tar.gz and and sys.tar.gz under /usr/src/ Apply the patches under openbsd/pffw Update the sources with the stable branch changes if any Follow the instructions in release(8), this step takes about 6 hours on a relatively fast computer Build the kernel and reboot Build the base system Make the release, use the dest and rel folders created above: export DESTDIR=/dest/dest/ RELEASEDIR=/dest/rel/ Copy the install sets under /dest/rel/ to ~/OpenBSD/X.Y/amd64/
Update the install sets: Update the links for install sets under cd/amd64/X.Y/amd64 using the install sets under ~/OpenBSD/X.Y/amd64/ made above Remove the old links Copy the xbaseXY.tgz install set from installXY.iso to docs/expat/amd64/xbaseXY.tgz Copy the xfontXY.tgz install set from installXY.iso to docs/fonts/amd64/xfontXY.tgz
Update the configuration files under config with the ones in the new versions of packages: Also update Doxyfile if the doxygen version has changed
Update PFRE: Update PFRE to the current version, support changes in pf if any Create and install the man2web package Produce pf.conf.html from pf.conf(5) using man2web Merge PFRE changes from the previous pf.conf.html, most importantly the anchors
Update phpseclib to its new version if any: Merge the PFFW changes from the previous version
Update d3js to its new version if any: Fix any issues caused by any API changes
Strip xbase and xfont: Make sure the contents are the same as in the one in the old iso file, except for the version numbers SECURITY: Be very careful about the permissions of the directories and files in these install sets, they should be the same as the original files
Run the createiso script: Install gettext-tools and doxygen for translations and documentation Run ./createiso under ~/pffw/
Thanks to a modified auto-partitioner of OpenBSD, the disk can be partitioned with a recommended layout for PFFW, so most users don't need to use the label editor at all.
All install sets including siteXY.tgz are selected by default, so you cannot 'not' install PFFW by mistake.
OpenBSD installation questions are modified according to the needs of PFFW. For example, X11 related questions are never asked.
512MB RAM and an 8GB HD should be enough.
INSTALL.amd64 in the installation iso file.
Supported hardware.
OpenBSD installation guide.
The purpose in this section is to build the installation iso file using the createiso script at the root of the project source tree. You are expected to be doing these on an OpenBSD 6.9 and have installed git, gettext, and doxygen on it.
However, the source tree has links to OpenBSD install sets and packages, which should be broken, hence need to be fixed when you first obtain the sources. Make sure you see those broken links now. So, before you can run createiso, you need to do a couple of things:. Note that you can strip down xbase and xfont install sets to reduce the size of the iso file. Copy or link them to the appropriate locations under openbsd/pffw. Now you can run the createiso script which should produce an iso file in the same folder as itself.
Clones the git repo of the project to a tmp folder.
Generates gettext translations and doxygen documentation.
Prepares the webif and config packages and the site install set.
And finally creates the iso file.
Install sets: Obtain the sources of OpenBSD. Patch the OpenBSD sources using the patch-* files under openbsd/pffw. Create the UTMFW secret and public key pair to sign and verify the SHA256 checksums of the install sets, and copy them to their appropriate locations. The installation iso of PFFW uses the same install sets as UTMFW, hence the same secret key. If you want to use a different key pair, you should change the references to the UTMFW key pair in the source code as well. Build an OpenBSD release, as described in release(8) or faq5. Copy the required install sets to the appropriate locations to fix the broken links in the sources.
Packages: Download the required packages available on the OpenBSD mirrors. Copy them to the appropriate locations to fix the broken links in the sources.
The following are steps you can follow to build PFFW yourself. Some of these steps can be automated by a script. You can modify these steps to suit your needs.
Install OpenBSD: Download installXY.iso from an OpenBSD mirror Create a new VM with 60GB disk, choose a size based on your needs Add a separate 8GB disk for /dest, which will be needed to make release(8) Start VM and install OpenBSD Create a local user, after reboot add it to /etc/doas.conf During installation mount the dest disk to /dest Add noperm to /dest in /etc/fstab Make /dest owned by build:wobj and set its perms to 700 Create /dest/dest/ and /dest/rel/ folders
Fetch the PFFW sources and update if upgrading: Install git Clone PFFW to your home folder Bump the version number X.Y in the sources, if upgrading cd/amd64/etc/boot.conf meta/createiso meta/install.sub src/create_po.sh Doxyfile README.md src/lib/defs.php cd/amd64/X.Y/ openbsd/X.Y/ .po files under src/View/locale/ Bump the version number XY in the sources, if upgrading README.md openbsd/pffw/expat/amd64/xbaseXY.tgz openbsd/pffw/fonts/amd64/xfontXY.tgz Update based on the release date, project changes, and news, if upgrading config/etc/motd meta/root.mail README.md Update copyright if necessary
Make sure the signify key pair for UTMFW is in the correct locations: Save utmfw-XY.pub and utmfw-XY.sec to docs/signify Copy utmfw-XY.pub to /etc/signify/, the utmfw-XY.pub file is copied into the bsd.rd file while making release(8), to verify install sets during installation
Update the packages: Install the OpenBSD packages Set the download mirror, use the existing cache if any export PKG_PATH=/var/db/pkg_cache/:https://cdn.openbsd.org/pub/OpenBSD/X.Y/packages/amd64/ Save the depends under PKG_CACHE, which will be used later on to update the packages in the iso file export PKG_CACHE=/var/db/pkg_pffw/ isc-bind symon symux pftop php, php-cgi, php-curl, php-pcntl Update the links under cd/amd64/X.Y/packages/ with the OpenBSD packages saved under PKG_CACHE
Update meta/install.sub: Update the versions of the packages listed in THESETS
Make release(8): Extract src.tar.gz and and sys.tar.gz under /usr/src/ Apply the patches under openbsd/pffw Update the sources with the stable branch changes if any Follow the instructions in release(8), this step takes about 6 hours on a relatively fast computer Build the kernel and reboot Build the base system Make the release, use the dest and rel folders created above: export DESTDIR=/dest/dest/ RELEASEDIR=/dest/rel/ Copy the install sets under /dest/rel/ to ~/OpenBSD/X.Y/amd64/
Update the install sets: Update the links for install sets under cd/amd64/X.Y/amd64 using the install sets under ~/OpenBSD/X.Y/amd64/ made above Remove the old links Copy the xbaseXY.tgz install set from installXY.iso to docs/expat/amd64/xbaseXY.tgz Copy the xfontXY.tgz install set from installXY.iso to docs/fonts/amd64/xfontXY.tgz
Update the configuration files under config with the ones in the new versions of packages: Also update Doxyfile if the doxygen version has changed
Update PFRE: Update PFRE to the current version, support changes in pf if any Create and install the man2web package Produce pf.conf.html from pf.conf(5) using man2web Merge PFRE changes from the previous pf.conf.html, most importantly the anchors
Update phpseclib to its new version if any: Merge the PFFW changes from the previous version
Update d3js to its new version if any: Fix any issues caused by any API changes
Strip xbase and xfont: Make sure the contents are the same as in the one in the old iso file, except for the version numbers SECURITY: Be very careful about the permissions of the directories and files in these install sets, they should be the same as the original files
Run the createiso script: Install gettext-tools and doxygen for translations and documentation Run ./createiso under ~/pffw/
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
