Displaying 20 results from an estimated 2000 matches similar to: "[Bug 3680] New: Wrong destination in case of dropbear server"
2011 Sep 30
2
Interop problem with old dropbear and new openssh
Hi,
I have a router running an old version of OpenWRT with an old version of
dropbear (Dropbear sshd v0.44test3). It has been working for many years and I
ssh in from my desktop systems (running Debian Testing) with no problem.
However, recently I upgraded one of my desktops and I can no longer connect to
the router. Dropbear on the router is exiting with:
exit before auth: bad
2024 Sep 29
1
Bug: ssh-copy-id mishandles dropbear
Am So., 29. Sept. 2024 um 00:20 Uhr schrieb <piticu.pulii at gmail.com>:
>
> On Fri, Sep 27, 2024 at 04:35:22PM +0200, Norbert Lange wrote:
> > ssh-copy-id has special handling for dropbear, but this seems to be
> > quite out of date (or forever wrong).
> > I dont see dropbear ever accessing `/etc/dropbear/authorized_keys`,
> > and I don't see any hints this
2007 May 21
2
Using Dropbear for RTOS which is not POSIX complaint?
Hi,
We have a proprietary RTOS which is *not* POSIX complaint. We want to port
SSH server and SCP client onto our platform. How difficult it would be, to
port Dropbear into our platform? We would like to integrate our CLI with the
SSH.
Any recommendations on using Dropbear for our platform? Appreciate sharing
your experiences with Dropbear.
---
Thanks,
Mohan
2023 Jan 23
7
[Bug 3527] New: ssh-copy-id broken for dropbear
https://bugzilla.mindrot.org/show_bug.cgi?id=3527
Bug ID: 3527
Summary: ssh-copy-id broken for dropbear
Product: Portable OpenSSH
Version: 9.1p1
Hardware: Other
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: ssh-copy-id
Assignee: unassigned-bugs at mindrot.org
2014 Apr 18
3
[Bug 2233] New: curve25519-sha256@libssh.org Signature Failures When 'sshd' Used with Dropbear Clients
https://bugzilla.mindrot.org/show_bug.cgi?id=2233
Bug ID: 2233
Summary: curve25519-sha256 at libssh.org Signature Failures When
'sshd' Used with Dropbear Clients
Product: Portable OpenSSH
Version: 6.6p1
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
2015 Jan 29
2
Tinc and OpenWRT
On Tue, Jan 27, 2015, Sandy McArthur Jr wrote:
> I use the Tinc 1.0 series since I don't want to support my
> own packages. <snip>
> I wrote most of http://wiki.openwrt.org/doc/howto/vpn.tinc and that is
> what I still use. Since then . . .
Ok. I think I'll start with the 1.0 series packages that are already
out there and get them working.
and on Tue, Jan 27, 2015,
2018 Nov 23
2
Debian Stretch 9.6: openssh-server and old dropbear client don't work togheter
Il giorno gio 22 nov 2018 alle ore 21:24 Stuart Henderson
<stu at spacehopper.org> ha scritto:
>
> On 2018/11/22 19:55, owl700 at gmail.com wrote:
> > Hi, I have compatibility issues with the latest version of
> > openssh-server and an old dropbear client, the dopbear client stops at
> > preauth
> >
> > ov 22 14:34:03 myhostname sshd[3905]: debug1: Client
2015 Jun 13
2
Tinc and OpenWRT
Hey Saverio,
I'd really like the idea of a tinc-1.1-pre package for OpenWRT. I'm
currently using tinc-1.1 with an Ed25519-only network, really like the
new features and CLI and want to add some OpenWRT routers into the mix.
How do you plan to handle things with OpenSSL?
tinc-1.1 from git should be able to compile without it (but will then
only support the built-in algorithms). Depending
2018 Nov 22
2
Debian Stretch 9.6: openssh-server and old dropbear client don't work togheter
Hi, I have compatibility issues with the latest version of
openssh-server and an old dropbear client, the dopbear client stops at
preauth
ov 22 14:34:03 myhostname sshd[3905]: debug1: Client protocol version
2.0; client software version dropbear_0.46
Nov 22 14:34:03 myhostname sshd[3905]: debug1: no match: dropbear_0.46
Nov 22 14:34:03 myhostname sshd[3905]: debug1: Local version string
2014 Apr 18
2
[Bug 2232] New: curve25519-sha256@libssh.org Signature Failures When 'ssh' Used with Dropbear, libssh Servers
https://bugzilla.mindrot.org/show_bug.cgi?id=2232
Bug ID: 2232
Summary: curve25519-sha256 at libssh.org Signature Failures When
'ssh' Used with Dropbear, libssh Servers
Product: Portable OpenSSH
Version: 6.6p1
Hardware: All
OS: All
Status: NEW
Severity: major
2024 Sep 27
0
Bug: ssh-copy-id mishandles dropbear
Hello,
ssh-copy-id has special handling for dropbear, but this seems to be
quite out of date (or forever wrong).
I dont see dropbear ever accessing `/etc/dropbear/authorized_keys`,
and I don't see any hints this ever was the case.
dropbear uses ~/.ssh/authorized_keys just like OpenSSH, so the special
handling needs to go.
regards, Norbert
2015 Jan 26
3
Tinc and OpenWRT
Greetings.
I'm new to tinc, but have so far managed to get a couple laptops and a
hosted server all connected. They're working as expected, running
Tinc 1.1-pre11, which I compiled from source.
Next I want to move on to adding my home router into the mix. My
routers run OpenWRT. I don't have experience compiling anything from
source for OpenWRT, but OpenWRT has Tinc 1.0.25
2015 Jan 29
1
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote:
>
> Hi,
>
> On Thu, 29 Jan 2015 11:11:32 +1100
> David Gibson <david at gibson.dropbear.id.au> wrote:
>
> > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote:
> > > On Thu, 22 Jan 2015 12:43:43 +1100
> > > David Gibson <david at gibson.dropbear.id.au> wrote:
> >
2015 Jan 29
1
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote:
>
> Hi,
>
> On Thu, 29 Jan 2015 11:11:32 +1100
> David Gibson <david at gibson.dropbear.id.au> wrote:
>
> > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote:
> > > On Thu, 22 Jan 2015 12:43:43 +1100
> > > David Gibson <david at gibson.dropbear.id.au> wrote:
> >
2015 Jan 29
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote:
> On Thu, 22 Jan 2015 12:43:43 +1100
> David Gibson <david at gibson.dropbear.id.au> wrote:
>
> > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote:
> > > With virtio-1, we support more than 32 feature bits. Let's extend both
> > > host and guest features to 64, which should
2015 Jan 29
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote:
> On Thu, 22 Jan 2015 12:43:43 +1100
> David Gibson <david at gibson.dropbear.id.au> wrote:
>
> > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote:
> > > With virtio-1, we support more than 32 feature bits. Let's extend both
> > > host and guest features to 64, which should
2015 Jun 15
1
Tinc and OpenWRT
I already have a package made, if anyone would like me to I could submit it.
On 2015-06-13 17:26, Florian Klink wrote:
> Hey Saverio,
>
> I'd really like the idea of a tinc-1.1-pre package for OpenWRT. I'm
> currently using tinc-1.1 with an Ed25519-only network, really like the
> new features and CLI and want to add some OpenWRT routers into the mix.
>
> How do you
2015 Jan 22
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote:
> With virtio-1, we support more than 32 feature bits. Let's extend both
> host and guest features to 64, which should suffice for a while.
>
> vhost and migration have been ignored for now.
[snip]
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index f6c0379..08141c7 100644
> ---
2015 Jan 22
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote:
> With virtio-1, we support more than 32 feature bits. Let's extend both
> host and guest features to 64, which should suffice for a while.
>
> vhost and migration have been ignored for now.
[snip]
> diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h
> index f6c0379..08141c7 100644
> ---
2019 Oct 14
3
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
On Fri, Oct 11, 2019 at 06:25:18PM -0700, Ram Pai wrote:
> From: Thiago Jung Bauermann <bauerman at linux.ibm.com>
>
> In order to safely use the DMA API, virtio needs to know whether DMA
> addresses are in fact physical addresses and for that purpose,
> dma_addr_is_phys_addr() is introduced.
>
> cc: Benjamin Herrenschmidt <benh at kernel.crashing.org>
> cc: