Skip to content

proposed extra bits to script and spelling fix#1

Open
Prezj1 wants to merge 3 commits into
strikoder:mainfrom
Prezj1:changes
Open

proposed extra bits to script and spelling fix#1
Prezj1 wants to merge 3 commits into
strikoder:mainfrom
Prezj1:changes

Conversation

@Prezj1

@Prezj1 Prezj1 commented May 31, 2026

Copy link
Copy Markdown

proposed changes and spelling fixes

@strikoder strikoder left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I like the script a lot, but still needs some improvements.
I'm going to change readme completely, since it has yet more typos that are not in the PR as well.

Comment thread LinEnum-ng.sh Outdated


# ---- Shell users cross-reference hunt ----
echo -e "\n${YELLOW}[+] ${NC}Harvesting users with a login shell from /etc/passwd:"

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I really like this idea. However, this takes a lot of time on many boxes, IRL, it should be added as a flag like --hunt-users or smth similar.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Thats a good shout

Comment thread LinEnum-ng.sh Outdated
done

# ---- Dot files in home directories ----
echo -e "\n${YELLOW}[+] ${NC}Readable dot-config files in home directories:"

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I think the dot files section could be combined with the word readable files and could put under the WRITABLE LOCATIONS section.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Thats a good shout

Comment thread LinEnum-ng.sh Outdated
fi

# ---- Config files readable in common app dirs ----
echo -e "\n${YELLOW}[+] ${NC}Readable config files in common application directories:"

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

This generates a lot of noise, especially when a custom application is installed on the machine, I think manual enumeration would be better for such a case.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Thats a good shout

@Prezj1

Prezj1 commented Jun 8, 2026

Copy link
Copy Markdown
Author

I like the script a lot, but still needs some improvements. I'm going to change readme completely, since it has yet more typos that are not in the PR as well.

Thanks mate, I can try to make the requested changes during the week then push them if that's okay

@strikoder

Copy link
Copy Markdown
Owner

Of course, take your time & I'm sorry about the delay on my side, I just wanted to do some testing before merging anything into main.

Comment thread README.md
> A focused, stable, OSCP-oriented Linux privilege escalation enumeration script.
> ![LinEnum](https://github.com/user-attachments/assets/a702bc2c-dd14-4fba-927c-f8d505e5df2b)
<img width="640" height="640" alt="LinEnum-ng" src="https://github.com/user-attachments/assets/bed1425d-3133-46c6-bf91-dd49ee8d47bf" />

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I mean that's not a huge diff but okay

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Could you change the repo's version to 1.0.1 so that when I accept your PR, the version in the readme and the script would be updated instantly?

Comment thread README.md Outdated
| Color output | ❌ | ✅ linPEAS-style color scheme |
| Password spray hint | ❌ | ✅ Reminds you to try found passwords against all users |
| | LinEnum | LinEnum-ng |
|---|---|---|

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I want to keep the emojis tbh

Comment thread README.md
**linPEAS changes too much between versions and has too much noise for a 24H exam.**

If you've done enough OSCP boxes, you've hit this: a specific linPEAS version finds the vector immediately, then you update and the next version misses it entirely (happend to me on the exam), output restructured, noise level changed.
If you've done enough OSCP boxes, you've hit this: a specific linPEAS version finds the vector immediately, then you update and the next version misses it entirely (happened to me on the exam)!

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I will just accept the typo fix in here

Comment thread README.md Outdated
| 🟣 Magenta | Exploitation steps, links, and remediation hints |
| Color | Meaning |
|-------|---------|
| **Red text on yellow background** | Confirmed vulnerability or critical misconfiguration |

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Please keep the emojis. Also, the extra spaces in the Markdown table don't affect the rendered output, so there's no need to change them.

Comment thread README.md Outdated
| OSCP-scoped, no noise | ✅ | ⚠️ Very verbose | ✅ |
| Feature | LinEnum | linPEAS | LinEnum-ng |
|---------|---------|---------|------------|
| Kernel CVE matching | No | Yes | Yes |

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Same as Above

@strikoder

Copy link
Copy Markdown
Owner

Thanks for the new PR! I'll put it through extensive testing and get back to you with feedback in about a week.

@strikoder

Copy link
Copy Markdown
Owner

@Prezj1
LGTM. One minor inefficiency: the dotfile loop iterates over /root the same as any /home/* dir without first checking if we can traverse into it. If /root isn't executable, all those [ -r "$target" ] calls fail silently at the directory level anyway, so we're burning stat calls for nothing. Worth adding a [ -x "$homedir" ] guard before entering the loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants