On Tue, 16 Jun 2020 20:08:17 -0700 John Ralls <jra...@ceridwen.us> wrote:
> I think the only really feasible workaround is to reverse-engineer > the Web Connect authentication. That would mean installing Quicken > and setting up and using OFX Web Connect while monitoring the traffic > with wireshark. > https://redflagsecurity.net/2019/03/10/decrypting-tls-wireshark/ > might be helpful for decrypting the authentication traffic with the > browser. No doubt the quicken connection will also be encrypted so > you'll need to find the keys for that too to be able to interpret the > traffic--and working out the key exchange between Quicken and the > bank will also be necessary. Frankly I would expect a low probability > of success without help from a crypto expert. Reminds me of doing that once to switch a fragile windows client into a robust system running on another OS. When I got the code using wireshark, it was " 1 2 3 4" Liz _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
