Skip to content

modules/exploits/solaris: Resolve RuboCop violations #20073

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bcoles
Copy link
Contributor

@bcoles bcoles commented Apr 22, 2025

Most violations were resolved with rubocop -A, except notes.

The RSH stack clash module needs some work to move the C source into a standalone file in external/, but this is outside the scope of this PR.

@bcoles bcoles added the code quality Improving code quality label Apr 22, 2025
@bcoles bcoles force-pushed the rubocop-modules-exploits-solaris branch from 0583bd0 to 0ef9f30 Compare April 22, 2025 15:18
end


def exploit
Copy link
Contributor

@adfoster-r7 adfoster-r7 Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have SPARC hardware to test, but yes, is should. The check function doesn't set up anything required by the remainder of the module. spc_connect is called within attack within the exploit method.

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

Successfully merging this pull request may close these issues.

2 participants