Remote Registry Management (integration) - reg + cmd

[LockBB1]

• Add a new Registry device tab for MeshCentral on desktop and mobile layouts
• Implement a dedicated Registry tunnel on protocol 4
• Add read-only Registry browsing with hive listing, key navigation, path input, and details view
• Add core Registry write operations: New Key, New Value, Edit, Rename, Delete
• Add .reg export for selected Registry keys
• Integrate Registry with MeshCentral session tracking, relay indicators, event logging, and user consent controls

[si458]

We will talk about this at the next community meeting before we integrate it

Also I have a few questions/comments

1. Why are u running cmd.exe when the win-registry module can do all that for u as it talks directly with the windows api???
2. plz don't add anything to package.json/package-lock.json!
3. Screenshots/video missing
4. What about tab permissions so only certain users can access the registry tab?

[LockBB1]

We will talk about this at the next community meeting before we integrate it

Also I have a few questions/comments

1. Why are u running cmd.exe when the win-registry module can do all that for u as it talks directly with the windows api???
2. plz don't add anything to package.json/package-lock.json!
3. Screenshots/video missing
4. What about tab permissions so only certain users can access the registry tab?

Thank you for your comments, I agree with you.

1. I started with cmd +reg, because when setting up a new tunnel, it was easy to perform testing and this simplified the first stage of implementation while I was checking the operability of the process. I agree that win-registry is the best implementation since MeshCentral already uses it. I can rebuild registry write/read operations under win-registry.

2. Understood. They should not have been part of this change, I will remove them from the PR.

3. I've pinned down a few screenshots

4. I completely forgot about it, I will try to implement the restrictions in the near future.

[si458]

@LockBB1 thank you for the reply!
I'm going to be a pain now (sorry)
would it be possible for you create a new branch with the removal of cmd and using win-registry instead and then a separate pr for that?
This just then allows the community to test each of them and decide if they want to use cmd or the integrated win-registry!
Look forward to the results etc!

Edit: also github security bot is not happy with your code! Please can you check it out and fix the code etc

[LockBB1]

@si458 No problem, I'll make a new branch and publish the rework on win-reg, but I'll start working on user permissions.

[LockBB1]

@si458 i've improved the functionality.