Re: Dropbear 2018.76 when behaving as client sending sha1 as mac

2019-04-11 Thread Matt Johnston
9 > To: Chahar, Rohini <mailto:rohini.cha...@netscout.com>> > Cc: dropbear@ucc.asn.au <mailto:dropbear@ucc.asn.au> > Subject: Re: Dropbear 2018.76 when behaving as client sending sha1 as mac > > [EXTERNAL EMAIL] > Hi Rohini, > > I'm not entirely clear about

RE: Dropbear 2018.76 when behaving as client sending sha1 as mac

2019-04-10 Thread Chahar, Rohini
Hi Matt, Please find my responses below. Regards, Rohini From: Matt Johnston Sent: 10 April 2019 18:39 To: Chahar, Rohini Cc: dropbear@ucc.asn.au Subject: Re: Dropbear 2018.76 when behaving as client sending sha1 as mac [EXTERNAL EMAIL] Hi Rohini, I'm not entirely clear about the problem

Re: Dropbear 2018.76 when behaving as client sending sha1 as mac

2019-04-10 Thread Matt Johnston
Hi Rohini, I'm not entirely clear about the problem - is the conneciton failing or is it just selecting hmac-sha2-sha1 which you don't want? The algorithm chosen will be the first one in the client's list that is also in the server's list. When you do the "copy to the server" is it dropbear as

Re: Dropbear 2018.76

2019-03-20 Thread Matt Johnston
Hi Warren, I think the current tree is ready to release, so hopefully in the next week. There are a few outstanding pull requests but on balance I think it's better that they wait for the next release - hopefully at a shorter interval. Cheers, Matt On Wed, Mar 20, 2019 at 12:53:55AM -0400,

Re: Dropbear 2018.76

2019-03-19 Thread Russell Warren
I've just run into this same problem. Any word on a new release to fix the numerous changes since 2018.76? Also, anyone care to jump in with a recommendation out of these options? 1. Continue to use 2017.75? 2. Use 2018.76 with the specified patch

[SUSPECTED SPAM]Re: Dropbear 2018.76

2018-03-09 Thread Peter Krefting
Matt Johnston: This should be fixed in https://secure.ucc.asn.au/hg/dropbear/rev/0dc3103a5900 This patch does indeed fix the problem. Thank you! -- \\// Peter - http://www.softwolves.pp.se/

Re: Dropbear 2018.76

2018-03-08 Thread Matt Johnston
Hi Peter, This should be fixed in https://secure.ucc.asn.au/hg/dropbear/rev/0dc3103a5900 Dropbear was advertising both the existing ecdsa size as well as the default size (for -R), but then the client chose the default size which didn't

Re: Dropbear 2018.76

2018-03-05 Thread Peter Krefting
Matt Johnston: Yes it should. I can't immediately reproduce it here, what flags are you giving to Dropbear? Is /mnt/nv/dropbear_ecdsa_host_key specified with -r or as a default config path, and are there other keyfiles? The daemon is started with "dropbear -R", and the keyfiles are specified

Re: Dropbear 2018.76

2018-03-02 Thread Steffen Nurpmeso
I want to point out that Konstantin Tokarev was Cc:d in my message, his name has been stripped by the ML. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert

Re: Dropbear 2018.76

2018-03-02 Thread Steffen Nurpmeso
Matt Johnston wrote: |On 2 March 2018 6:17:42 pm AWST, Konstantin Tokarev \ |wrote: |>02.03.2018, 00:18, "Steffen Nurpmeso" : |>>> ok?? Ok, so how about "-o ProxyLocalhost=PORT"? |> |>There is no such option in openssh | |I'm not

Re: Dropbear 2018.76

2018-03-02 Thread Konstantin Tokarev
02.03.2018, 00:18, "Steffen Nurpmeso" : > Hello Matt. > > Matt Johnston wrote: >  |> On Wed 28/2/2018, at 12:59 am, Steffen Nurpmeso \ >  |> wrote: >  |> And yes, i am still using such grumpy networks with VMs, so please >  |> let me

Re: Dropbear 2018.76

2018-03-01 Thread Matt Johnston
Hi Peter, On Thu, Mar 01, 2018 at 10:37:19AM +0100, Peter Krefting wrote: > After upgrading to 2018.76, I can no longer log in. On the dropbear end, it > complains about not being able to read the host key (/mnt/nv is the > non-volatile storage in my target HW): > > Mar 1 11:19:03 gbprobe

Re: Dropbear 2018.76

2018-02-28 Thread Matt Johnston
> On Wed 28/2/2018, at 12:59 am, Steffen Nurpmeso wrote: > And yes, i am still using such grumpy networks with VMs, so please > let me post the "git am" mailbox that adds support for proxy-over- > localhost. Hi Steffen, Thanks for the patch, though I'm not sure it's worth

Re: Dropbear 2018.76

2018-02-28 Thread Matt Johnston
> On Tue 27/2/2018, at 11:28 pm, Konstantin Tokarev wrote: >> >> - Add 'dbclient -J ' to allow dbclient to connect over an existing socket. >> See dbclient manpage for a socat example. Patch from Harald Becker > > Wouldn't it be better to support -o ProxyUseFdPass like in

Re: Dropbear 2018.76

2018-02-27 Thread Steffen Nurpmeso
Matt Johnston wrote: |Dropbear 2018.76 is released. As well as the usual Thank you! And yes, i am still using such grumpy networks with VMs, so please let me post the "git am" mailbox that adds support for proxy-over- localhost. Ciao, --steffen | |Der Kragenbaer,

Re: Dropbear 2018.76

2018-02-27 Thread Konstantin Tokarev
27.02.2018, 17:54, "Matt Johnston" : > Hi all, > > Dropbear 2018.76 is released. As well as the usual > improvements and bugfixes this release simplifies > local configuration options. > You will probably need to adjust your build configuration. > > Rather than modifying