On 2/20/2013 5:55 AM, Anton Shterenlikht wrote:
From feenb...@nber.org Wed Feb 20 13:39:28 2013
From: Fleuriot Damien m...@my.gd
To: me...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned IP address
Date: Wed, 20 Feb
On Feb 20, 2013, at 10:28 AM, Anton Shterenlikht me...@bristol.ac.uk wrote:
I have a laptop with FreeBSD -current,
with ip address assigned via DHCP.
The laptop has neither a static ip address,
nor a domain.
I can ping the laptop fine, but cannot
ssh into it. The sshd is running, /etc
On Feb 20, 2013, at 10:45 AM, Anton Shterenlikht me...@bristol.ac.uk wrote:
From: Fleuriot Damien m...@my.gd
To: me...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned IP address
Date: Wed, 20 Feb 2013 10:31:22 +0100
Cc: freebsd-questions
From m...@my.gd Wed Feb 20 10:11:12 2013
Run this on your server:
tcpdump -ni wlan0 ip and port 22
Then try to ssh to the box,
see if SYN packets arrive,
see if your box sends SYN/ACK back.
172.21.220.12 is the ssh server
137.222.187.241
Ok I think you've got a DNS resolution problem here, so when you try to
establish the connection, SSHD tries to resolve your client's hostname.
It fails and times out, however your ssh login gracetime is already over.
You have several options here:
1/ increase the login grace time
From m...@my.gd Wed Feb 20 10:28:54 2013
Ok I think you've got a DNS resolution problem here,
so when you try to establish the connection,
SSHD tries to resolve your client's hostname.
It fails and times out, however your ssh login gracetime is already
From feenb...@nber.org Wed Feb 20 13:39:28 2013
From: Fleuriot Damien m...@my.gd
To: me...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned IP address
Date: Wed, 20 Feb 2013 10:31:22 +0100
Cc
From: Fleuriot Damien m...@my.gd
To: me...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned IP address
Date: Wed, 20 Feb 2013 10:31:22 +0100
Cc: freebsd-questions@freebsd.org
On Feb 20, 2013, at 10:28 AM, Anton Shterenlikht
On Feb 20, 2013, at 2:55 PM, Anton Shterenlikht me...@bristol.ac.uk wrote:
From feenb...@nber.org Wed Feb 20 13:39:28 2013
From: Fleuriot Damien m...@my.gd
To: me...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned IP address
...@bristol.ac.uk
Subject: Re: cannot ssh into a box with DHCP assigned
IP address
Date: Wed, 20 Feb 2013 10:31:22 +0100
Cc: freebsd-questions@freebsd.org
On Feb 20, 2013, at 10:28 AM, Anton
El día Wednesday, February 20, 2013 a las 03:18:47PM +0100, Fleuriot Damien
escribió:
Well.. what should it be?
I have on the problem box (ssh server):
wlan0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1
500
ether 00:21:5c:50:68:c3
inet
El día Wednesday, February 20, 2013 a las 03:43:43PM +0100, Matthias Apitz
escribió:
El día Wednesday, February 20, 2013 a las 03:18:47PM +0100, Fleuriot Damien
escribió:
Well.. what should it be?
I have on the problem box (ssh server):
wlan0: flags=8943UP,BROADCAST,RUNNING
(or by some other router more
far away) behind a real IP addr. You can check what this addr is by
going to the page http://myip.nl/
And you can not SSH to the addr shown there, at least normally it would
not
be NAT'ed to your addr you got by DHCP.
No way.
fuck
CipherWave Fibre Broadband with FREE installation from only R8840/month
Good day,
I have just configured FreeBSD on my server. I would like to find out how can I
be able to login to it via ssh?
Looking forward to hear from you soon.
Thank you
--
Mannase Nyathi
Support Technician
sb: 011 541
Hi,
On Tue, 15 Jan 2013 10:10:16 +
Mannase Nyathi mann...@cipherwave.co.za wrote:
CipherWave Fibre Broadband with FREE installation from only
R8840/month
Good day,
I have just configured FreeBSD on my server. I would like to find out
how can I be able to login to it via ssh
Hi,
I have just configured FreeBSD on my server. I would like to find out
how can I be able to login to it via ssh?
Looking forward to hear from you soon.
Thank you
you must enable ssh in /etc/inetd.conf and then read
Or better, in /etc/rc.conf
sshd_enable=YES
Olivier
man ssh
On 15/01/2013 10:10, Mannase Nyathi wrote:
I have just configured FreeBSD on my server. I would like to find out
how can I be able to login to it via ssh?
Start by editing /etc/rc.conf and add the line:
sshd_enable=YES
(anywhere in the file -- order doesn't matter)
Then as root:
/etc
. You can change that by editing /etc/ssh/sshd_config .
--
Bruce Cran
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD on my server. I would like to find out
how can I be able to login to it via ssh?
Looking forward to hear from you soon.
Thank you
you must enable ssh in /etc/inetd.conf and then read
In FreeBSD it is in rc.conf
$ man rc.conf | col -b | fgrep -i ssh
matthias
On Tue, 15 Jan 2013 10:52:04 +
Matthew Seaman articulated:
On 15/01/2013 10:10, Mannase Nyathi wrote:
I have just configured FreeBSD on my server. I would like to find
out how can I be able to login to it via ssh?
Start by editing /etc/rc.conf and add the line:
sshd_enable=YES
have just configured FreeBSD on my server. I would like to find out
how can I be able to login to it via ssh?
Looking forward to hear from you soon.
Thank you
you must enable ssh in /etc/inetd.conf and then read
In FreeBSD it is in rc.conf
$ man rc.conf | col -b | fgrep -i ssh
In FreeBSD
Volodymyr Kostyrko c.kw...@gmail.com writes:
snip
In FreeBSD there are two ways of enabling sshd: default, fast and easy through
rc.conf and a bit tricky and secure via inetd.conf. Everyone can select their
own poison. I personally prefer the latter one.
You seem to imply that enabling sshd
El día Tuesday, January 15, 2013 a las 02:40:32PM +0200, Volodymyr Kostyrko
escribió:
In FreeBSD it is in rc.conf
$ man rc.conf | col -b | fgrep -i ssh
In FreeBSD there are two ways of enabling sshd: default, fast and easy
through rc.conf and a bit tricky and secure via inetd.conf
On 15/01/2013 12:51, Matthias Apitz wrote:
Why it is more secure via inetd.conf?
You can centralise access control via TCP Wrappers -
http://www.freebsd.org/doc/handbook/tcpwrappers.html .
--
Bruce Cran
___
freebsd-questions@freebsd.org mailing
15.01.2013 14:48, Frank Staals:
Volodymyr Kostyrko c.kw...@gmail.com writes:
snip
In FreeBSD there are two ways of enabling sshd: default, fast and easy through
rc.conf and a bit tricky and secure via inetd.conf. Everyone can select their
own poison. I personally prefer the latter one.
You
To: Volodymyr Kostyrko
Cc: Erich Dollansky; questi...@freebsd.org; Mannase Nyathi
Subject: Re: SSH on FreeBSD
El dÃa Tuesday, January 15, 2013 a las 02:40:32PM +0200, Volodymyr Kostyrko
escribió:
In FreeBSD it is in rc.conf
$ man rc.conf | col -b | fgrep -i ssh
In FreeBSD there are two
On Tue, 1 Jan 2013 18:59:05 +0330, takCoder wrote:
thank you for the details mentioned :)
but now, a questions occurred to me about this ssh key.
as i don't know enough about its process, would you please tell me whether
this key is a shared key for all ssh clients who send a request
of keys involved in ssh. The host keys are used at
the start of the connection to make sure that some other machine doesn't
impersonate the one you wanted.
and
On Wed, Jan 2, 2013 at 2:22 PM, Polytropon wrote:
The key received in the first step of a SSH session is the
host key which identifies the host
-- Forwarded message --
From: Aldis Berjoza graude...@yandex.com
Date: Tue, Jan 1, 2013 at 2:17 PM
Subject: Re: ssh server hashcode change on nanoBSD
I've never used NanoBSD, but, check if ssh daemon can write to /etc/ssh/
otherwise it won't be able to save ssh_host_* keys
Or you
On Tue, 1 Jan 2013 14:11:21 +0330, takCoder wrote:
everything is fine until i restart my nanoBSD server. the problem is that
each time i restart my server, the source system is complaining about that
i need to edit my known_hosts file cause my nanoBSD hash-code is not
matched..
how can i
thank you for the details mentioned :)
but now, a questions occurred to me about this ssh key.
as i don't know enough about its process, would you please tell me whether
this key is a shared key for all ssh clients who send a request? or it
differs as the client changes?
(this question may sound
Don't top-post, please.
takCoder tak.offic...@gmail.com writes:
but now, a questions occurred to me about this ssh key.
as i don't know enough about its process, would you please tell me whether
this key is a shared key for all ssh clients who send a request? or it
differs as the client
Paul Kraus p...@kraus-haus.org writes:
On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Yup, I just have not had a chance to chase that one down, and
given that it happens once per SSH session, has not been a high
priority. I mentioned
On Fri, Nov 23, 2012 at 6:43 PM, Paul Kraus p...@kraus-haus.org wrote:
I am seeing very poor response time running the VitrualBox GUI via X11
tunneled over SSH via the Internet. The issue _appears_ to be limited
to the VBox GUI as Firefox is reasonable. I am well aware of the
latency issues
I am seeing very poor response time running the VitrualBox GUI via X11
tunneled over SSH via the Internet. The issue _appears_ to be limited
to the VBox GUI as Firefox is reasonable. I am well aware of the
latency issues tunneling X11 over SSH across the Internet, but that is
what we are stuck
On Fri, Nov 23, 2012 at 11:43 AM, Paul Kraus p...@kraus-haus.org wrote:
I am seeing very poor response time running the VitrualBox GUI via X11
tunneled over SSH via the Internet. The issue _appears_ to be limited
to the VBox GUI as Firefox is reasonable. I am well aware of the
latency issues
On Fri, Nov 23, 2012 at 1:01 PM, Adam Vande More amvandem...@gmail.com wrote:
On Fri, Nov 23, 2012 at 11:43 AM, Paul Kraus p...@kraus-haus.org wrote:
I am seeing very poor response time running the VitrualBox GUI via X11
tunneled over SSH via the Internet. The issue _appears_ to be limited
Paul Kraus p...@kraus-haus.org writes:
I am seeing very poor response time running the VitrualBox GUI via X11
tunneled over SSH via the Internet. The issue _appears_ to be limited
to the VBox GUI as Firefox is reasonable. I am well aware of the
latency issues tunneling X11 over SSH across
On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
Observations:
1. When I first SSH into the box I see a long delay after the SSH
tunnel is setup before being prompted for a password, and I do not
know if this delay is related to the VBox issue
On 13 Apr 2012 at 23:51, Frank Staals wrote:
John McDonnell gorgar...@ymail.com writes:
All in all, creating an entry in Site Manager makes more sense if
it's something you connect to from your own hardware. From someone
else's machine, the quick connect is quite handy though.
Don't
On 12 Apr 2012 at 11:28, Frank Bonnet wrote:
Dave B d...@g8kbv.demon.co.uk writes:
Hi, ordinarily perhaps yes, if I could only figure out how to set
it up on the FreeBSD box. As always, the Manuals though no doubt
correct and complete as a reference, are no good to people who
don't
On 12 Apr 2012 at 9:32, Frank Staals wrote:
Dave B d...@g8kbv.demon.co.uk writes:
Hi, ordinarily perhaps yes, if I could only figure out how to set it
up on the FreeBSD box. As always, the Manuals though no doubt
correct and complete as a reference, are no good to people who
don't
, not current,
but it works.) That is mainly used for timekeeping with an attached
PPS equipped GPS. No problems with that.
It also has a small web server (Hiawatha) FTP server and SSH portal,
for my own use.
The FTP server is the built-in OS based ftpd implementation, and
works well
From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
questi...@freebsd.org] On Behalf Of Dave B
FYI, you have to create an entry in FileZilla's Site Manager, for it
to invoke SFTP, the Quickconnect feature just uses plain vanilla FTP.
Best Regards.
Dave Baxter.
You can
On 13 Apr 2012 at 9:21, John McDonnell wrote:
From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
questi...@freebsd.org] On Behalf Of Dave B
FYI, you have to create an entry in FileZilla's Site Manager, for it
to invoke SFTP, the Quickconnect feature just uses plain vanilla
John McDonnell gorgar...@ymail.com writes:
All in all, creating an entry in Site Manager makes more sense if it's
something you connect to from your own hardware. From someone else's
machine, the quick connect is quite handy though.
Don't forget to clear out the entry from the dropdown list
On 11 Apr 2012 at 14:54, Mike Clarke wrote:
On Wednesday 11 April 2012, Dave B wrote:
I just found however, that though I can reliably send a file to the
FTP server and it get's saved just fine, that's not true when
connecting this way using a SSH tunnel.
Would it not be simpler just
Dave B d...@g8kbv.demon.co.uk writes:
Hi, ordinarily perhaps yes, if I could only figure out how to set it up
on the FreeBSD box. As always, the Manuals though no doubt correct and
complete as a reference, are no good to people who don't already know
How To do it.
There is not much to
why not ftp over TLS ? like proftpd or pure-ftpd can do ?
Envoyé de mon iPhone.
Le 12 avr. 2012 à 09:32, Frank Staals fr...@fstaals.net a écrit :
Dave B d...@g8kbv.demon.co.uk writes:
Hi, ordinarily perhaps yes, if I could only figure out how to set it up
on the FreeBSD box. As always,
command, or you can use such things
as WEBDAV. Easy to run over TLS by using HTTPS.
* RSYNC -- has an anonymous mode which works fine for generic
downloads. For authenticated access defaults to ssh(1) for all
traffic.
* SFTP or SCP -- for those who are unwilling or unable
On Wednesday 11 April 2012, Dave B wrote:
I just found however, that though I can reliably send a file to the
FTP server and it get's saved just fine, that's not true when
connecting this way using a SSH tunnel.
Would it not be simpler just to use sftp directly rather than tunnelling
ftp
for timekeeping with an attached PPS equipped
GPS. No problems with that.
It also has a small web server (Hiawatha) FTP server and SSH portal, for
my own use.
The FTP server is the built-in OS based ftpd implementation, and works
well for all that I need.
Anyway... I found a while ago, that I can tunnel
On Mon, Mar 19, 2012 at 8:45 PM, Mark Felder f...@feld.me wrote:
Is the HPN patchset included with the base OpenSSH the full patchset? Does
it include the threaded CTR patch? I can't seem to find a clear answer to
this.
crypto/openssh/README.hpn references it so I would assume so.
--
Adam
Is the HPN patchset included with the base OpenSSH the full patchset? Does
it include the threaded CTR patch? I can't seem to find a clear answer to
this.
Thanks,
Mark
___
freebsd-questions@freebsd.org mailing list
, I have a pretty nice Fvwm environment with
some nifty plotting. (Though I wonder, is it better to be forced to
visualize the underlying curve's of a system without looking. A
philosophical problem for another day...)
Second, I am getting: inetd[1081]: ssh/tcp: bind: address already in use
On Feb 8, 2012, at 11:39 AM, Henry Olyer wrote:
Second, I am getting: inetd[1081]: ssh/tcp: bind: address already in use.
What's the fix, please?
Don't try to run sshd via inetd when you're already starting it as a daemon.
Regards,
--
-Chuck
On 1/6/2012 12:07 PM, Al Plant wrote:
per...@pluto.rain.com wrote:
Al Plant n...@hdk5.net wrote:
I accessed the sshd from the new install screen as an option when
I loaded it on the test box. I had to set up the lan manually to
first get it up. Then you should be able to use ssh.
I take
to
first get it up. Then you should be able to use ssh.
I take it you either arranged for ssh to accept a direct root login,
or added a non-root username. Does the new installer do one of
these automatically, or is there more manual configuration involved?
BSD Installer asks if you want
Peter Kryszkiewicz tundra2b...@gmail.com writes:
I have several machines networked using NFS mounts or SSH and scp. Only one
machine has internet connectivity - a laptop (machine vbear) with a wireless
card (I'm in a temporary location for a few weeks and only wireless is
available here).
I
I have several machines networked using NFS mounts or SSH and scp. Only one
machine has internet connectivity - a laptop (machine vbear) with a wireless
card (I'm in a temporary location for a few weeks and only wireless is
available here).
I tried to mount the ports tree on this machine
Does anyone know a good way of limiting the number of ssh attempts
from a single IP address?
I found the following website, which describes a variety of approaches:
http://www.freebsdwiki.net/index.php/Block_repeated_illegal_or_failed_SSH_logins
But I am honestly not really happy with any
anyone know a good way of limiting the number of ssh attempts
from a single IP address?
I found the following website, which describes a variety of approaches:
http://www.freebsdwiki.net/index.php/Block_repeated_illegal_or_failed_SSH_logins
But I am honestly not really happy with any of them
2011/9/19 Григорьев Александр mr.fes...@yandex.ru:
If your target is protect freebsd box from bruting passwords from inet maybe
security/knockd will help you?
19.09.2011, 23:05, James Strotherjstrother9...@gmail.com:
Does anyone know a good way of limiting the number of ssh attempts
from
target is protect freebsd box from bruting passwords from inet
maybe security/knockd will help you?
19.09.2011, 23:05, James Strother jstrother9...@gmail.com:
Does anyone know a good way of limiting the number of ssh attempts
from a single IP address?
I found the following website, which
of unauthorized
login attempts. Everything so far is highly unsophisticated, but it
did make me start to really think about the issue. I might put ssh
onto a different port, that would at least stop the sort of fishing I
am currently seeing. It's not clear if that would be good enough.
@Damien Fleuriot
Have
On 9/19/2011 2:05 PM, James Strother wrote:
Does anyone know a good way of limiting the number of ssh attempts
from a single IP address?
I found the following website, which describes a variety of approaches:
http://www.freebsdwiki.net/index.php/Block_repeated_illegal_or_failed_SSH_logins
Moving ssh to another port has solved the problem for me.
I had used sshguard in the past, but was always leery of locking myself out.
Regards,
Matt Emmerton
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of James
Does anyone know a good way of limiting the number of ssh attempts
from a single IP address?
I found the following website, which describes a variety of approaches:
http://www.freebsdwiki.net/index.php/Block_repeated_illegal_or_failed_SSH_logins
But I am honestly not really happy
Григорьев == Григорьев Александр mr.fes...@yandex.ru writes:
Григорьев If your target is protect freebsd box from bruting passwords
Григорьев from inet maybe security/knockd will help you?
Portknocking adds only a dozen bits or so to your password. Do you
really think it helps to go from a
Paul == Paul Macdonald p...@ifdnrg.com writes:
Paul in my experience running ssh on a high port cuts the amount of unwanted
ssh
Paul connections to approximately zero, in fact i got a surprise when seeing a
sec
Paul log from a box which i hadn't done this for
I run sshd on 443 (for firewall
On Mon, Sep 19, 2011 at 05:11:28PM -0700, Randal L. Schwartz wrote:
Григорьев == Григорьев Александр mr.fes...@yandex.ru writes:
Григорьев If your target is protect freebsd box from bruting passwords
Григорьев from inet maybe security/knockd will help you?
Portknocking adds only a dozen
of ssh connections
Paul == Paul Macdonald p...@ifdnrg.com writes:
Paul in my experience running ssh on a high port cuts the amount of
Paul unwanted ssh connections to approximately zero, in fact i got a
Paul surprise when seeing a sec log from a box which i hadn't done this
Paul for
I run
, please pass the -v flag to
your ssh client to toggle verbose output and post that here too.
On 9/13/11 2:14 PM, George Vagner wrote:
I was thinking that maybe because the wired interface doesn't actually have
An IP address it is a reverse lookup thing.
-Original Message-
From
On 9/13/11 3:54 AM, george vagner wrote:
I have set up wireless AP with a static IP and bridged it to my internal
wired network on RE0.
I can successfully connect with WPA to the wireless network and browse other
computers on the wired net fine,
I can log into the freebsd machine using ssh
, 2011 5:36 AM
To: freebsd-questions@freebsd.org
Subject: Re: ssh with bridged ap
On 9/13/11 3:54 AM, george vagner wrote:
I have set up wireless AP with a static IP and bridged it to my internal
wired network on RE0.
I can successfully connect with WPA to the wireless network and browse
other
Allow connections to forwarded ports in sshd config
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of George Vagner
Sent: Tuesday, September 13, 2011 8:14 AM
To: freebsd-questions@freebsd.org
Subject: RE: ssh
I have set up wireless AP with a static IP and bridged it to my internal
wired network on RE0.
I can successfully connect with WPA to the wireless network and browse other
computers on the wired net fine,
I can log into the freebsd machine using ssh no problem as long as if I
connect via
.]
inet 192.168.101.123 netmask 0xff00
Then in natd.conf I have nats defined like so:
redirect_port tcp 192.168.101.123:22 12322
At first _all_ my NATed ssh connections were slow until I added -tso
to the main nic ifconfig. So this -tco switch is something that I've
had to add to all
On Tue, Jul 12, 2011 at 03:18:07AM -0700, per...@pluto.rain.com wrote:
DISPLAY is not getting set in a remote shell started by ssh -X.
$ echo $DISPLAY
:0.0
$ ssh -X [server] 'echo DISPLAY=%$DISPLAY%'
DISPLAY=%%
How would I go about debugging this?
DISPLAY _is_ set correctly
Mark Felder f...@feld.me wrote:
On Tue, 12 Jul 2011 00:06:33 -0500, Michael Sierchio ku...@tenebras.com
wrote:
xauth not in your path?
ssh -Y skips all auth stuff so you don't need xauth; he said that
didn't work either :-(
Well, apparently, even -Y needs xauth (which was not installed
Frank Shute fr...@shute.org.uk wrote:
On Tue, Jul 12, 2011 at 03:18:07AM -0700, per...@pluto.rain.com wrote:
DISPLAY is not getting set in a remote shell started by ssh -X.
...
Have you tried putting:
DISPLAY=:0.0
in ~/.ssh/environment on the machine that's not setting DISPLAY
properly
DISPLAY is not getting set in a remote shell started by ssh -X.
$ echo $DISPLAY
:0.0
$ ssh -X [server] 'echo DISPLAY=%$DISPLAY%'
DISPLAY=%%
How would I go about debugging this?
DISPLAY _is_ set correctly on the ssh client -- I am running in
an xterm there, and can successfully start
This sounds silly, but what happens if you try ssh -Y
Regards,
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr
Mark Felder f...@feld.me wrote:
This sounds silly, but what happens if you try ssh -Y
Exactly the same thing as with -X, in either direction.
It still fails with the 6.1 system as the ssh client,
and works with the 6.1 system as the ssh server
xauth not in your path?
On Tue, Jul 12, 2011 at 4:46 AM, per...@pluto.rain.com wrote:
Mark Felder f...@feld.me wrote:
This sounds silly, but what happens if you try ssh -Y
Exactly the same thing as with -X, in either direction.
It still fails with the 6.1 system as the ssh client
On Tue, 12 Jul 2011 00:06:33 -0500, Michael Sierchio ku...@tenebras.com
wrote:
xauth not in your path?
ssh -Y skips all auth stuff so you don't need xauth; he said that didn't
work either :-(
___
freebsd-questions@freebsd.org mailing list
http
It still fails with the 6.1 system as the ssh client,
and works with the 6.1 system as the ssh server
Is X11Forwarding yes set in the server config of the failing direction?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
Eitan Adler li...@eitanadler.com wrote:
It still fails with the 6.1 system as the ssh client,
and works with the 6.1 system as the ssh server
Is X11Forwarding yes set in the server config of the failing
direction?
Both seem to be defaulted.
On 6.1:
$ egrep -C 2 X11Forwarding /etc/ssh
On 7/8/2011 11:07 PM, David Krauser wrote:
Hello everybody,
I've tried to setup a kind of 'dedicated ssh client' using FreeBSD, and
I'm having some issues with the terminal colors.
I have a basic install of FreeBSD 8.2-RELEASE (I only had kernel-dev
packages checked at installation) and I
I echoed $TERM on both boxes, and they are both cons25. I figured out,
though, that I'm only seeing the color spillover issue when I run GNU
Screen on the remote box (which is OpenBSD). GNU Screen is not installed
on the FreeBSD box.
How can I get screen's colors to work in my FreeBSD ssh
Figured it out. I just needed screen installed on the FreeBSD box. Thanks
for all your help!
On Sat, 9 Jul 2011, Joshua Isom wrote:
On 7/8/2011 11:07 PM, David Krauser wrote:
Hello everybody,
I've tried to setup a kind of 'dedicated ssh client' using FreeBSD, and
I'm having some issues
(which is OpenBSD). GNU Screen is not installed
on the FreeBSD box.
How can I get screen's colors to work in my FreeBSD ssh sessions? I can
connect to the remote box from other computers (using putty, xterm,
linux console, etc.) without issue. Maybe I need to have screen
installed in FreeBSD
Hello everybody,
I've tried to setup a kind of 'dedicated ssh client' using FreeBSD, and
I'm having some issues with the terminal colors.
I have a basic install of FreeBSD 8.2-RELEASE (I only had kernel-dev
packages checked at installation) and I rebuilt the GENERIC kernel with
the VESA
a few personal ruby on rails hosting on one of the
servers (via mod_passenger), and I'd like to do so for other people.
Problem: most of the RoR operations will require a ssh shell, for
example for rake db:migrate, local gem installation, debugging, and
local git repository management as well.
I
I have a question concerning SSH op a FreeBSD 7.4-STABLE server.
Is it possible to limit the SSH access?
I want t o restrict a user to his own home directory.
So that if he connects to the server with SSH he only can go to his own home
dir.
Also the same for sftp...
Thanks for your time
Jack
On 04/05/2011 10:08, Jack Raats wrote:
I have a question concerning SSH op a FreeBSD 7.4-STABLE server.
Is it possible to limit the SSH access?
I want t o restrict a user to his own home directory.
So that if he connects to the server with SSH he only can go to his own home
dir.
Also
On 4 May 2011 13:35, Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
On 04/05/2011 10:08, Jack Raats wrote:
I have a question concerning SSH op a FreeBSD 7.4-STABLE server.
Is it possible to limit the SSH access?
I want t o restrict a user to his own home directory.
So that if he
Jack Raats j...@jarasoft.net writes:
Hello,
I have a question concerning SSH op a FreeBSD 7.4-STABLE server.
Don't know sshd version in 7.4-STABLE, but if higher or equal to 4.8,
the following link could help :
http://www.debian-administration.org/articles/590
Regards
Éric Masson
--
C'est
On 4 May 2011 12:47, Balázs Mátéffy repcs...@gmail.com wrote:
On 4 May 2011 13:35, Matthew Seaman m.sea...@infracaninophile.co.uk
wrote:
On 04/05/2011 10:08, Jack Raats wrote:
I have a question concerning SSH op a FreeBSD 7.4-STABLE server.
Is it possible to limit the SSH access
On 4 May 2011 16:27, krad kra...@gmail.com wrote:
On 4 May 2011 12:47, Balázs Mátéffy repcs...@gmail.com wrote:
On 4 May 2011 13:35, Matthew Seaman m.sea...@infracaninophile.co.uk
wrote:
On 04/05/2011 10:08, Jack Raats wrote:
I have a question concerning SSH op a FreeBSD 7.4-STABLE
1 - 100 of 2751 matches
Mail list logo
