-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Pipal lag and failure to complete analysis (RAM limitations?) #42
Comments
The readme is out of date, 1.9 was recommended over 1.87.
There is an issue with memory usage as it caches the results as it goes
through so with such a big list it will be eating a lot of memory.
I've got a rewrite that isn't release yet that stores the results on disk
rather than in memory and runs quite a bit faster. I should try to get the
finished off and released. Till then, try using just one checker at a time,
that will reduce the memory usage.
…On Sat, 7 Apr 2018, 22:30 tokyoneon, ***@***.***> wrote:
Hey @digininja <https://github.com/digininja> , I would like to feature
pipal on Null Byte <https://creator.wonderhowto.com/tokyoneon/>, but I'm
experiencing an issue.
The wordlist being analyzed is 92,400,000 lines, 1.1Gb. Pipal seems to lag
after ~2 hours of processing. At that point my CPU usage drops down to
normal levels and the ETA starts to slowly increase until it stops. This
was done in a Kali VM with 4 cores and 6Gb RAM. Tried again on a dedicated
Ubuntu machine with an i7 and 16Gb RAM -- same issue.
Does pipal have limitations? What might be causing the lag and how can I
debug?
EDIT:
I just realized Ruby v1.9 is recommended in the README.
> apt-cache policy ruby
ruby:
Installed: 1:2.5.0
Candidate: 1:2.5.0
Version table:
*** 1:2.5.0 500
500 http://http.kali.org/kali kali-rolling/main amd64 Packages
100 /var/lib/dpkg/status
But pipal works fine when analyzing smaller wordlists using v1.2. Should I
try manually installing v1.9.x in Kali? There's an APT candidate for v2.3
and v2.5, will those suffice?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHJWYZUOH6RgLuXVwsmx62TuEV3sWqdks5tmS_ngaJpZM4TLQt7>
.
|
Thanks for the reply. I think the Do you have an estimated time frame for when the rewrite will be uploaded to GitHub? I wanted to publish my article ~Tuesday but I might be able to postpone it a few days. I would really like to analyze this large wordlist and feature it in the article. |
It won't be this week. Would you be able to send me the list? I'll run it
through and send you the results, would be a good test.
…On Sat, 7 Apr 2018, 22:52 tokyoneon, ***@***.***> wrote:
Thanks for the reply. I think the basic.rb checker is the only one
enabled.
Do you have an estimated time frame for when the rewrite will be uploaded
to GitHub? I wanted to publish my article ~Tuesday but I might be able to
postpone it a few days. I would really like to analyze this large wordlist
and feature it in the article.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHJWR-nTAKCv_efubB9f7tNdjbnUemPks5tmTUSgaJpZM4TLQt7>
.
|
-----BEGIN PGP MESSAGE----- hQEMA3E/TAUfwjjMAQf/cVlnFK8SwdHmrKPkDYnpNveAxO2hSCvo4xlcYpl7DMUL |
Thanks for your help btw. Think you can analyze it this weekend? |
Unfortunately I'm currently sat in a hotel about to run a marathon so might
not be home in time tonight to do it.
Where did you get the PGP key? If it was keybase I can read your message,
if not, try again and I'll go out and try to kill the key wherever it is.
…On Sun, 8 Apr 2018, 02:59 tokyoneon, ***@***.***> wrote:
Reopened #42 <#42>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHJWe2JOdvM8-X72SfROeiAkdGi_I6aks5tmW72gaJpZM4TLQt7>
.
|
Yup, Keybase. I did notice an older key on the MIT database, but figured it was revoked/expired.
I think I'll postpone the article till Thursday if you don't get to analyzing the database this weekend. The article will be more interesting for it. So it's worth the wait 👍 |
Oh, if possible, get the
|
Hey, really sorry, looks like I deleted the keybase app from my other computer. I can't view the messages you sent me. I would have to reset my entire Keybase account to regain access Keybase's chat functionality, but doing so would still wipe my previous message history. Would you be able to send me PGP blocks here or via email? Really sorry for the inconvenience. #EncryptionFail |
Ye sure, will send it over in some way.
Not all the checkers are working yet but I'll get as many going as I can.
…On Mon, 9 Apr 2018, 02:20 tokyoneon, ***@***.***> wrote:
Hey, really sorry, looks like I deleted the keybase app from my other
computer. I can't view the messages you sent me. I would have to reset my
entire Keybase account to regain access Keybase's chat functionality, but
doing so would still wipe my previous message history.
Would you be able to send me PGP blocks here or via email? Really sorry
for the inconvenience. #EncryptionFail
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHJWSXQF0ZAqgIy1sgPEJUyLh_6tv1Wks5tmrdwgaJpZM4TLQt7>
.
|
Hey @digininja , I would like to feature pipal on Null Byte, but I'm experiencing an issue.
The wordlist being analyzed is 92,400,000 lines, 1.1Gb. Pipal seems to lag after ~2 hours of processing. At that point my CPU usage drops down to normal levels and the ETA starts to slowly increase until it stops. This was done in a Kali VM with 4 cores and 6Gb RAM. Tried again on a dedicated Ubuntu machine with an i7 and 16Gb RAM -- same issue.
Does pipal have limitations? What might be causing the lag and how can I debug?
EDIT:
I just realized Ruby v1.9 is recommended in the README.
But pipal works fine when analyzing smaller wordlists using v1.2. Should I try manually installing v1.9.x in Kali? There's an APT candidate for v2.3 and v2.5, will those suffice?
P.S. I'm not a ruby coder
The text was updated successfully, but these errors were encountered: