For anyone that doesn't want to maintain a fork of chromium, just download the PDB and hook it at runtime for spoofing and/or dumping call logs. For hook itself just add your dll as a dependency in the PE structure.
Show HN: I'm building a browser for reverse engineers
31–40 of 58 posts
Re: Show HN: I'm building a browser for reverse engineers
#32Re: Show HN: I'm building a browser for reverse engineers
#33Re: Show HN: I'm building a browser for reverse engineers
#34For anyone that doesn't want to maintain a fork of chromium, just download the PDB and hook it at runtime for spoofing and/or dumping call logs. For hook itself just add your dll as a dependency in the PE structure.
That sounds like a Windows-only approach though.
Re: Show HN: I'm building a browser for reverse engineers
#35resworb nwo ym detnaw syawla ev'i dna reenigne esrever a m'I
Re: Show HN: I'm building a browser for reverse engineers
#36Re: Show HN: I'm building a browser for reverse engineers
#37Re: Show HN: I'm building a browser for reverse engineers
#38Re: Show HN: I'm building a browser for reverse engineers
#39Earlier quoted context omitted.
To note, there are undocumented detections to even Proxys, for example using `in` operator in v8 (such as `proxiedFunc in 1` for some proxied function). Really cool to see a project like this.
How do you use `in` in v8 to detect proxies? I assume its a difference in the exception, but the message and the cause were the same in both direct and proxied `x in 1`.
Re: Show HN: I'm building a browser for reverse engineers
#40Build times were way longer on my potato hardware. Since then I haven't touched much C++.