Using my bank, https://www.scotiaonline.scotiabank.com/ I think I could manage this easy enough. It requires entering my card number, password (in oddly named fields, which change every time you visit, probably to defeat browser caching.. they seem security concious). Submit the form, it gives me some sorta session, redirects me once or twice, then shows my info. A scrape of that screen, would tell me all I needed to know (unless something was out of wack, then I'd check the odd seeming accounts transaction list) So, in summary, what you'd need to do to access my bank:

Contact the site, find the form fields, store the cookies. Replace certain form values with card/pass, leave the rest alone, but note them since you'll need to send them.

Know that the first field is card number, second is password.

Send a post. (with the proper info)

read/accept/submit all cookies through the 2-3 redirects it does.

scrape the page for the data you want.

Then again, I am kinda glad my bank seems to take security seriously, and it would be difficult to 'scrape' automatically. If it was easy to scrape, it'd be easy to do all sorts of things

Then again, bank of america, seems to use a static field to login, it should be fairly easy to deal with something like that automatically. It should be fairly easy for the less scrupulous people to break in as well, since all they have to do is get into your machine, and check your browsers auto-complete data.

---

In reply to Re: Quest: a bulletproof-secure, automated scraper by cowboy
in thread Quest: a bulletproof-secure, automated scraper by tlm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or or How to display code and escape characters are good places to start.