about summary refs log tree commit diff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* machines: Remove tyree and brawndoaszlig2023-09-142-18/+0
| | | | | | | | | | | | | The former no longer exists and the latter has a new hardware and it's self-managed by the owner now (which is always the best IMHO). With both machines gone, we no longer need the "managed" profile and the BFQ module that was used for the old hardware of Brawndo was no longer used anywhere else. Same with the T100HA module, since Tyree was an ASUS T100HA and apart from the module being probably very much outdated we don't have another such hardware in Vuizvui. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Return test attr instead of option defsaszlig2022-10-031-1/+1
| | | | | | | | | | | | | | | | | | | Introduced by a recent change[1], all NixOS VM tests are evaluated using the NixOS module system and with [2], makeTest doesn't return a derivation anymore but the .config attribute of the module system evaluation. This however doesn't work very well when thrown into Hydra, which traverses through all attributes recursively looking for derivations. We had our fair share of OOMs on our Hydra evaluator and right now, some jobsets are still getting evaluation timouts, one of them is due to the fact that we use makeTest without returning the actual test derivation. [1]: https://github.com/NixOS/nixpkgs/pull/191540 [2]: https://github.com/NixOS/nixpkgs/commit/aed1deab0574f663be2d401861b Signed-off-by: aszlig <aszlig@nix.build>
* tests/gnupg: Work around possible buffering issueaszlig2022-05-081-1/+3
| | | | | | | | | | | | | | | | | | | | | | | Recently the test has started to stall, so I investigated and found the commit that introduced this in nixpkgs[1]. The commit in question changes the command to be passed to Machine.execute from a list in a subshell environment (like "(some commands)") to using a subshell directly via "sh -c". This is allegedly to avoid shell injection, but what matters in our case I guess is that it forks into another shell. Unfortunately, I did not find out *exactly* why this happens but it seems to affect buffering in such a way that the command never terminates for some reason. Since I don't have a lot of time to investigate further, I just worked around the issue by suppressing stdout output from the expect scripts we run. This is not nice but since the test stall is irrelevant to our gnupg module, it doesn't make sense to block the test for reasons out of the scope of this test. [1]: https://github.com/NixOS/nixpkgs/commit/dbc95f15b8dad5224cbb6a52df9 Signed-off-by: aszlig <aszlig@nix.build>
* flameshot: Rebase patch against version 11.0.0aszlig2022-02-091-2/+5
| | | | | | | | | | | | | | | | | | This is a major upstream release which deprecates a few of our options but also made our patch a little longer because the tools we remove are now defined in multiple places. The patch itself is pretty much doing the same things as before we do have one thing that is different, which is that we now create the savePath directory if it doesn't exist. I do know that this doesn't necessary need to be a directory but in the way I'm using flameshot it is, so I don't care ;-) While at it, I also disabled the checkForUpdates option, because this has annoyed me for some time and I really don't care if the version is the latest for a screenshot utility. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Fix running background command for PSI testaszlig2021-11-071-1/+1
| | | | | | | | | | | | | | | | | Recently, the implementation behind Machine.execute() and thus also Machine.succeed() has been changed[1] to pipe all the command's output into base64 on the guest machine. Unfortunately this means that base64 is blocking until stdout is closed, which in turn means that we now need to make sure that whenever we run a program in background via "&" we also need to make sure to close stdout. In the PSI test, we're doing this by simply redirecting the output to stderr. [1]: https://github.com/NixOS/nixpkgs/pull/142747 Signed-off-by: aszlig <aszlig@nix.build>
* tests/sandbox: Substitute alias for libressl.ncaszlig2021-06-161-1/+1
| | | | | | | | | | | Another one of a series of aliases to rename, similar to the last few commits. Unfortunately, I didn't evaluate the sandbox test to make sure all the references were changed, so I missed the netcat one. This time however, I evaluated the sandbox test with latest nixpkgs and it went without errors. Signed-off-by: aszlig <aszlig@nix.build>
* treewide: Replace xvfb_run with xvfb-runaszlig2021-06-161-2/+2
| | | | | | | | | | | | Another alias that has been introduced not too long ago[1] and now more closely resembles the actual command name. Since NixOS VM tests no longer allow aliases, our sandbox tests did not evaluate anymore. While at it, I also renamed all the other uses of the alias. [1]: https://github.com/NixOS/nixpkgs/commit/726306003af21ade95b1908d1920ce9a0f9815bb Signed-off-by: aszlig <aszlig@nix.build>
* tests/psi: Work around OCR recognition failureaszlig2021-03-091-1/+1
| | | | | | | | | | | | For some reason I currently don't have time to investigate, the test has stopped to recognise the "Register new account" text, because the text extracted via OCR was "Reg ster new account" (note: without the "i"). Since we're not testing OCR in general and all we really care here in the test is whether the application starts up, I just changed the "i" to a "." (any character in regex) to make sure the detection passes. Signed-off-by: aszlig <aszlig@nix.build>
* tests/profpatsch/programs/nman: add nixos test for nmansternenseemann2021-02-252-0/+54
| | | | | | | | | | | We can't really do normal unit tests, since they'd be integration tests requiring nix. Recursive nix is also a bad idea in normal derivations, so we add a NixOS test for nman. Here we are also somewhat limited since we already need to have all store paths used by nman in /nix/store otherwise we'd need to access the network which would fail. However we can verify that nman only builds specific store paths before finding the desired man page this way.
* profiles/workstation: Add Flameshotaszlig2021-02-132-0/+27
| | | | | | | | | | | So far I've almost exclusively used scrot for screenshots, but most of the time I used an image manipulation program to pixelate stuff, add descriptions or draw arrows. Flameshot combines this in a single application, so I expect that from now on I can spam-post screenshots in even a higher rate than before ;-) Signed-off-by: aszlig <aszlig@nix.build>
* games/starbound: Update to version 1.4.4aszlig2020-11-101-13/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I already updated the game a while ago, but didn't commit it yet and since the update has been out since a year, I think it's time to actually update it here as well (shame on me). This essentially includes the "new" bounty hunter update from June 2019, which has a lot of changes. So instead of including the changelog here, I'm hereby referring to the upstream release announcement: https://playstarbound.com/starbound-1-4-bounty-hunter-update/ I also changed the -Werror flag in the preloader to -Wall, since the errors/warnings we're getting are false-positives: error: '__builtin_strncpy' specified bound depends on the length of the source argument [-Werror=stringop-overflow=] While a warning like this usually is a concern, it's not in our case, since the size of the destination *also* depends on the length of the source argument. Additionally, I changed the test to use the new networking.interfaces.*.ipv4.addresses option instead of the legacy one which has been deprecated for ages. Signed-off-by: aszlig <aszlig@nix.build>
* sandbox: Only mount new procfs instance for PID nsaszlig2020-09-111-0/+7
| | | | | | | | | | If we don't have a PID namespace, we're not allowed to mount a new procfs instance and subsequently get an error (EPERM). To cope with this, we're now bind-mounting /proc just like the other pseudo file systems IFF we're not using the CLONE_NEWPID flag. Signed-off-by: aszlig <aszlig@nix.build>
* sandbox: Allow to enable/disable namespacesaszlig2020-09-111-0/+25
| | | | | | | | | | | | | | | | | | | | While the sandbox was initially written for games, I now use the implementation for other things, such as sandboxing database management systems inside "nix develop". However, both MariaDB and PostgreSQL do not like it very much if for example IPC is too restricted and if the PID file contains the PID of the process inside the namespace. Additionally I always wanted to have a way to enable network namespaces for games as well, so this is a good occasion to make them configurable. Of course, since we need the mount and user namespaces to implement our sandbox in the first place, we can't allow users to disable these namespaces, but for everything else, we now have a new "namespaces" attribute. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Switch all tests to Python test driveraszlig2020-08-297-178/+165
| | | | | | | | | | | | | | | | | | | | | Since the removal[1] of the Perl test driver, our tests will no longer run or even evaluate. Fortunately, the test API is more or less the same, so the transition to Python was not very involved. However, I did add a "# fmt: off" on top of every testScript, since formatting with black not only has issues with parameterised antiquotations but is also plain ugly to mix 2 spaces of indentation with 4 spaces of indentation. Additionally, I'd like to have a maximum line length of 79 characters in my Nix expressions while black on the other side even *insists* of using longer lines. [1]: https://github.com/NixOS/nixpkgs/commit/0620184f3f94f1bf8de014ab168 Signed-off-by: aszlig <aszlig@nix.build>
* Fix deprecated displayManager.auto.enable optionaszlig2020-02-102-3/+2
| | | | | | | | | | | | | | | | Since a while[1], the services.xserver.displayManager.auto option is deprecated. Since first of all SLiM got removed and now every display manager supports auto-login, I switched the labtops module to use the LightDM implementation. Since the common x11 test module still exposes a similar interface, we only need to use the same options from the test-support option, which should hopefully be a "sane default" suitable for tests. [1]: https://github.com/NixOS/nixpkgs/commit/c95612a5a2d4bd93011c042066c Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* treewide: use `runCommandLocal` where applicableProfpatsch2019-12-081-2/+2
| | | | | | | `runCommandLocal` was added to nixpkgs in https://github.com/NixOS/nixpkgs/pull/74642 to speed up trivial `runCommand` derivations by always building them locally. We have a few places where that’s good to use.
* pkgs/psi: Fix Qt5 application wrappingaszlig2019-09-232-0/+27
| | | | | | | | | | | | | Qt applications are no longer implicitly wrapped since a while[1] and so we new have to use wrapQtAppsHook instead, which also makes the wrapping for Psi obsolete. To make sure we don't run into startup errors again, I added a small VM test, which checks whether the application starts up properly. [1]: https://github.com/NixOS/nixpkgs/commit/f79fd2e826dd95b3b64839d3e0bec8ae1dfab17e Signed-off-by: aszlig <aszlig@nix.build>
* tests/luks2-bcache: Wait for cache deviceaszlig2019-06-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | When chomping the cache set UUID introduced in 6ae9056a5a82dd16b745188a7ee6122ed27239f0, this actually has brought a bug to surface, because when the UUID wasn't chomped the cache device hasn't been attached at all, because the resulting command looked like this: echo f994bcca-8e52-4b54-9c96-5f5af0711b55 > /sys/block/$bcache1/bcache/attach Yes, that's a newline after the echo, so it's just echoing the UUID and then writes *nothing* into /sys/block/$bcache1/bcache/attach. Chomping the UUID now results in an error, because the attach is made directly after creating the device. So all we need to do here is wait until the cache device was registered and then do the attach. Signed-off-by: aszlig <aszlig@nix.build>
* tests/luks2-bcache: Add missing chomp on $csetuuidaszlig2019-06-111-0/+1
| | | | | | | | This is just a minor nitpick and doesn't actually change a lot in functionality, but I chomped all the other occasions, so let's be consistent here as well. Signed-off-by: aszlig <aszlig@nix.build>
* sandbox: Add an option to set up /bin/shaszlig2019-03-231-0/+12
| | | | | | | | | | | | | | | | So far I mostly used this implementation for the games we have packaged, where we pretty much patch out all commands that execute external programs. However in order to be useful in a more generic way, it makes sense to provide a /bin/sh implementation, especially when you have to deal with scripting languages. I'm using dash here, because it's a more minimal implementation rather than the default shell (bash) we use in nixpkgs and it practically only needs to be able to run constructs like "/bin/sh -c foo". Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Enable bcache kernel moduleaszlig2018-12-242-0/+128
| | | | | | | | | | | | | | | Since I got a new SSD for the machine (thanks @cvdnext), I also had the opportunity to re-create my LUKS containers to LUKS2 with Argon2 key derivation alongside creating bcache backing devices. The change in order to support bcache is just a matter of adding "bcache" to availableKernelModules and we're done. However, as the storage configuration is not a very common one, I decided to add a test specific to that to make sure future NixOS updates won't prevent the machine from booting. Signed-off-by: aszlig <aszlig@nix.build>
* tests/gnupg: Fix OCR match on passphrase dialogaszlig2018-12-071-1/+1
| | | | | | | | | | | | | | | | | | | | Sinc the Tesseract update to version 4.0.0[1], the OCR result is much better than what we had before. The string we want to match is the following: Please enter the passphrase to unlock the OpenPGP secret key In the previous Tesseract alpha version (4.00.00alpha-git-20170410), the word "passphrase" was detected with an upper-case "P", which now is no longer the case. Nevertheless, I've changed it to matching both "Passphrase" and "passphrase", just to be sure. [1]: https://github.com/NixOS/nixpkgs/commit/d4b9752212f77b122b9166dc52f Signed-off-by: aszlig <aszlig@nix.build>
* test/make-test: Add pkgs argument to testing.nixaszlig2018-11-131-3/+3
| | | | | | | Since NixOS/nixpkgs@6c68fbd4e1f8beac39cb1f499ff90c78256262d6 a pkgs argument is required for nixos/lib/testing.nix. Signed-off-by: aszlig <aszlig@nix.build>
* tests/bfq: Don't test on bleeding edge kernelaszlig2018-10-031-1/+1
| | | | | | | | | | | | If someone is going to use our patch for the latest release canidate kernel and it doesn't work I'd say it's somewhat expected. Right now the test fails with the current 4.19-rc6 and I don't have time to investigate this. It might be the case that this also might be an upstream issue, but let's actually lazy evaluate this and re-check once 4.19 is released. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Add UTS/PID/IPC namespacingaszlig2018-09-201-0/+8
| | | | | | | | | | | | | | | | | | | In order to isolate processes even further it's a good idea to not let them access information about other PIDs, eg. by enumerating /proc. However, this still bind-mounts /sys from the root namespace, so we might want to restrict /sys further. For our games however we will need /sys because it is used to enumerate gamepads and other input devices. Currently the processes will now be PID 1. I've tested this against a few games and none of them had problems with that so far, so let's keep it that way. Another thing we might want to add and which currently isn't there is a subreaper, which is useful if we have a process that leaves zombie processes around. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Handle store paths that are symlinksaszlig2018-06-091-0/+16
| | | | | | | | | | | | | | | For example the store path of libGL-1.0.0 is a symlink pointing to libglvnd-1.0.0 right now on my machine. If we have such a symlink the sandbox would just silently skip it and only mount the *resolved* path instead of creating the symlink leading to the target. Now whenever bind_mount() with the resolve argument being true is used, we create all the symlinks leading to the target path determined by realpath(). Signed-off-by: aszlig <aszlig@nix.build>
* tests/starbound: Fix evaluationaszlig2018-05-201-1/+1
| | | | | | | | | | This was an error I made in 7b7f782c93fafe2c42f882b933cf49ba99e3e3bc. Basically the change was to replace "import ../../nixpkgs-path.nix" by thu "nixpkgsPath" argument, but I forgot to remove the ".nix" and it became "nixpkgsPath.nix". Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Fix and pass through .desktop filesaszlig2018-04-291-23/+70
| | | | | | | | | | | | | | Since the introduction and move of a few packages to use the sandbox, we no longer have XDG desktop entries, because the sandbox only creates wrappers for all programs in $drv/bin. This now also copies the XDG desktop files and replaces absolute paths to binaries to refer to the sandboxed binaries. I also modified the test to go through the XDG desktop file by default so we can ensure that this works properly. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Properly propagate nixpkgs pathaszlig2018-04-033-4/+5
| | | | | | | Yet another occasion where we import nixpkgs-path.nix unconditionally, so let's actually pass a nixpkgsPath to every test function. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Pass in nixpkgs source from release.nixaszlig2018-04-032-6/+13
| | | | | | | | | Another point where we rely on nixpkgs-path.nix from within release.nix, where we already have the correct path to nixpkgs passed as an argument. So let's simply pass that argument along to the actual test. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Add handling for XDG_CACHE_HOMEaszlig2017-11-301-1/+17
| | | | | | | | | | | | We only handle XDG_DATA_HOME and XDG_CONFIG_HOME, but we've missed XDG_CACHE_HOME. While the latter is used very rarely as it doesn't matter a lot if it ends up within a tmpfs anyway. However if the cache directory gets pretty large we might run out of space. Not only do we now have proper fallbacks but this also adds tests for all of the XDG environment variables we're using. Signed-off-by: aszlig <aszlig@nix.build>
* tests/sandbox: Use top-level buildSandboxaszlig2017-11-301-2/+1
| | | | | | | | In 38d3fe573f4d0ad2115eaca71a0b8f67fd01a580 we have moved the sandbox builder to the top-level vuizvui namespace so we no longer need to do weird workarounds by providing an empty game configuration. Signed-off-by: aszlig <aszlig@nix.build>
* tests/games/sandbox: Rename to tests/sandboxaszlig2017-11-212-1/+1
| | | | | | | | | | | We have excluded all tests within the games directory from being built by Hydra, rightfully so because they're proprietary. However our sandbox is *not* proprietary so we want to have it tested. Besides, we might want to use that sandbox for other things rather than just games in the future, which saves us that rename later ;-) Signed-off-by: aszlig <aszlig@nix.build>
* tests: Add simple test for buildSandboxaszlig2017-11-212-0/+43
| | | | | | | | This is only a very rudimentary test of the sandbox implementation, but it already serves as a series of regression test for a few problems I ran into so far. Signed-off-by: aszlig <aszlig@nix.build>
* tests/bfq: Use SCSI disk interfaceaszlig2017-09-061-1/+2
| | | | | | | | | Using the virtio disk interface isn't very suitable for real-world simulation, so let's use the SCSI interface, because SATA is exposed to userland as a SCSI device. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @devhell
* Rename all occurences of gpg2 to gpgaszlig2017-08-191-6/+6
| | | | | | | | | | | | This is in reaction to upstream commit NixOS/nixpkgs@e34ce9d1c551fb43742aada6bb43ccb1a52e64a1. One of the changes in GnuPG 2.1.23 is that the main binary is now called gpg instead of gpg2. See the full release announcement here: https://lists.gnupg.org/pipermail/gnupg-announce/2017q3/000412.html Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests/bfq: Use bleeding edge kernelaszlig2017-07-201-1/+1
| | | | | | | | IMHO it makes more sense to use the latest rc kernel instead of the latest stable kernel to run this test, because what we're actually testing here is whether our bfq-by-default.patch is working. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Remove service and tests for multipath-vpnaszlig2017-07-062-193/+0
| | | | | | | | | | The service and test has been broken for a long time now and nobody really has any interest in using it or even fixing it, so I'm removing it to decrease the amount of crap we have in there. If somebody still wants to use this someday we can still bring it back. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Move BFQ stuff into its dedicated moduleaszlig2017-07-062-0/+16
| | | | | | | | | Not everybody likes to have the latest release canidate kernel, so we now have an option called vuizvui.system.kernel.bfq.enable, which *only* enables the BFQ scheduler per default. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @devhell
* starbound: Update to version 1.3.0aszlig2017-06-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Major upstream changes are: * Navigation Overhaul: The cockpit navigation interface has been completely overhauled. Planets, moons and ships are all visible and orbit each other in real time. Systems will now contain NPC stations, friendly and hostile NPC ships, and strange space anomalies to visit! * Customizable Mechs: Explore these new space locations in customizable spacefaring mechs! Traverse hostile space in zero gravity, fight powerful new space monsters, and collect unique rewards as you upgrade your mech to progress through more difficult hazards. Mechs can also be deployed to planets, to crush your enemies with overwhelming firepower! * Modular Space Stations: Make a permanent home among the stars with player-owned stations! Use a station transponder to place your station into orbit, then expand it with modular rooms to suit your needs. The full changes can be found at the announcement blog post at: http://playstarbound.com/spacefarer-update/ One of the changes not listed there is that the archive now consists of a server_linux and client_linux directory, where the latter is structured the same as in previous versions. However, both contain the server binary and both of these binaries match in content. So I'm assuming that the server_linux directory is only a trimmed-down version in terms of assets but otherwise pretty much the same. I've also fixed the VM test, which didn't recognize the font of "Species" anymore, so we're now matching on "randomise". In addition to that I've added a sleep of 30 seconds before the final screenshot, so we get a picture of the fully rendered intro scenario. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests: Fix and improve Starbound testaszlig2016-08-151-27/+10
| | | | | | | | | | | | | | | | Since version 1.0, the coordinates for the menu labels no longer apply and need to be fixed. Also we no longer land on our ship but in the protectorate building, so there won't be a quest dialog to close. This also simplifies the test because we can now detect whether we're in-game using OCR matching parts of the quest marker for "Attend your graduation ceremony". I've also increased the available memory for the server, because it seems that for this simple test the base memory required for running a Starbound server seems to have increased. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/tests: Use Starbound from HumbleBundleaszlig2016-08-151-1/+3
| | | | | | | The Steam version is old anyway and since we've reached 1.0 there is no point in extracting it from Steam anymore. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules/gnupg: Don't close/remove sockets on stopaszlig2016-06-261-2/+8
| | | | | | | | | | | | | | | | | | | | | | When using systemctl restart or systemctl stop on any of the GnuPG services, the sockets were closed and removed. However we are using socket activation, so a simple restart of for example the agent would cause the socket to be closed and removed and afterwards the gpg-agent service is unable to pick up the socket again, thus failing to start. This in turn has led to GnuPG starting the agent by its own, entirely bypassing socket activation and our shiny service module. In order to cope with this, we need to provide LD_PRELOAD wrappers also for remove() and close(), so that we can prevent GnuPG from closing the systemd file descriptors. I've also added a small subtest to ensure this won't happen again in the future. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests/gnupg: Remove leftover for debuggingaszlig2016-06-261-1/+1
| | | | | | | | | The shell script embedded into the expect script had "set -x" enabled. While this doesn't really hurt it doesn't really aid in debugging either (expect -d works much better), so let's remove it. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests: Remove reference to aszlig.i3aszlig2016-05-281-3/+0
| | | | | | Forgot to do that in ea85dd3eaf0cbd19ddf22f41391d092a21147063. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests: Remove dummy test for i3aszlig2016-05-281-41/+0
| | | | | | | | | | | | We already have an "i3wm" test in upstream <nixpkgs> which is much more thorough than the unfinished test I've made here. The intention of this test however was to specifically test the Vuizvui service module. Nevertheless, it's still just a dummy test and the "i3wm" test works much better, so let's remove it until we have a more complete implementation. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests/gnupg: Enable scdaemon supportaszlig2016-04-041-0/+1
| | | | | | | We're not testing this thoroughly though, but this makes sure that we don't accidentally break module support for scdaemon. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Rename gpg-agent to gnupgaszlig2016-04-043-4/+6
| | | | | | | | | We do things such as placing gnupg into environment.systemPackages, so calling this just "programs.gpg-agent" doesn't fit that. Especially if we really want to have a way to specify configuration values in case I'm getting masochistic someday ;-) Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Add a new module and test for gpg-agentaszlig2016-04-023-0/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since NixOS/nixpkgs@5391882 there no longer is the option to start the agent during X session startup, which prompted me to write this module. I was unhappy how GnuPG is handled in NixOS since a long time and wanted to OCD all the configuration files directly into the module. Unfortunately, this is something I eventually gave up because GnuPG's design makes it very hard to preseed configuration. My first attempt was to provide default configuration files in /etc/gnupg, but that wasn't properly picked up by GnuPG. Another way would have been to change the default configuration files, but that would have the downside that we could only override those configurations using command line options for each individual GnuPG component. The approach I tried to go for was to patch GnuPG so that all the defaults are directly set in the source code using a giant sed expression. It turned out that this approach doesn't work very well, because every component has implemented its own ways how to handle commandline arguments versus (default) configuration files. In the end I gave up trying to OCD anything related to GnuPG configuration and concentrated just on the agent. And that's another beast, which unfortunately doesn't work very well with systemd. While searching the net for existing patches I stumbled upon one done by @shlevy: https://lists.gnupg.org/pipermail/gnupg-devel/2014-November/029092.html Unfortunately, the upstream author seems to be quite anti-systemd and didn't want to accept that into the upstream project. Because of this I went for using LD_PRELOAD to pick up the file descriptors provided by the systemd sockets, because in the end I don't want to constantly catch up with upstream and rebase the patch on every new release. Apart from just wrapping the agent to be socket activated, we also wrap the pinentry program, so that we can inject a _CLIENT_PID environment variable from the LD_PRELOAD wrapper that is picked up by the pinentry wrapper to determine the TTY and/or display of the client communicating with the agent. The wrapper uses the proc filesystem to get all the relevant information and passes it to the real pinentry. The advantage of this is that we don't need to do things such as "gpg-connect-agent updatestartuptty /bye" or any other workarounds and even if we connect via SSH the agent should be able to correctly pick up the TTY and/or display. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Add new Starbound service and testaszlig2016-03-152-0/+120
| | | | | | | | | | | | | | | | | | | | | Very preliminary and doesn't have all the option descriptions right, nor does it have convenience features such as setting allowAdminCommands based on whether any users are defined with admin privileges. Of course the latter needs to undergo the decision on how to handle RCON connections, because the latter *might* need that option. But apart from that single option, there are a lot more options we need to flesh out. Also, the test currently is very limited and only spins up a client, connects to the server and does a movement (just walk to the right). Needless to say, it's even quite fragile and relies on OCR to properly detect the custom pixel fonts from Starbound. Which unfortunately fails most of the time. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-29 10:18:03 +0000