| 1 |
Source: boxfort |
| 2 |
Section: libs |
| 3 |
Priority: optional |
| 4 |
Maintainer: SZALAY Attila <[email protected]> |
| 5 |
Standards-Version: 4.5.0 |
| 6 |
Vcs-Browser: https://salsa.debian.org/sasa/boxfort |
| 7 |
Vcs-Git: https://salsa.debian.org/sasa/boxfort.git |
| 8 |
HomePage: https://github.com/Snaipe/Criterion |
| 9 |
Rules-Requires-Root: no |
| 10 |
Build-Depends: debhelper-compat (= 12), |
| 11 |
meson, |
| 12 |
python3-cram |
| 13 |
|
| 14 |
Package: libboxfort-dev |
| 15 |
Section: libdevel |
| 16 |
Architecture: amd64 arm64 i386 |
| 17 |
Multi-Arch: same |
| 18 |
Depends: ${misc:Depends}, pkg-config |
| 19 |
Breaks: libboxfort (<< 0.0.0-git20200808-ac0507b-1) |
| 20 |
Replaces: libboxfort (<< 0.0.0-git20200808-ac0507b-1) |
| 21 |
Description: development file for BoxFort |
| 22 |
BoxFort provides a simple API to run user code in isolated processes. |
| 23 |
. |
| 24 |
Although BoxFort provides some kind of security of the parent process from |
| 25 |
spawned sandboxes, a sandbox has by default the same system permissions and |
| 26 |
access than its parent, and is hence, without care, ill-fitted for security |
| 27 |
purposes. |
| 28 |
. |
| 29 |
The main goal of this project is not security, but portable code isolation |
| 30 |
-- if you want complete system isolation, consider using properly configured |
| 31 |
containers. |
| 32 |
. |
| 33 |
This package contains the header files required to compile a package against |
| 34 |
BoxFort. |