You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When exporting wordlists and precracked can you have them go into the import folder rather than direct to the files folder. This way they are available for import directly into other hashlists or are ready to be imported for use in other crack jobs.
When they go direct to files they don't go into the database and the webui isn't ready to use them for a direct import into another job
The text was updated successfully, but these errors were encountered:
Does it really make sense to export it to the import folder? Because there it cannot be downloaded from, so it would need to be imported as a file first and then it can be downloaded.
I know, maybe that's not the ideal solution for you, but generally a direct download would be better I think. So in case you export something, you want to have it downloaded.
There are certain cases where selecting the output location of any export function (export of cracks, left lists, wordlists etc.) would be handy, ideally being able to select files, the import dir or [files+insert into the files db].
Please modify all areas where exports are possible to select the output location (import, files dir, or files dir + insert into the files db] and enable via the user-api
With this still open I would suggest exporting the founds to the "Other" tab or offering a download function. As of right now I am opening the list and copy/pasting the founds into a txt document.
zyronix
changed the title
Change export behavior
[ENHANCEMENT] Change file export behavior
Jun 16, 2023
When exporting wordlists and precracked can you have them go into the import folder rather than direct to the files folder. This way they are available for import directly into other hashlists or are ready to be imported for use in other crack jobs.
When they go direct to files they don't go into the database and the webui isn't ready to use them for a direct import into another job
The text was updated successfully, but these errors were encountered: