/mandos/trunk : changes

» Changes from revision 1316

To get this branch, use:

bzr branch
http://bzr.recompile.se/loggerhead/mandos/trunk

From Revision 1307 to 1288

expand all

Rev	Summary	Authors	Date
1307	Make binary directory configurable Make binary directory configurable Reportedly, Arch Linux uses /bin for all binaries, not /sbin. Therefore, make binary directory configurable. From: Erich Eckner <mandos@eckner.net> Signed-off-by: Teddy Hogeborn <teddy@recompile.se>	Teddy Hogeborn	24 days ago
1306	Detect GPGME version correctly Detect GPGME version correctly It seems that newer versions of dpkg-query can print an empty version. Change the code to also parse this output. Reported-By: Pablo Abelenda <pabelenda@igalia.com>	Teddy Hogeborn	24 days ago
1305	Only use D-Bus when necessary Only use D-Bus when necessary If both "use_dbus" and "zeroconf" are false, by either setting them to False in mandos.conf or by using the --no-dbus and --no-zeroconf options (and a port number or socket is specified), then we do not need to connect to D-Bus at all. From: Mike Klein <mike@kleinnet.com> Signed-off-by: Teddy Hogeborn <teddy@recompile.se>	Teddy Hogeborn	2 months ago
1304	Override lintian experimental tag "executable-in-usr-lib" Override lintian experimental tag "executable-in-usr-lib" Lintian reports executable files in /usr/lib, since binaries which are executed internally are supposed to be stored in /usr/libexec. But the executables we store in /usr/lib are all files to be copied into the initial RAM disk image, and are never executed from their storage location in /usr/lib. Except one; the Dracut module-setup.sh file. But that file seems to be required to be executable; the module-setup.sh file of every other Dracut module is also an executable file. * debian/mandos-client.lintian-overrides: Override experimental tag "executable-in-usr-lib" about files which are not actually executed from this location, and only exist to be copied to the initial RAM disk image. Also the Dracut module-setup.sh file, which merely follows the pattern of all other Dracut module-setup.sh files from other Dracut modules.	Teddy Hogeborn	2 months ago
1303	Fix lintian warning "build-depends-on-obsolete-package" Fix lintian warning "build-depends-on-obsolete-package" Apparently, pkg-config is deprecated in favor of pkgconf: <https://bugs.debian.org/1020799>, <http://pkgconf-migration.debian.net/> Therefore, prefer pkgconf in the build dependencies. * debian/control (Source: mandos/Build-Depends): Change "pkg-config" to "pkgconf \| pkg-config".	Teddy Hogeborn	2 months ago
1302	Merge from release branch Merge from release branch	Teddy Hogeborn	2 months ago
1301	Ignore some more files Ignore some more files * .bzrignore: Ignore "cl", which is used to temporarily save the commit message. Ignore the .mypy_cache directories. Ignore *.c.local files which are used by the tools to sort #include directives and associated comments.	Teddy Hogeborn	2 months ago
1300	Hide warnings if --no-warn-execstack is not supported Hide warnings if --no-warn-execstack is not supported * Makefile: When testing if "-Xlinker --no-warn-execstack" can be used by the C compiler, hide any error output.	Teddy Hogeborn	2 months ago
1299	Only use linker option --no-warn-execstack if supported Only use linker option --no-warn-execstack if supported The --no-warn-execstack is new in ld(1) version 2.39; only use the option if the linker supports it. * Makefile: Only add "-Xlinker --no-warn-execstack" to LDFLAGS for various programs if we can successfully run a compiler with that linker flag.	Teddy Hogeborn	2 months ago
1298	Eliminate compiler warnings Eliminate compiler warnings Many programs use nested functions, which now result in a linker warning about executable stack. Hide this warning. Also, rewrite a loop in the plymouth plugin to avoid warning about signed overflow. This change also makes the plugin pick the alphabetically first process entry instead of the last, in case many plymouth processes are found (which should be unlikely). * Makefile (plugin-runner, dracut-module/password-agent, plugins.d/password-prompt, plugins.d/mandos-client, plugins.d/plymouth): New target; set LDFLAGS to add "-Xlinker --no-warn-execstack". * plugins.d/plymouth.c (get_pid): When no pid files are found, and we are looking through the process list, go though it from the start instead of from the end, i.e. in normal alphabetical order and not in reverse order.	Teddy Hogeborn	2 months ago
1297	Acknowledge NMUs in debian/changelog Acknowledge NMUs in debian/changelog * debian/changelog (1.8.16-1.1, 1.8.16-1.2): New entries.	Teddy Hogeborn	2 months ago
1296	Update Debian Policy version to 4.7.0; no other changes nece... Update Debian Policy version to 4.7.0; no other changes necessary. * debian/control (Standards-Version): Change to "4.7.0".	Teddy Hogeborn	2 months ago
1295	Change to new lintian override syntax Change to new lintian override syntax Lintian has changed its output for warnings, and as a result, its syntax for overriding those warnings has also changed. (See Debian bug #1007002 for further information.) Therefore, change the syntax in the lintian override files. * debian/mandos-client.lintian-overrides: Change to new lintian "pointed hints" syntax. * debian/mandos.lintian-overrides: - '' -	Teddy Hogeborn	2 months ago
1294	Make all required directories when installing Make all required directories when installing When installing into a normal system, one can assume that target directories, such as /usr/bin, already exists. But when installing into a subdirectory for the purpose of creating a package, one cannot assume that all directories already exist. Therefore, when installing, we must not check if any directories exist, and must instead always create any directories we want to install into. * Makefile (confdir/mandos.conf, confdir/clients.conf, install-html): Use the "-D" option to "install" instead of creating the directory separately. (install-server): Move creation of $(CONFDIR) down to before it is needed. Don't check if the $(TMPFILES) or $(SYSUSERS) directories exist; instead create them by using the "-D" option to "install". Create the $(PREFIX)/sbin directory. Always use "--target-directory" if possible; i.e. if the file name is the same. Create the $(DBUSPOLICYDIR) and $(DESTDIR)/etc/init.d directories by using the "-D" option to "install". Don't check if the $(SYSTEMD) directory exists; instead create it by using the "-D" option to "install". Create the $(DESTDIR)/etc/default and $(MANDIR)/man8 directories by using the "-D" option to "install". Create the $(MANDIR)/man5 directories explicitly. (install-client-nokey): Remove unnecessary creation of the $(CONFDIR) directory. Don't check if the $(SYSUSERS) directory exists; instead create it by using the "-D" option to "install". Move the "--directory" argument to be the first argument, for clarity. Create the $(PREFIX)/sbin directory. Use the "-D" argument to "install" when installing $(INITRAMFSTOOLS)/hooks/mandos, $(INITRAMFSTOOLS)/conf.d/mandos-conf, $(INITRAMFSTOOLS)/conf-hooks.d/zz-mandos, $(INITRAMFSTOOLS)/scripts/init-premount/mandos, $(INITRAMFSTOOLS)/scripts/local-premount/mandos, $(DRACUTMODULE)/ask-password-mandos.path, and $(DRACUTMODULE)/dracut-module/ask-password-mandos.service. Create the $(MANDIR)/man8 directory. Reported-By: Erich Eckner <erich@eckner.net> Thanks: Erich Eckner <erich@eckner.net> for analysis	Teddy Hogeborn	2 months ago
1293	Fix minor deprecated syntax issue in debian/control Fix minor deprecated syntax issue in debian/control The << syntax should be preferred to the deprecated < notation. * debian/control (Source: mandos/Build-Depends): Change from having "systemd (< 256~rc2-1)" to "systemd (<< 256~rc2-1)".	Teddy Hogeborn	2 months ago
1292	Do not hardcode directory names; get them from pkg-config Do not hardcode directory names; get them from pkg-config Similarly to the directory for systemd unit files (output of "pkg-config systemd --variable=systemdsystemunitdir"), the values of the "tmpfilesdir" and "sysusersdir" variables should not be hardcoded in debian/mandos.dirs and debian/mandos-client.dirs. Fix this the same way as with systemdsystemunitdir; i.e. remove the directories from the .dirs files, and instead create the directories in override rules in debian/rules. * debian/mandos-client.dirs (usr/lib/sysusers.d): Removed. * debian/mandos.dirs (usr/lib/tmpfiles.d, usr/lib/sysusers.d): Removed. * debian/rules (override_dh_installdirs-indep): Also create directories for the "tmpfilesdir" and "sysusersdir" variables from pkg-config. (override_dh_installdirs-arch): New; create directory for the "sysusersdir" variable from pkg-config.	Teddy Hogeborn	2 months ago
1291	Require correct version of systemd-dev or systemd Require correct version of systemd-dev or systemd The systemd.pc file (for use by pkg-config) was moved from the systemd package to the systemd-dev package in version 256~rc2-1. Therefore, require either systemd-dev or a version of systemd before that version, in order to be guaranteed the presence of the systemd.pc file. * debian/control (Source: mandos/Build-Depends): Add version qualifier "(< 256~rc2-1)" to "systemd".	Teddy Hogeborn	2 months ago
1290	Minor fix for manual Makefile uninstallations Minor fix for manual Makefile uninstallations If the Mandos systemd unit file was not installed, it was still removed by the "purge-server" target. If systemd is not installed, this could mean removal of "mandos.service" from the root directory. (Note: this was not used by the Debian package as a method of uninstallation; this was only ever done by the Makefile if "make purge-server" was called by hand. And a "mandos.service" file was presumably also unlikely to exist in the root directory.) * Makefile (purge-server): Only remove systemd service file "mandos.service" if the same conditions exist which permitted its initial installation in the "install-server" target.	Teddy Hogeborn	2 months ago
1289	Fix #1069689 by using pkg-config in debian/rules Fix #1069689 by using pkg-config in debian/rules The directory for systemd unit files (output of "pkg-config systemd --variable=systemdsystemunitdir") has changed. But there was a hardcoded instance of this directory in debian/mandos.dirs. Fix this by removing the directory from debian/mandos.dirs, and instead creating the correct directory explicitly in debian/rules. * debian/mandos.dirs (lib/systemd/system): Removed. * debian/rules (PKG_CONFIG): New; copied from Makefile. (override_dh_installdirs-indep): New; run dh_installdirs twice: first normally, and again for the systemd unit file directory. Closes: #1069689 Reported-By: Helmut Grohne <helmut@subdivi.de> Thanks: Helmut Grohne <helmut@subdivi.de> for report and analysis	Teddy Hogeborn	2 months ago
1288	Fix #1079588 by not outputting to stdout in maintainer scrip... Fix #1079588 by not outputting to stdout in maintainer scripts From The Debconf Programmer's Tutorial: "Anything your maintainer scripts output to standard output is passed into the frontend as a command". We must make sure to redirect stdout to stderr for every command in the postinst and postrm scripts which might output to stdout. * debian/mandos-client.postinst (update_initramfs): Add "1>&2" to invocations of update-initramfs and /etc/kernel/postinst.d/dracut. (add_mandos_user): Add "1>&2" to invocations of usermod, groupmod, and adduser. (create_keys): Add "1>&2" to invocations of mandos-keygen, gpg-connect-agent, certtool, and openssl. (create_dh_params): Add "1>&2" to invocations of certtool and openssl. Add "--force" option to "rm". * debian/mandos-client.postrm (update_initramfs): Add "1>&2" to invocations of update-initramfs and /etc/kernel/postinst.d/dracut. Closes: #1079588 Reported-By: Ben Hutchings <ben@decadent.org.uk>	Teddy Hogeborn	2 months ago

Older »