30.11.2015, 16:58, "Matt Johnston" :
> On Mon, Nov 30, 2015 at 04:21:29PM +0300, Konstantin Tokarev wrote:
>> >> I'd like to see that as a feature - I was thinking about it a few days
>> ago. I'd keep it under a command line flag for backwards compatibility.
>> Failing to
> On Mon 30/11/2015, at 6:29 am, Anthony Sherwin
> wrote:
>
> I have cross compiled dropbear to my embedded product from 2015.68 to 2015.70
> and am getting the following error:
> dropbear[2528]: Exit (user): Bad buf_incrpos
Hi Anthony,
This should be
> On Mon 30/11/2015, at 7:24 pm, Konstantin Tokarev wrote:
> dbclient: Remote TCP forward request failed (port 3320 -> localhost:22)
>
> ...
> 1. Is there any way to force dbclient to exit in this case?
> 2. If not, would it be reasonable feature to have in dbclient?
Hi
Hi all,
I think it would be useful to have syslog loggin in client when it is running
in background (e.g., when -f option is used, or, like in my case, it is started
from init system to create tunnel).
Would such contribution be welcome?
--
Regards,
Konstantin
30.11.2015, 15:36, "Matt Johnston" :
>> On Mon 30/11/2015, at 6:29 am, Anthony Sherwin
>> wrote:
>>
>> I have cross compiled dropbear to my embedded product from 2015.68 to
>> 2015.70 and am getting the following error:
>>
>>
30.11.2015, 15:39, "Matt Johnston" :
>> On Mon 30/11/2015, at 7:24 pm, Konstantin Tokarev wrote:
>> dbclient: Remote TCP forward request failed (port 3320 -> localhost:22)
>>
>> ...
>> 1. Is there any way to force dbclient to exit in this case?
>> 2. If
> On Mon 30/11/2015, at 8:38 pm, Konstantin Tokarev wrote:
>
> Hi all,
>
> I think it would be useful to have syslog loggin in client when it is running
> in background (e.g., when -f option is used, or, like in my case, it is
> started from init system to create tunnel).
>