possible user lockout with a hypothetical openconnect wrapper

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

 



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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5213 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20180625/ecb0df9e/attachment.bin>


[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