Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to a different Configuration (Powershell) #238

Open
brendanmeyer opened this issue Oct 26, 2016 · 6 comments
Open

Connecting to a different Configuration (Powershell) #238

brendanmeyer opened this issue Oct 26, 2016 · 6 comments

Comments

@brendanmeyer
Copy link

Hi, I was wondering it the ability to connect to predefined PowerShell ConfigurationName with WinRM as you can with Enter-PSSession

for example the equivalent with Enter-PSSession command
Enter-PSSession -ComputerName -ConfigurationName "differentconfiguration"

If it currently isn't possible, it would be a great feature, as it will allow different configurations which in turn allows remote scripts to run as a standard user with restricted commands instead of more full powered powershell session.

Thank you
Brendan

@mwrock
Copy link
Member

mwrock commented Oct 27, 2016

Its not currently supported. Its actually not a feature of the PSRP specification but is a convenience implementation of the Windows native PSRP client (powershell remoting). That does not at all mean it would not be considerd for implementation here.

@brendanmeyer
Copy link
Author

Thank you for the information. I will keep any eye on the project.

@fwininger
Copy link
Contributor

Hello @mwrock, we would like to use JEA to enforce some restriction on our admin user.

I can develop this feature, do you have some link to understand how it's implemented by MS ?

@fwininger
Copy link
Contributor

I think I have enough information to develop a PR for this.

@brendanmeyer
Copy link
Author

that would be great, and very useful for adding restricted sessions, thank you

It would also be nice for this to work with Invoke-Command if possible as well

@fwininger
Copy link
Contributor

I'm able to connect a JEA session but I have a issue with the current implementation of this gem because after the PSRP pipeline is open the gem use :

Invoke-Expression -Command "body_script"

So right now, I need to allow Invoke-Expression in the JEA session and that is a insecure command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants