aboutsummaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAge
* version 0.9.66rc1 released0.9.66rc1Libravatar netblue302021-06-02
|
* configure*: use cat instead of many echoesLibravatar Kelvin M. Klann2021-05-28
| | | | For simplicity and increased portability.
* configure.ac: run autoupdate to fix autoconf warningLibravatar Kelvin M. Klann2021-05-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the following warning: $ autoconf configure.ac:306: warning: AC_OUTPUT should be used without arguments. configure.ac:306: You should run autoupdate. Environment: $ grep '^NAME' /etc/os-release NAME="Artix Linux" $ pacman -Q autoconf autoconf 2.71-1 Though keep `AC_PREREQ` at 2.68 (released on 2010-09-23[1]), as version 2.71 (which autoupdate automatically bumps to) is rather recent (released on 2021-01-28[2]) and the changes do not appear to require a version bump, as on `AC_INIT` it only adds some quotes, and the rest of the changes are consistent with the autoconf 2.68 manual. From Section 18.4, Obsolete Macros[3]: > — Macro: AC_OUTPUT ([file]..., [extra-cmds], [init-cmds]) > > The use of AC_OUTPUT with arguments is deprecated. This obsoleted > interface is equivalent to: > > AC_CONFIG_FILES(file...) > AC_CONFIG_COMMANDS([default], > extra-cmds, init-cmds) > AC_OUTPUT > > See AC_CONFIG_FILES, AC_CONFIG_COMMANDS, and AC_OUTPUT. Note: The usage of the above format has been present since the inception of configure.ac, on commit 137985136 ("Baseline firejail 0.9.28"). Misc: This is a continuation of #4293. [1] https://lists.gnu.org/archive/html/info-gnu/2010-09/msg00013.html [2] https://lists.gnu.org/archive/html/autoconf/2021-01/msg00126.html [3] https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Obsolete-Macros.html#index-AC_005fOUTPUT-2058
* CI: build with GCC 11Libravatar Reiner Herrmann2021-05-23
| | | | | | | | | this fixes a new false positive memory leak (#4297), but unfortunately opens a few new false positives (#4274). therefore let it ignore memleak checks for now, until the detection is a bit more stable in GCC. Fixes: #4274, #4297
* configure*: fix build with non-bash /bin/shLibravatar Kelvin M. Klann2021-05-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The configure script happens to work if /bin/sh supports the non-POSIX "+=" operator (e.g.: bash) and fails otherwise (e.g.: dash). This usage first appeared on configure.ac on commit 66a476419 ("gcov support"), which is from 2016. If the --enable-apparmor flag is passed to ./configure (which is the default on Arch Linux), running `make` fails due to the missing -lapparmor LDFLAG. Thus, building firejail-git from the AUR does not work if /bin/sh is e.g.: dash. Errors when running the build commands below from makepkg: $ ./configure --prefix=/usr --enable-apparmor >/dev/null ./configure: 3174: EXTRA_CFLAGS+= -mindirect-branch=thunk: not found ./configure: 3246: EXTRA_CFLAGS+= -fstack-clash-protection: not found ./configure: 3282: EXTRA_CFLAGS+= -fstack-protector-strong: not found ./configure: 3518: EXTRA_CFLAGS+= : not found $ make >/dev/null /usr/bin/ld: apparmor.o: in function `apparmor_test': /tmp/firejail-git/src/firejail-git/src/jailcheck/apparmor.c:28: undefined reference to `aa_gettaskcon' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:10: jailcheck] Error 1 make: *** [Makefile:42: src/jailcheck/jailcheck] Error 2 make: *** Waiting for unfinished jobs.... /usr/bin/ld: apparmor.o: in function `print_apparmor': /tmp/firejail-git/src/firejail-git/src/firemon/apparmor.c:28: undefined reference to `aa_gettaskcon' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:10: firemon] Error 1 make: *** [Makefile:42: src/firemon/firemon] Error 2 /usr/bin/ld: join.o: in function `extract_apparmor': /tmp/firejail-git/src/firejail-git/src/firejail/join.c:65: undefined reference to `aa_is_enabled' /usr/bin/ld: sandbox.o: in function `set_apparmor': /tmp/firejail-git/src/firejail-git/src/firejail/sandbox.c:133: undefined reference to `aa_change_onexec' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:10: firejail] Error 1 make: *** [Makefile:42: src/firejail/firejail] Error 2 Without the apparmor flag, the CFLAGS related to HAVE_SPECTRE do not get applied either, but `make` does not error out, so the problem is harder to detect in this case. Diff comparing the output of `./configure 2>&1` when running without and then with this patch: $ git --no-pager diff --no-index configure_current.log configure_patch.log diff --git a/configure_current.log b/configure_patch.log index f5e814f..099d836 100644 --- a/configure_current.log +++ b/configure_patch.log @@ -10,12 +10,9 @@ checking for gcc option to accept ISO C89... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking whether C compiler accepts -mindirect-branch=thunk... yes -./configure: 3174: EXTRA_CFLAGS+= -mindirect-branch=thunk: not found checking whether C compiler accepts -mretpoline... no checking whether C compiler accepts -fstack-clash-protection... yes -./configure: 3246: EXTRA_CFLAGS+= -fstack-clash-protection: not found checking whether C compiler accepts -fstack-protector-strong... yes -./configure: 3282: EXTRA_CFLAGS+= -fstack-protector-strong: not found checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for gawk... yes @@ -88,7 +85,7 @@ Configuration options: busybox workaround: no Spectre compiler patch: yes EXTRA_LDFLAGS: - EXTRA_CFLAGS: + EXTRA_CFLAGS: -mindirect-branch=thunk -fstack-clash-protection -fstack-protector-strong fatal warnings: Gcov instrumentation: Install contrib scripts: yes
* jailtest -> jailcheck (#4268)Libravatar netblue302021-05-18
|
* retiring --audit (replaced by jailtest)Libravatar netblue302021-03-01
|
* Add ./configure --enable-force-nonewprivsLibravatar rusty-snake2021-03-01
| | | | This will always set 'nonewprivs', 'caps.drop all' and 'nogroups'.
* compile time: enable LTSLibravatar startx20172021-02-28
|
* compile time: disable --outputLibravatar startx20172021-02-28
|
* jaitest - simple sandbox testing utility programLibravatar netblue302021-02-20
|
* Merge pull request #3864 from haraldkubota/masterLibravatar rusty-snake2021-02-13
|\ | | | | Add first version of zsh completion
| * Add first version of zsh completionLibravatar Harald Kubota2021-02-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't have duplicate descriptions and put = signs where they belong to zsh completion function now dynamically adjusts for options (e.g. no --apparmor option without AppArmor configured) No EXTRA_CFLAGS for cpp Found main.c which does the argument processing. Moved some arguments into the correct #ifdef blocks Profile selection now much better Not more cpp. Using preproc.awk instead. Updated bash firejail command completion to add profiles ignore bash and zsh dynamically created completion scripts Moved bash/zsh completions out of ALL_ITEMS to fix make install Cleanup
* | configure*: fix typo of HAVE_USERTMPFSLibravatar Kelvin M. Klann2021-02-09
| | | | | | | | | | | | | | | | | | | | | | Added on commit 64a8d6a7f ("compile time option to disable --private-cache and --tmpfs for regular user"). These are the only occurrences: $ git ls-files -z | xargs -0 grep -Fin USERTMPS configure:3542:HAVE_USERTMPS="" configure.ac:80:HAVE_USERTMPS=""
* | disabled overlayfs, fixes pending; added video channels to README* filesLibravatar netblue302021-02-06
| |
* | back to 0.9.65; rel 0.9.64.2 moved on a different branch, out in the next ↵Libravatar netblue302021-01-27
| | | | | | | | two days
* | release 0.9.64.2 testingLibravatar netblue302021-01-26
|/
* compile time option to disable --private-cache and --tmpfs for regular userLibravatar netblue302020-10-27
|
* refactor test targets and let build fail on test errorsLibravatar Reiner Herrmann2020-10-24
|
* bump version to new development version 0.9.65Libravatar Reiner Herrmann2020-10-24
|
* 0.9.64 testingLibravatar netblue302020-10-21
|
* build: check for presence of gawk when manpages will be builtLibravatar Reiner Herrmann2020-10-10
| | | | Fixes: #3661
* set as 0.9.64rc2 for development until we release the real oneLibravatar netblue302020-10-05
|
* testing 0.9.64rc1Libravatar netblue302020-10-04
|
* replaced --enable-man with --disable-man in ./configureLibravatar netblue302020-10-03
|
* compile support for GCC static analyzer (--enable-analyzer)Libravatar netblue302020-09-28
|
* disable dbus proxy at compile time (default enabled) - part 1Libravatar netblue302020-09-09
|
* preprocessor for man pagesLibravatar startx20172020-09-01
|
* removed --disable-seccomp from ./configureLibravatar startx20172020-09-01
|
* Configure Debian package with AA and SELinux optionsLibravatar Topi Miettinen2020-05-14
| | | | | Configure Debian package with AA and SELinux options if they are enabled.
* profile statsLibravatar netblue302020-03-19
|
* Add support for SELinux labelingLibravatar Topi Miettinen2020-02-22
| | | | | | | | | | | | | | | | | | | | | | | Running `firejail --noprofile --private-bin=bash,ls ls -1Za /usr/bin` shows that the SELinux labels are not correct: ``` user_u:object_r:user_tmpfs_t:s0 . system_u:object_r:usr_t:s0 .. user_u:object_r:user_tmpfs_t:s0 bash user_u:object_r:user_tmpfs_t:s0 ls ``` After fixing this: ``` system_u:object_r:bin_t:s0 . system_u:object_r:usr_t:s0 .. system_u:object_r:shell_exec_t:s0 bash system_u:object_r:bin_t:s0 ls ``` Most copied files and created directories should now have correct labels (bind mounted objects keep their labels). This is useful to avoid having to change the SELinux rules when using Firejail.
* mainline moving to 0.9.63 for new development; release 0.9.62 is handled on ↵Libravatar netblue302019-12-06
| | | | release-0.9.62 branch
* testing for -fstack-clash-protection and -fstack-protector-strong compile flagsLibravatar netblue302019-06-26
|
* disable firetunnel at config time (#2793)Libravatar netblue302019-06-24
|
* use pkg-config macro to locate apparmor and flagsLibravatar Reiner Herrmann2019-06-21
|
* use AX_CHECK_COMPILE_FLAG to check for spectre flagsLibravatar Reiner Herrmann2019-06-21
| | | | Fixes #2661
* 0.9.60 is out, movin to 0.9.61Libravatar netblue302019-05-27
|
* 0.9.60 testingLibravatar netblue302019-05-26
|
* moving to rc2Libravatar netblue302019-04-21
|
* 0.9.60-rc1 testing0.9.60-rc1Libravatar netblue302019-04-21
|
* 0.9.58.2 is out, moving back to 0.9.59Libravatar netblue302019-02-08
|
* 0.9.58.2 testingLibravatar netblue302019-02-08
|
* moving to 0.9.59Libravatar netblue302019-01-27
|
* release 0.9.58 testingLibravatar netblue302019-01-26
|
* release 0.9.58-rc1Libravatar netblue302019-01-21
|
* reverting to 0.9.57Libravatar netblue302018-10-21
|
* 0.9.56.1 - bugfix releaseLibravatar netblue302018-10-11
|
* configure.ac: set sysconfdir only if none was specified manuallyLibravatar Reiner Herrmann2018-10-03
| | | | Fixes #2125
* --version 0.9.57Libravatar netblue302018-09-19
|