you can create an equivalent at the create-module step and store them in environment
I am not sure what i was trying to do as well, but its something to…
looks like i am only limited to using these two methods 2024-02-06T11:35:36+03:00 [1:vaultwarden2:vaultwarden-app] Please generate a secure Argon2 PHC string by using vaultwarden hash or argon2.
And mor einfo as documented here: Enabling admin page - vaultwarden - Gitlockr | A self hosted version of Gitea
PHC is found here: phc-string-format/phc-sf-spec.md at master · P-H-C/phc-string-format (github.com)
@step hello,
How would i implement an internal module thats not supposed to be exposed on the intenet, but only available to be consumed and used by normal modules.
In gernal most modules mus timplement publish, which exposes the module, if this publish is not given, will this be the case, or what exactly happenes
1 Like
You can open a port restricted to the localhost like you do in the pod and do not create a route in traefik. Like this any other modules could contact your module by the 127.0.0.1:tcpport but nobody from the external could have a route to this module
The cons is that you won’t have encryption by traefik so you need to make it workable on your own
Hence maybe using traefik is the easier way
2 Likes
Easier is not always the best, anyways, I’ll just leave it normal, maybe as I gain more experience I can figure it out.
I had no Idea that modules can get dangerous.
A certain version of a module i was building caused a Loop during the upgrade process
Attempts to remove the module through the normal means are proving to be futile
I am attempting a reboot to see if it resolves the issue.
Could we implement a Core level check that would prevent a module installation, Update or any other processing to run forever for any given module.
MAybe a NS8 parameter that checks for this kind of behavior in a module action state, and stops it.
From a security perspective i can see Many ways a Bad Actor could use that loopHole.
The reboot seems to fix the issue, But assume, someone adds a scrip that restarts the process on boot.
Make a broken module is always easier than make a robust module and at core level there is no way to control what a developer could do I think.
Except maybe with a strict control of what a developer does by implementing rules and permissions like apple does. However it could become a nightmare for you martin
Look the last apple vision pro, the only thing for what I want it is for pornoVR and it is forbidden (dont tell it to my wife)
3 Likes
What a wonderful business
2 Likes