[
https://issues.apache.org/jira/browse/KNOX-2631?focusedWorklogId=635623&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-635623
]
ASF GitHub Bot logged work on KNOX-2631:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Aug/21 18:16
Start Date: 07/Aug/21 18:16
Worklog Time Spent: 10m
Work Description: lmccay commented on pull request #477:
URL: https://github.com/apache/knox/pull/477#issuecomment-894688536
> I'm pretty worried about where this is going - where it looks like it
spawns shells on the Knox host. This opens up a wide range of attacks
potentially and doesn't look like there is protection against those.
@moresandeep hinted at a bunch of them in the review as well.
>
> Secondarily, not sure why we are copying full JS and CSS files without
much attribution or versions where they came from. Most of the newer UIs are
using npm to at least ensure we are declaring our dependencies.
>
> https://issues.apache.org/jira/browse/KNOX-2631 doesn't seem to have much
detail about the design of this feature so not sure if this is POC or what, but
I don't think its close to ready to be merged.
It is indeed POC status. @luliu8 is interning with us and this is a first
iteration PR. The codereview details are great here, @risdenk and will help
clean this up for the next iteration. The security implications are also being
considered and will ultimately be reviewed closely. The idea here is to
strictly allow the same sort of trusted proxy based impersonation for Shell
access as we do for all other proxied resources. We will need the same level of
protections for this as we have for hadoop trusted proxies.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@knox.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 635623)
Time Spent: 2h 40m (was: 2.5h)
> KnoxSSO for Secure Shell Access
> -------------------------------
>
> Key: KNOX-2631
> URL: https://issues.apache.org/jira/browse/KNOX-2631
> Project: Apache Knox
> Issue Type: New Feature
> Components: Homepage, KnoxSSO
> Affects Versions: 1.5.0
> Reporter: Lu Liu
> Assignee: Lu Liu
> Priority: Minor
> Fix For: 1.6.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> While Apache Knox aids in helping to lessen the need to gain physical access
> to deployment machines, there are still numerous compelling reasons for users
> to require such access:
> 1. Debugging, log access, etc
> 2. CLI use and automation
> 3. beeline and other clients that are deployed to gateway machines
> Gaining access to a shell for these purposes currently requires the user to
> have
> an ssh client installed and valid credentials that can be used for ssh, such
> as:
> username and password or SSH keys. Separate management of credentials for this
> access introduces some additional complexities which may even violate
> enterprise
> infosec policies and require the secure distribution and management of keys.
> The intent of this proposed improvement is to add a browser based terminal
> application
> that will provide secure access to a shell on the Knox machine. Just as any
> resource
> exposed by or hosted by Knox, you would be able to protect access to this
> terminal
> with any of the available security providers. We would also like to make this
> available out of the box as available from the Knox Homepage. This would make
> the
> terminal/shell available via KnoxSSO thus providing shell access with your
> existing
> enterprise credential authenticated SSO session.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
