Skip to content

Connecting to a different Configuration (Powershell) #238

Open

Description

@brendanmeyer

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

Activity

  1. mwrock commented on Oct 27, 2016

    @mwrock
    Member

    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.

  2. brendanmeyer commented on Oct 27, 2016

    @brendanmeyer
    Author

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

  3. fwininger commented on Mar 1, 2020

    @fwininger
    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 ?

  4. fwininger commented on Mar 5, 2020

    @fwininger
    Contributor

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

  5. brendanmeyer commented on Mar 6, 2020

    @brendanmeyer
    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

  6. fwininger commented on Mar 6, 2020

    @fwininger
    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions