IndexError: string index out of range (Interlace) #752
Comments
|
ping @0xtavian |
|
Hey @Nishantbhagat57 sorry for the delay. can you show me the module you’ve written? I have a feeling we can rearrange a few things so interlace doesn’t complain about them. The scan should continue even though you received that error. Does it not? |
|
@0xtavian Sorry for my late response, I didn't got any notification :| Module I am using: For this module to work, you have to install unfurl and x8 My input file size is 13.1 MB [containing 143190 urls] with content like this: Axiom command: It works well if my input have less contents. But when my list is huge the output is: |
|
@Nishantbhagat57 Hey so admittedly, I have not tried these but hopefully they work or need small changes. I would first try: If that still doesnt work (it should at least reduce the amount of errors), i would try a simple module instead Even tho your terminal might be filling up with errors, the scan is still progressing and ends up finishing right? Granted with less results than expected? |
|
@Nishantbhagat57 If the above doesnt work for you or you'd rather have a one-shot module, please try this patch of axiom-scan https://github.com/pry0cc/axiom/blob/_safe-target_/interact/axiom-scan and use the added Basically these errors could be attributed to not adding the We have not added the With this patch we replace all occurrences of Please join us on our discord to continue to troubleshoot https://discord.com/invite/c6BHVfn |
|
@0xtavian This command works fine with short urls list: Here I have added '' to But the errors are same when the input urls list is huge: If I replace And I get this error: |
|
@0xtavian Sorry I think I have to install this patch |
|
@0xtavian So I did everything. Actually I reinstalled axiom using this command: Can you see this: codingo/Interlace#143 Someone had the same issue, opened a pull request but in the end it was closed and the request wasn't merged. Maybe that will solve this issue? |
|
@0xtavian OK so I was dumb...This time I did what I should have done. I simply changed the content of The module worked fine when the input urls list had less lines. But with big list the error is still same: |
|
@0xtavian Output is same even with Command: |
|
@Nishantbhagat57 unfortunately in this case you’ll have to use a Simple Module. Can you upload a copy of the target list so I can take a look? try something like this |
|
@0xtavian No, the problem is not with module at all. To verify this I tried my input file with different modules, for example this katana module: My command: The interlace gives
The axiom-scan works perfectly if:
Here is the input file which I am using: https://1ty.me/b1TqT |
|
@Nishantbhagat57 sorry for the confusion. So what we call Simple-Modules are modules that don’t contain the string Since Interlace isn’t handling the threading you shouldn’t get these errors when using a Simple Module, only with one-shot modules in ur case. The amount of lines in the target list shouldnt matter. That’s not a very large target list either. I’ve scanned 10s of millions of targets before, for example. I don’t believe the amount of threads changes anything either. The issue is, some lines in your target list aren’t playing nicely with Interlace. To avoid using Interlace in this way, use a Simple-Module. Have you tried something like this? Can you show me the output? can you join our discord so we can chat? |
|
@0xtavian I have joined your discord but there are a lot of members and I couldn't figure where to chat with you. As you said using Simple-Modules I will not be dependent on Interlace Threading. So I think I can make this to work by using rush for running x8 in parallel. But still there are some issues and to solve those issues I need your help. First I tried this: Here everything is good but x8 can't write to output file, So I thought it can't access the value of output that axiom-scan wants to give it as I am using output inside rush. So then I tried different approach i.e testing what is really happening: Here I really can't figure out why it is not echoing value of folder as xyz If I can make that happen then I can use something like this: But the thing is, If I try the below module, it is giving me the value of output as output and not the exact output folder path, so the above commands maybe will not work even if we figure a way to pass the output folder value to rush: For testing you can use katana instead of x8 as it requires cargo, ruby and brew which takes around 30-40 minutes to install. Katana test module with rush similar to x8: At this point I am exhausted and I don't have any more ideas. |
Post in the axiom channel and we’ll chat
Change the extension to Look thru the the modules we have for examples. I would avoid using subshells if possible but they are certainly supported.
output and input are not variables. input is always a list. output is either a file named output or a folder named output, depending on the extension mentioned in the module. Please read thru the wiki
you’re getting close. Make sure to read the wiki about Simple Modules modules. There is also good info in Horizontal vs Vertical Scaling. To troubleshoot these issues you can always ssh into the instance, cd into the tmp scan working directory and try running the command manually once on a remote instance. Also running |
|
@0xtavian As you said, I changed the ext from The result is saved in different files in a directory but that's totally fine. I really appreciate all your assistance. Our conversation went on for a while, but I'm so happy we got it to work :) Thanks a bunch for this awesome tool – it's the heart of my workflow! ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well I know the issue is with Interlace and not Axiom but I am opening the issue here as well so you can keep track of it.
Here I used my custom axiom module that works okay if the input file have less data/urls but when the list is huge (here it was 13 MB file with 143190 urls) it breaks and the Interlace gives me this error
IndexError: string index out of rangeThe text was updated successfully, but these errors were encountered: