Re: SSH question

2008-08-14 Thread Polytropon
Hi!

On Thu, 14 Aug 2008 10:06:46 +0800, EdwardKing [EMAIL PROTECTED] wrote:
 I use SSH to remote FreeBSD
 $ssh  [EMAIL PROTECTED]
 password:
 
 Then I SSh to suspend client in that remote machine:
 $~
 /home/tom: Permission denied
 
 Permission denied? Why? How to do that?

In opposite to Matthew Seaman I don't think it's an escape code
problem here. Instead, it seems you're trying to execute your
home directory. :-)

The $ sign seems to imply you're using the Bourne Shell. The
same problem you described can be done using the C Shell:

% ~
/home/poly: Permission denied.

When I try this in BASH, I get this:

$ ~
bash: /home/poly: is a directory

Maybe

% cd ~

is what you indended to do?



-- 
Polytropon
From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH question

2008-08-13 Thread Matthew Seaman
EdwardKing wrote:
 I use SSH to remote FreeBSD
 $ssh  [EMAIL PROTECTED]
 password:
 
 Then I SSh to suspend client in that remote machine:
 $~
 /home/tom: Permission denied
 
 Permission denied? Why? How to do that?

What happened here is that you were trying to type an escape code
into ssh -- eg. ~^Z (suspend) or ~. (quit)

However, '~' is actually a fairly common character in normal usage,
so ssh will pass it through to the remote login session unless you
get the escape sequence exactly right.  The ~ character must be the
first thing on a new line, and it must be followed by one of the
known key codes, which you can list by using the ~? escape during a
ssh session.

It seems that you typed something wrong: perhaps you managed to type
~~ which means your shell on the remote machine would receive the ~ character.  
This it would duely expand to be the path to your home
directory.  It then tried to execute that path, but directories are
not executable, resulting in the 'permission denied' message.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


Re: SSH question (some kind off-topic)

2007-05-19 Thread Kevin Hunter

At 5:42p -0400 on 19 May 2007, Arvee Klesk wrote:
Hi list. When a password is send (via a POP3 session without SSL,  
or without

establishing a secure connection) it can be retrieved by the ISP, or
somebody ahead, right. AFAIK, making an SSH session to a server and
forwarding, for instance, port 110 (POP3) to the SSH session, or  
some other
port / application, passwords and / or traffic cannot be retrieved  
as easy

by proxy servers or sniffers.

So my question is what happens in the SSH server then, the traffic  
can be analyzed on that side? Really I don't know what happens when  
traffic reach the SSH server and keep their way.


Sounds like your asking How does ssh work?  I'm not sure at what  
level you're asking this question, but let me point you to a couple  
of websites and perhaps you can figure out what you need, or come  
back with a more direct question.


http://en.wikipedia.org/wiki/Public-key_cryptography
http://www.linuxforums.org/forum/linux-security/53254-how-does-ssh- 
exactly-work.html


You might also Google for the keywords trusting trust and Ken  
Thompson


HTH,

Kevin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ssh question

2004-08-25 Thread Hugo Silva


 After modifying the sshd.conf to allow my new IP access via ssh I can't
 connect.  I have stopped and restarted the service and the server and
 double

'Allow your new ip address' ?

What you can specify on /etc/ssh/sshd_config is the ip the server binds
to, not the ip addresses of the clients connecting. (your words suggest
you did this) - reconfigure your sshd_config to the old value (your ip
address, or 0.0.0.0) and re-start sshd.

To limit access to the sshd, use a firewall, like ipfw , pf , or ipfilter.

 check the conf file.  I have checked hosts.allow and found nothing wrong.
 Is there some other file I need to change as well?  If not, how would I go
 about reinstalling/reconfiguring ssh?

 Thanks in advance



 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]



-- 
www.6s-gaming.com

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ssh question

2004-08-25 Thread epilogue
On Wed, 25 Aug 2004 13:42:52 -0500
Mark Tullos [EMAIL PROTECTED] wrote:

 
 After modifying the sshd.conf to allow my new IP access via ssh I can't
 connect.  I have stopped and restarted the service and the server and
 double check the conf file.  I have checked hosts.allow and found nothing
 wrong. Is there some other file I need to change as well?

are you running a firewall?  and if so, do you have a port open for ssh?

 If not, how would I go about reinstalling/reconfiguring ssh?
 
 Thanks in advance
 
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ssh question

2004-08-25 Thread Volker Kindermann
  After modifying the sshd.conf to allow my new IP access via ssh I
  can't connect.  I have stopped and restarted the service and the
  server and double
 
 'Allow your new ip address' ?
 
 What you can specify on /etc/ssh/sshd_config is the ip the server
 binds to, not the ip addresses of the clients connecting. (your words
 suggest you did this) - reconfigure your sshd_config to the old value
 (your ip address, or 0.0.0.0) and re-start sshd.
 
 To limit access to the sshd, use a firewall, like ipfw , pf , or
 ipfilter.
 

in addition you can actually limit access to the sshd with the keywords
AllowUsers and AllowGroups with the corresponding user/group _names_
(not uid/gid!!!).

But there's no option to do this ip-based (this is possible with
packetfilters or tcp-wrapper).

Do a netstat -na|grep LISTEN|grep 22 to prove on which IP your
ssh-Server is listening.


 -volker
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH question

2004-06-07 Thread Matthew Seaman
On Mon, Jun 07, 2004 at 02:31:43PM -0400, Bart Silverstrim wrote:

 While the server I want to copy FROM is apparently running
 sshd2: SSH Secure Shell 3.2.3 (non-commercial version) on 
 i686-pc-linux-gnu
 
 I have created the pub key on the FreeBSD system with
 ssh-keygen -t dsa
 then copied the resulting .pub file to the other server with the name 
 ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2.  Neither one seems 
 to work, and I don't see errors being generated in the logs.

Yes -- the public keys generated by OpenSSH and SSH Corp versions of
ssh(1) are in different formats.  You can use ssh-keygen(1) to convert
a public key produced by the SSH Corp product into a format the
OpenSSH can cope with:

% ssh-keygen -i -f ssh-corp-key.pub  openssh-key.pub

Or you can got the other way round:

% ssh-keygen -e -f openssh-key.pub  ssh-corp-key.pub

('i' is for import, 'e' is for export).  You want to do the second,
and then copy the transformed public key into the authorized_keys file
on the target host.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpXNSXQuoADt.pgp
Description: PGP signature


Re: ssh question

2003-01-30 Thread Daniel Bye
On Thu, Jan 30, 2003 at 12:46:30PM -0500, Tyler Parrott wrote:
 Hello all,
 
  I was just in the process of compiling something through ssh(i.e. I
 ssh'd to my machine at home and ran make install) but during the
 compilation, my ssh client crashed.  Does that mean that my build was
 killed as well?

I'm afraid so.  screen (in the ports) may be of interest to help you
avoid this in future.

Dan

-- 
Daniel Bye

PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message