possible user lockout with a hypothetical openconnect wrapper

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




25.06.2018 22:49, David Woodhouse ?????:
> On Mon, 2018-06-25 at 20:35 +0300, Basin Ilya wrote:
>>
>> Yeah, but in this case the the exit code of the second stage is
>> useless. What really important is to know the reason why `openconnect
>> --authenticate` failed.
> 
> The second stage should exit with code 2 if the cookie was invalid. In
> which case you use 'openconnect --authenticate' to get a new one. If it
> exits with anything other than 2 you just spawn it again.
> 
David try to understand. I don't have a cookie yet. In both cases (wrong password or a network issue) the first stage will exit with code 1. The wrapper should decide whether to prompt for a new password or to retry.



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux