Skip to content

Please add gss-ntlmssp as Recommends to the powershell debian package #11374

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.

Sign up for GitHub

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

Jump to bottom
Closed
rhertzog opened this issue Dec 17, 2019 · 6 comments
Closed

Please add gss-ntlmssp as Recommends to the powershell debian package #11374

rhertzog opened this issue Dec 17, 2019 · 6 comments
Labels
Area-Maintainers-Build specific to affecting the build Issue-Enhancement the issue is more of a feature request than a bug Resolution-By Design The reported behavior is by design.
Milestone
7.1-Consider

Comments

@rhertzog
Copy link

Someone reported to us (Kali) that Enter-PSSession is not working (see https://bugs.kali.org/view.php?id=5915) but we are only installing the package that you provide. From a quick search it looks like that the Debian package that you build should be modified to "Depends" (or "Recommends" if you want it optional) on the "gss-ntlmssp" package that provides the required NTLM support (through a plugin) to libgssapi-krb5-2 which you are already depending on.

FWIW, this is related to #6647 but I wanted to highlight the fact that the Debian package should be modified, whereas the current solution was to modify the docker image to add the missing package. By adding the dependency on the package itself, it would automatically fix all use cases.
@rhertzog rhertzog added the Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a label Dec 17, 2019
@iSazonov iSazonov added the Area-Maintainers-Build specific to affecting the build label Dec 17, 2019
@iSazonov
Copy link
Collaborator

/cc @TravisEz13 Could you please look the proposal?

@TravisEz13
Copy link
Member

I would not recommend installing this. cc @SteveL-MSFT What are your thoughts?

@SteveL-MSFT
Copy link
Member

My concern is that we don't have test coverage for this and including it implies we've validated it and support it.

@TravisEz13 TravisEz13 added Issue-Enhancement the issue is more of a feature request than a bug and removed Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a labels Jan 7, 2020
@TravisEz13 TravisEz13 added this to the Future milestone Jan 7, 2020
@iSazonov
Copy link
Collaborator

iSazonov commented Jan 8, 2020

Maybe add a unsupported note to Linux PowerShell installation docs? It is common for such Linux users to use special configurations.

@rhertzog
Copy link
Author

rhertzog commented Jan 8, 2020

You do realize that you ship that package in some of the docker images that you provide?

For example for centos, this got merged: PowerShell/PowerShell-Docker#125

It seems really strange to have different standards for various distributions. Also the lack of test coverage can be tracked in a separate issue/request, it seems weird to require someone to write functional tests to get this one-line patch merged (since adding a dependency is really trivial).

@SteveL-MSFT SteveL-MSFT modified the milestones: Future, 7.1-Consider Jan 8, 2020
@BitDesert BitDesert mentioned this issue Jan 16, 2020
Closed
@TravisEz13 TravisEz13 added the Resolution-By Design The reported behavior is by design. label Aug 20, 2020
@TravisEz13
Copy link
Member

Users can manually install the package. We don't recommend installing NTLM on non-Windows

The package being included in docker is an independent decision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Maintainers-Build specific to affecting the build Issue-Enhancement the issue is more of a feature request than a bug Resolution-By Design The reported behavior is by design.
Projects
None yet
Milestone
7.1-Consider
Development

No branches or pull requests
5 participants
@daxian-dbw @rhertzog @TravisEz13 @SteveL-MSFT @iSazonov