From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] amazon
Date: Wed, 27 Sep 2017 20:45:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709272014310.32591@carhart.net> (raw)
In-Reply-To: <20170827064819.eklhad@comcast.net>
> Instead of try catch I created the style object, if it was missing, and also log that it is not there.
Thank you.. the homepage of amazon now reports no errors at all!
The login page still reports a couple. Logging in doesn't work yet.
There's something quite remarkable.........
If you want to experience this for yourself, do this..
b http://amazon.com
11
{the line with the login link}
demin
g2
{Now the login page is loaded}
jdb
showscripts()
{scripts[9] is the big one. either echo document.scripts[9].data or export
it to a file}
This code, called fwcim._CB516154953_.js, is impressively obfuscated. Not
something you run across every day. I hope we will be able to just point
edbrowse at it and will not need to think about its inner workings, unless
anyone knows about deobfuscation or has the appetite for a huge
substitution cipher:
var _z2sz = function (_Zs$2, _iLLLl, _111LI) {
var _ooO0O = [
'FwcimObfusca',
'nod',
'te',
'hBStatement',
'has',
'e',
39801
];
var _ZS$2z = _ooO0O[1] + _ooO0O[5] +
(_ooO0O[0] + _ooO0O[2]), _2szSs = _ooO0O[6];
There is more to do here.. I've just been reading a blog post by Ricky
Lalwani, who has succesfully done just what we are trying to do. The
problem involves an http request variable called 'metadata1', which is
generated on the fly. And a remarkable amount of work goes in to building
this thing.
https://ricky.lalwani.me/programming/logging-in-to-amazon-part-2/
So the good news is that others have tried to log in to amazon over http
tools. The bad news is that it appears to be an industrial strength
challenge..
next prev parent reply other threads:[~2017-09-28 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 4:01 [Edbrowse-dev] how about wrapping style placement in try-catch? Kevin Carhart
2017-09-27 10:48 ` Karl Dahlke
2017-09-28 3:45 ` Kevin Carhart [this message]
2017-09-28 4:58 ` [Edbrowse-dev] amazon Karl Dahlke
2017-09-28 6:45 ` Kevin Carhart
2017-09-28 3:48 ` [Edbrowse-dev] how about wrapping style placement in try-catch? Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.03.1709272014310.32591@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).