Issue 86: History extraction POC from Michael Zalewski (Working for IE and Firefox) #638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Java() from /beef/core/main/client/net/local.js
…Java() from /beef/core/main/client/net/local.js
Issue 86 - Working for Firefox. Support for Chrome+Opera+IE still pending.
…oth Firefox and IE
|
This pull request includes changes for Issue 86 and Issue 639 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Module has been implemented for both IE and Firefox.
POC http://lcamtuf.coredump.cx/cachetime/chrome.html did not work well for me.
It seems that the number of links referenced under targets variable is not being used by Chrome when accessing sites like Facebook.
I will have to determine the list of css and js files that are cached by Chrome by accessing the sites like Facebook, etc