Bug 182222 - can't use ssh/scp inside of anaconda and rescue mode
Summary: can't use ssh/scp inside of anaconda and rescue mode
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: FC5Blocker
TreeView+ depends on / blocked
 
Reported: 2006-02-21 05:21 UTC by Dax Kelson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-03 19:06:32 UTC
Type: ---


Attachments (Terms of Use)

Description Dax Kelson 2006-02-21 05:21:59 UTC
Description of problem:

When installing FC5 test releases or rawhide I've noticed that during the
install or inside of a rescue environment (very important!) I'm unable to use
ssh or scp.

It looks like this:

# scp localfile.txt 1.2.3.4:/tmp
Host key verication failed.
lost connection

Using verbose mode swich reveals this clue:

[snip a bunch of output]
debug1: read_passphrase: can't open /dev/tty: No such device or address
Host key verication failed.
lost connection

Comment 1 Jeremy Katz 2006-02-21 15:59:31 UTC
Hmm, it's working just fine for me with today's rawhide.  Does /dev/tty exist? 
What type of hardware and what install type are you using?

Comment 2 Dax Kelson 2006-02-21 16:39:30 UTC
Did you try the rescue mode?

/dev/tty did exist

I was installing 32bit FC5test3 on AMD64 hardware.

Comment 3 Jeremy Katz 2006-02-22 21:12:01 UTC
Aha, it's only a problem on tty and is fine on tty2.  And this is also related
to your problems with ctrl-c.  Why accessing /dev/tty from tty1 is returning
ENXIO is what I'm not clear on right now...

Comment 4 David Cantrell 2006-03-03 19:06:32 UTC
This problem has been corrected in CVS.  The tty1 shell doesn't get ENXIO when
accessing /dev/tty now.  I also modified init so that when you've booted rescue
mode, the Ctrl+C, Ctrl+Z, and friends are not disabled.


Note You need to log in before you can comment on or make changes to this bug.