[Buildroot] dropbear permission denied

[Buildroot] dropbear permission denied

[Belisko Marek]

Hi,

second time I'm using dropbear for embedded project and again same troubles ;)
(and cannot remember how to resolve it first time). I compile
buildroot with dropbear support.
Booting board keys was generated. Then want to copy some file from PC to board:
scp test.txt root@<IP>:/home/defaut and result is:
Permission denied, please try again.

What I'm doing wrong? Is there anything I'm missing? Must root user have passwd
to make dropbear working (try it but it doesn't work)?

Thanks for replies.

Cheers,

mbe


-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

[Buildroot] dropbear permission denied

[Dirk Lohse]

Hi,

ssh/dropbear doesn't work without password (right?). I've created a password for root and it works. If not - maybe there is another problem. When target-fs is mounted read-only you should get another failure.

Dirk


-----Urspr?ngliche Nachricht-----
Von: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] Im Auftrag von Belisko Marek
Gesendet: Donnerstag, 23. August 2012 21:01
An: buildroot at uclibc.org
Betreff: [Buildroot] dropbear permission denied

Hi,

second time I'm using dropbear for embedded project and again same troubles ;)
(and cannot remember how to resolve it first time). I compile
buildroot with dropbear support.
Booting board keys was generated. Then want to copy some file from PC to board:
scp test.txt root@<IP>:/home/defaut and result is:
Permission denied, please try again.

What I'm doing wrong? Is there anything I'm missing? Must root user have passwd
to make dropbear working (try it but it doesn't work)?

Thanks for replies.

Cheers,

mbe


-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] dropbear permission denied

[Thomas Petazzoni]

Le Fri, 24 Aug 2012 08:56:32 +0200,
"Dirk Lohse" <d.lohse@meier-nt.de> a ?crit :

> ssh/dropbear doesn't work without password (right?). I've created a
> password for root and it works. If not - maybe there is another
> problem. When target-fs is mounted read-only you should get another
> failure.

Correct. dropbear doesn't allow login into accounts that have an empty
password.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] dropbear permission denied

[Belisko Marek]

On Fri, Aug 24, 2012 at 1:53 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Fri, 24 Aug 2012 08:56:32 +0200,
> "Dirk Lohse" <d.lohse@meier-nt.de> a ?crit :
>
>> ssh/dropbear doesn't work without password (right?). I've created a
>> password for root and it works. If not - maybe there is another
>> problem. When target-fs is mounted read-only you should get another
>> failure.
>
> Correct. dropbear doesn't allow login into accounts that have an empty
> password.
Is there any way in e.g. post-processing to set some passwd (maybe empty) for
root user to avoid such troubles? Anybody using it that way?
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com

thanks,

mbe

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

[Buildroot] dropbear permission denied

[Kevin Chadwick]

> scp test.txt root@<IP>:/home/defaut and result is:
> Permission denied, please try again.
> 
> What I'm doing wrong? Is there anything I'm missing?

Are you sure /home/defaut exists.

I know less about dropbear but with openssh you need extra things like
ttys for scp, that you do not need for sftp.

-- 
_______________________________________________________________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
_______________________________________________________________________

[Buildroot] dropbear permission denied

[Thomas Petazzoni]

Le Fri, 24 Aug 2012 16:31:38 +0200,
Belisko Marek <marek.belisko@gmail.com> a ?crit :

> > Correct. dropbear doesn't allow login into accounts that have an
> > empty password.
> Is there any way in e.g. post-processing to set some passwd (maybe
> empty) for root user to avoid such troubles? Anybody using it that
> way?

See http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
slide 25. You can use the post-build script mechanism to tune
the /etc/passwd file to set a root password.

I once thought of adding a Kconfig option for that, but it would mean
that the root password would be stored as clear text in the .config
file, which probably isn't that nice.

Should we make the default 'root' password be 'root' so that it is
non-empty and it works with Dropbear? Or simply add a FAQ entry
which explains this problem? Other ideas?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] dropbear permission denied

[Dmitry Golubovsky]

Hi,

Thomas Petazzoni wrote:

> Should we make the default 'root' password be 'root' so that it is
> non-empty and it works with Dropbear? Or simply add a FAQ entry
> which explains this problem? Other ideas?

Not being much familiar with Dropbear, I'm wondering if it supports
PAM [1]? If it does, can it work with a similar PAM config file like I
am supplying* with Busybox for login i. e.

auth      required       pam_unix.so nullok
account   required       pam_unix.so nullok
password  required       pam_unix.so nullok
session   required       pam_unix.so nullok

with such PAM config file zero-length passwords are allowed. Busybox
login works this way for users `default' and `root' but not for any
other username.

[1] http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2010q3/001053.html

* In a patch I submitted some time earlier, but it hasn't been
committed  yet:
http://lists.busybox.net/pipermail/buildroot/2012-August/057490.html

Thanks.
-- 
Dmitry Golubovsky

Anywhere on the Web

[Buildroot] dropbear permission denied

[Dirk Lohse]

I would prefer to set root-password "root" as default - so that dropbear works.

But would this bring up questions like "what is the default password"?

Dirk

-----Urspr?ngliche Nachricht-----
Von: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com] 
Gesendet: Freitag, 24. August 2012 19:46
An: Belisko Marek
Cc: Dirk Lohse; buildroot at uclibc.org; buildroot at busybox.net
Betreff: Re: [Buildroot] dropbear permission denied

Le Fri, 24 Aug 2012 16:31:38 +0200,
Belisko Marek <marek.belisko@gmail.com> a ?crit :

> > Correct. dropbear doesn't allow login into accounts that have an
> > empty password.
> Is there any way in e.g. post-processing to set some passwd (maybe
> empty) for root user to avoid such troubles? Anybody using it that
> way?

See http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
slide 25. You can use the post-build script mechanism to tune
the /etc/passwd file to set a root password.

I once thought of adding a Kconfig option for that, but it would mean
that the root password would be stored as clear text in the .config
file, which probably isn't that nice.

Should we make the default 'root' password be 'root' so that it is
non-empty and it works with Dropbear? Or simply add a FAQ entry
which explains this problem? Other ideas?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] dropbear permission denied

[Stephan Hoffmann]

Am 27.08.2012 08:37, schrieb Dirk Lohse:
> I would prefer to set root-password "root" as default - so that dropbear works.
I would also opt for a default password.
> But would this bring up questions like "what is the default password"?
This could be mentioned in the "Welcome"-message.

Kind regards

Stephan
> Dirk
>
> -----Urspr?ngliche Nachricht-----
> Von: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com] 
> Gesendet: Freitag, 24. August 2012 19:46
> An: Belisko Marek
> Cc: Dirk Lohse; buildroot at uclibc.org; buildroot at busybox.net
> Betreff: Re: [Buildroot] dropbear permission denied
>
> Le Fri, 24 Aug 2012 16:31:38 +0200,
> Belisko Marek <marek.belisko@gmail.com> a ?crit :
>
>>> Correct. dropbear doesn't allow login into accounts that have an
>>> empty password.
>> Is there any way in e.g. post-processing to set some passwd (maybe
>> empty) for root user to avoid such troubles? Anybody using it that
>> way?
> See http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
> slide 25. You can use the post-build script mechanism to tune
> the /etc/passwd file to set a root password.
>
> I once thought of adding a Kconfig option for that, but it would mean
> that the root password would be stored as clear text in the .config
> file, which probably isn't that nice.
>
> Should we make the default 'root' password be 'root' so that it is
> non-empty and it works with Dropbear? Or simply add a FAQ entry
> which explains this problem? Other ideas?
>
> Best regards,
>
> Thomas


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

[Buildroot] dropbear permission denied

[Belisko Marek]

On Fri, Aug 24, 2012 at 7:31 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Fri, 24 Aug 2012 16:31:38 +0200,
> Belisko Marek <marek.belisko@gmail.com> a ?crit :
>
>> > Correct. dropbear doesn't allow login into accounts that have an
>> > empty password.
>> Is there any way in e.g. post-processing to set some passwd (maybe
>> empty) for root user to avoid such troubles? Anybody using it that
>> way?
>
> See http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
> slide 25. You can use the post-build script mechanism to tune
> the /etc/passwd file to set a root password.
Thanks for link.
>
> I once thought of adding a Kconfig option for that, but it would mean
> that the root password would be stored as clear text in the .config
> file, which probably isn't that nice.
>
> Should we make the default 'root' password be 'root' so that it is
> non-empty and it works with Dropbear? Or simply add a FAQ entry
> which explains this problem? Other ideas?
As I read http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
it's really easy to do it in post-build script. IMO adding to FAQ with
simple example
could solve dropbear problems.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com

Cheers,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

[Buildroot] dropbear permission denied

[Kevin Chadwick]

> Or simply add a FAQ entry
> which explains this problem? Other ideas?

Is it easy to add an entry into a readme file packaged with dropbear.

-- 
_______________________________________________________________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
_______________________________________________________________________