On Jan 19, 2012, at 3:24 PM, Paul Hoffman wrote: > On Thu, Jan 19, 2012 at 11:16 AM, Jeff Forcier <[email protected]> wrote: >> N.B. This only impacts *connection* failures and not *authentication* >> errors (meaning passwords, bad host keys, etc.) Actual "wrong >> password" errors should already allow you at least 3 tries to >> re-enter, FWIW. > > I understand the design here, but it really doesn't work well for > systems that are supposed to be automated with no user watching. In > such cases, "cannot connect" and "cannot log in with the set of > credentials given in the program" have exactly the same impact, and > would hopefully be able to be treated the same. Fortunately, wrapping > in try/except catches both anyway. But, please do consider making > unattended programs using Fabric as useful as those where someone has > the ability to type a different password. > > --Paul Hoffman
Another great feature I'm looking forward to in fab 1.4 is better SSH Agent support(!!) Side note: For automated systems you should strongly consider using SSH keys instead of passwords for SSH logins. _______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
