Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian <bastisoft@arcor.de>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for powerpc, no prompt + OpenSSH login
Date: Thu, 21 Jan 2010 16:57:13 +0100	[thread overview]
Message-ID: <4B587959.60804@arcor.de> (raw)
In-Reply-To: <8798648820214450AE9B59CC54232F14@gentiane>

Hello,

as far as I know SSH logins are not allowed unless there is a password 
set. To not show the attacker that there is no password, the prompt is 
still shown.

To connect through SSH, you need to set a password (passwd). Then it 
should work. Preferably use another user and "su" to do administration.

Hope this helps,

Sebastian

> My bad ! I checked "generic serial port config", but forgot to select 
> "ttyUL0" ;-P...
> Thank you for your help.
> 
> Anyway, my second problem still doesn't work, can you help me with that?
> I re-explain here:
> 
> When I try the to connect to the OpenSSH of my card, it does ask me for 
> a password.
> But root user doesn't have a password, I can login without it.
> 
> How to do? Should I connect with a different user? Is there a default 
> password for SSH?
> 
> Thank you.
> 

  parent reply	other threads:[~2010-01-21 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 14:29 [Buildroot] Buildroot for powerpc, no prompt + OpenSSH login Clément Foucher
2010-01-21 14:43 ` Daniel Mack
2010-01-21 15:49   ` Clément Foucher
2010-01-21 15:54     ` Daniel Mack
2010-01-21 16:23       ` Clement.FOUCHER at unice.fr
2010-01-21 16:58         ` [Buildroot] Usbmount - can't get it to work Will Moore
2010-01-21 15:57     ` Sebastian [this message]
2010-01-21 16:21       ` [Buildroot] Buildroot for powerpc, no prompt + OpenSSH login Clement.FOUCHER at unice.fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B587959.60804@arcor.de \
    --to=bastisoft@arcor.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox