- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat(wp): support csh, no sudo scan #1523
feat(wp): support csh, no sudo scan #1523
Conversation
csh対応 |
|
Thanks, @kurita0 It seems that unnecessary commits are mixed in. |
e105bd5
to
906bd46
Compare
rebase done. |
Please share your commands, config.toml, WordPress environment setup, before/after behavior, etc. to validate your PR. |
commnads
config.toml
before
Sakura server does not allow users to sudo. after
|
I don't think it's a good idea to base whether or not a scan user name and a WordPress user name are the same to determine whether or not a command requires permissions to execute.
Regarding the csh support, I would be glad if you could work on it. |
Add
Implemented. config.toml
after
|
Are you going to write a document about NoSudo and its operational case? |
118940d
to
bbbbbee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
bbbbbee
to
c380c10
Compare
Co-authored-by: MaineK00n <mainek00n.1229@gmail.com>
c380c10
to
100c940
Compare
What did you implement:
Support for environments where sudo cannot be used or when the shell is csh, so that users of the following rental servers can use WordPress scan.
https://help.sakura.ad.jp/rs/2251/?article_anchor=js-nav-3
Type of change
How Has This Been Tested?
Setup
When sudo can be used(ServerInfo.User's Shell is ash)
config.toml
before
after
When sudo cannot be used(ServerInfo.User == ServerInfo.WordPress.OSUser, ServerInfo.User's Shell is csh)
config.toml
before
after
after(ServerInfo.User's Shell is bash)
config.toml
When sudo cannot be used(ServerInfo.User != ServerInfo.WordPress.OSUser, ServerInfo.User's Shell is bash)
setup only for this case
$ ssh -i /home/mainek00n/github/github.com/MaineK00n/vuls-targets-docker/wordpress/.vagrant/machines/default/virtualbox/private_key -p 2222 root@127.0.0.1 apt-get purge -y sudo
config.toml
before
after
after(If the Switch User requires a Password)
config.toml
Checklist:
You don't have to satisfy all of the following.
make fmt
make test
Is this ready for review?: YES
Reference