exploitoverload / pwnixos Goto Github PK

Hey! Nice project, but there seems to be a few things that could see some love from the maintainer(s).

1. The usage of with lib;

Most good nix projects actively avoid with scopes. For better maintainability, those should be replaced with explicit inherits.

2. Lack of modularity

If this is meant as your personal config, and that only - it's perfectly fine. Otherwise, it will come off as too opinionated and could probably benefit from 1. an internal module system and 2. exposing some of the "pwning" related options as nixosModules that are directly importable from outside.

3. Confusing structure

Sticking everything in a modules directory is probably a bad idea. Maybe divide things by function so that it's easier to find what you're looking for?

Hello im trying to get greetd to autologin on my fork;
https://github.com/etherbiswas/nixos

it currently doesnt work even when user is added to greetd group manually, i tried adding hashed password for the user but no luck.
Most of the config is same as yours i just remove the hashed password.

Hey Asier,

thank you very much for providing this project. I followed the the installationguide on a fresh setup (installed NixOS with Gnome). building from the Flake went well (besides one warning that "exa" is deprecated and "eza" should be used), but after rebooting it still goes to the GNOME shell. Tried to figure out why it happens, but I'm kinda at an in-pass right now.

• It shouldn't be an issue to have the initial setup using GNOME, correct?
• Having two configuration.nix files (the system-generated one at /etc/nixos/ and the one provided here at ~/.config/nixos/) is fine too?
• Currently using MBR instead of EFI, since it's running inside a VM. Could that cause the issue?

Any thoughts/ideas would be very much appreciated :)

Hey, would you consider adding more modularity/customization to the flake?

So that for ex. the user could choose the specific category of tools to install/use (web-pentesting, reverse-engineering, etc..).
IMO it would be a great idea, so that people can just add the flake on top of their existing configuration and use a specific set of packages.
Also, would you consider adding more tools that are blue-team oriented, or is this flake solely for red-teamers?

It could also be a nice idea to add options to use the full environment, or to use the flake onto an existing system (although this could already be done, it's not really practical since you need to modify the flake manually)

hi @exploitoverload, appreciate your work.

I couldn't help but wonder, is it possible to mount your configurations (as a channel or something?), instead of replacing my existing configurations?

I recently came across musnix, a set of configurations that will make any nixos laptop music-production ready. At First, i somewhat doubt it, in fear of overriding my configurations; until i found out that i only needed to include it as a channel, and paste 4 lines of code on my precious configuration.nix. Done.

can it be done this way? so that, if one wants to install every pentesting tool, one would just enter one line of code into configuration.nix eg: PwNixOS.pentesting.installAll = true;.

Cause honestly, i think even nixpkgs can not keep up with the current speed of updates of these tools on github, and overlaying each one of them makes me wanna puke when i look at my configurations.nix. With its increasing growth of amalgamation of overlays. You can abstract these overlays from the user by hiding them inside PwNixOS configuration? which can be included by the user like this:

    1    {
    2         imports =
    3            [ # ...
    4                 <PwNixOS>
    5            ];
    6
    7         PwNixOS.pentesting.installAll = true;
    8         
    9    }

I'm not fluent with Nix programming (as I've been using nixos for 4 months), but I'm willing to put in the time; cause honestly, think this project will single-handedly make NixOS cooler than parrotOS.

thanks, for your time bruv.