Wells Fargo Bank changes

[Jimmy Crossley]

> -----Original Message-----
> From: gnucash-user-bounces+jcrossley=conetrix.com at gnucash.org [mailto:gnucash-user-
> bounces+jcrossley=conetrix.com at gnucash.org] On Behalf Of Liz
> Sent: Saturday, November 26, 2011 15:35
> To: gnucash-user at gnucash.org
> Subject: Re: Wells Fargo Bank changes
> 
> On Sat, 26 Nov 2011 12:43:30 -0600
> Jimmy Crossley <jcrossley at conetrix.com> wrote:
> 
> > I used to use Quicken long ago before I discovered gnucash.
> snip
> >
> > Action required for your Quicken(r) or QuickBooks(r) account
> > Wells Fargo has moved to a new system supporting Quicken and
> > QuickBooks users. Please make changes within your software by
> > November 30, 2011 to avoid having your service discontinued and all
> > pending bill payments automatically canceled on December 7, 2011.
> another snip
> >
> > We hope you will enjoy the new benefits included in the service:
> another snip
> > *       The same username and password for Quicken or QuickBooks and
> > Wells Fargo Online banking.
> >
> 
> well that makes a big security problem to me.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

I think the changes are adding more security because Quicken (and gnucash) used to use a 4 digit PIN.  Now the longer, more secure password is used.  Here are the requirements for the password:

    Must be 6 to 14 characters.
    Must contain at least one letter and one number.
    May not repeat the same number or letter more than 3 times in a row.
    May not contain more than 3 sequential numbers or letters (such as '1234' or 'abcd') in a row.
    May contain special characters (such as @, %, &, #).

>From https://online.wellsfargo.com/das/channel/helpText?key=fieldhelp_PasswordCreation

This e-mail message (and attachments) may contain confidential information.  Then again, it may not.