Skip to content
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

[Feature Request] Optional Caching of Retrieved Data #7

Open
tylerdotrar opened this issue Feb 7, 2025 · 1 comment
Open

[Feature Request] Optional Caching of Retrieved Data #7

tylerdotrar opened this issue Feb 7, 2025 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@tylerdotrar
Copy link

To the best of my understanding, upon execution rusthound_ce stores objects and queries in the host's memory rather than any other caching methods.

In most cases this is fine, but unfortunately in very large environments it is very possible for the rusthound_ce executable to utilize excessive amounts of RAM (e.g., > 32GB). Upon resource exhaustion and without proper caching, hours of querying and processing is can be lost -- resulting in an "Error: EndOfStream" message.

Similar to AD-miner, a caching option would be nice. I understand this is more of an outlier / niche issue, but a simple toggle parameter, an option to cache every X objects (e.g. --cache 100000), an option caching if the tool fails mid-LDAP object retrieval, or really anything could be a nice quality of life improvment.

@g0h4n g0h4n added enhancement New feature or request help wanted Extra attention is needed labels Feb 9, 2025
@g0h4n
Copy link
Owner

g0h4n commented Feb 9, 2025

Indeed actually, this feature is one of the most essential in RustHound CE and requires thorough examination on my part. All help is welcome to develop this feature 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants