southnode
southnode
A note on this is that the provisioning would likely be better off looking at the current restrict settings for all systems, for instances where, for example, you might have...
^^ seconded
This is still a major issue. Controller really needs to be able to re-query the instances in realtime that exist on it whilst it's online - we can't keep restarting...
@IceOfWraith this isn't resolved, and is one of our outstanding problems. Users cannot create users - they don't show up Users cannot create groups - there is no option to...
Testing methodology @IceOfWraith for complete confidence in a controller > target setup in an enterprise environment: Create a user, specifically have them have manage access to one instance Login as...
So from the Torch github - https://github.com/TorchAPI/Torch/issues/449 This was the original issue with Torch running as the network service just immediately shutting down. Torch could theoretically work with AMP now...
@PhonicUK Controller > Target will ban this across the entire target and controller stack, wherein the controller requires a restart to remove the honeypot ban
Just something that does it because that's not documented anywhere.
Bumping for visibility here, would be a good enhancement and bring the feature set alongside many other tools in the space.
Realistically this should be a simple process, no? Would require that a user have a common user on the nodes. Could have the caveat that it can only move between...