Starting caged applications under correct priviliges

[bencikpeter]

Resolving #66

Chage summary:

• Group name is now random
• Group does not stay in the system anymore
• Group is added to the token
• Caged applications are now started under logged on user, not under system (tokenLibis using a physical console user as a template token and not CageManager token as before)

[bencikpeter]

Why so nitpicky all of the sudden? 😄 😄 Fixed and merged 😉

[DonatJR]

@bencikpeter I'm always like that, there is no point in doing something only half right ;) just holding back a little for code in your library as I do not want to annoy you too much 😂 thanks for the fix 👍

[bencikpeter]

@DonatJR well... I was actually thinking about some last refactoring before I move to a completely different part of the project so... throw all your complaints at me 😂 And I´ll see what can I do 😇

[bencikpeter]

Uhhhh 😬 Fixed by #80

[SailReal]

Sorry but we have to revert this merge. We didn't actually check if all functionality is still working (just looked at the code, our bad ...). The configs can no longer be selected by the Chooser and starting the Cage does not actually spawn any processes.

[bencikpeter]

Any more data on that? The chooser should not be affected at all by this change, are you sure the problem is here?

[SailReal]

First you can ignore the problem with the chooser, the main issue is that the createProcess fails for some reason. Maybe we can look into the problem with the chooser and you figure out what the problem is with launching the applications?

[bencikpeter]

@SailReal Agreed.

For the createProcess :Actually... it fails only for non-console applications... console ones launch just fine (that was my bad, I tested only on console apps), anything else fails to launch