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
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
25.06.2018 13:18, David Woodhouse пишет:
> On Mon, 2018-06-25 at 12:32 +0300, Basin Ilya wrote:
>> Hi.
>> I'm trying to make a wrapper for Openconnect that uses its own
>> password manager. The wrapper should relaunch Openconnect infinitely,
>> when it fails to connect (possibly due to a temporary
On 25 June 2018 at 15:15, Daniel Lenski wrote:
> On Mon, Jun 25, 2018 at 12:12 PM, Jeroen Balduyck
> wrote:
>> Hi Dan,
>>
>> I *think* I figured it out. Hopefully this post will make it to the
>> list (my other one for this topic is under moderation). I'm using the
>> info from this document:
>>
On Mon, Jun 25, 2018 at 12:12 PM, Jeroen Balduyck
wrote:
> Hi Dan,
>
> I *think* I figured it out. Hopefully this post will make it to the
> list (my other one for this topic is under moderation). I'm using the
> info from this document:
>
On Mon, 2018-06-25 at 12:32 +0300, Basin Ilya wrote:
> Hi.
> I'm trying to make a wrapper for Openconnect that uses its own
> password manager. The wrapper should relaunch Openconnect infinitely,
> when it fails to connect (possibly due to a temporary network
> problem), but it shouldn't when the
Hi.
I'm trying to make a wrapper for Openconnect that uses its own password
manager. The wrapper should relaunch Openconnect infinitely, when it fails to
connect (possibly due to a temporary network problem), but it shouldn't when
the password is bad to avoid a user lockout.
How can the
On 25 June 2018 at 10:34, Daniel Lenski wrote:
> On Sat, Jun 23, 2018 at 12:22 PM, Jeroen Balduyck
> wrote:
>> Hi
>>
>> I've been struggling to get this option to work. Wireshark reports
>> this cipher in the server hello:
>> Cipher Suite: TLS_PSK_WITH_AES_256_GCM_SHA384 (0x00a9)
>
> Are you
On Sat, Jun 23, 2018 at 12:22 PM, Jeroen Balduyck
wrote:
> Hi
>
> I've been struggling to get this option to work. Wireshark reports
> this cipher in the server hello:
> Cipher Suite: TLS_PSK_WITH_AES_256_GCM_SHA384 (0x00a9)
Are you sure that the server supports this ciphersuite for *DTLS*, as
