Maybe patch around this change
http://sourceforge.net/p/sshpass/code/48/tree//trunk/main.c?diff=5182883de88f3d77deda7b5c:47
similarly to what was done in the Salt issue
https://github.com/saltstack/salt/pull/22120/files
--Nikolay
On Tue, Nov 24, 2015 at 1:05 AM, Adam Vande More <amvandemore at
gmail.com> wrote:> sshpass seems to be broken for at least FreeBSD 10.X targets and here is
> some debugging output:
>
> 6347: 0.306948550 write(2,"debug2:
input_userauth_info_req:"...,48) = 48
> (0x30)
> 6347: 0.307046901
> openat(0xffffff9c,0x8008a4fe6,0x2,0x0,0x7ff7fc75ecfc,0x803856010) ERR#6
> 'Device not configured'
> debug1: read_passphrase: can't open /dev/tty: Device not configured
> 6347: 0.307174637 write(2,"debug1: read_passphrase: can't
o"...,69) = 69
> (0x45)
> 6347: 0.307292478 open("/dev/tty",O_RDWR|O_CLOEXEC,0163727160)
ERR#6
> 'Device not configured'
> debug3: packet_send2: adding 48 (len 10 padlen 6 extra_pad 64)
> 6347: 0.307424012 write(2,"debug3: packet_send2: adding 48
"...,64) = 64
> (0x40)
>
> It seems various tools like ansible and salt are running into this as well:
>
> https://github.com/saltstack/salt/issues/20565
> https://github.com/ansible/ansible/issues/11565
> http://sourceforge.net/p/sshpass/bugs/12/ <- Misidentified cause
>
> Can anyone offer insight into this?
>
> Thanks,
>
> --
> Adam
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"