At 22:53 9/13/2003 -0700, you wrote:
Can you elaborate on this a little more? Very interesting... Why not
just have a closed port?
Some SOHO hardware (albeit only a few devices) are too stupid to close the
port, so you make 100% sure that no one can reach its admin website from
the outside by re
Can you elaborate on this a little more? Very interesting... Why not
just have a closed port?
On Sun, 2003-09-07 at 17:57, Ed Wilts wrote:
> On Sun, Sep 07, 2003 at 10:52:46AM -1000, Marc Adler wrote:
> > I want to configure my Linksys router to allow ssh connections. One and
> > a half seconds o
At 22:04 9/8/2003 -1000, you wrote:
Ok. I will try to digest what you have written above and follow your
advice.
Most of it is very simple; but it will help you to ask very pointed and
focused questions so you understand the answers clearly.
Static addresses never change, either because you told
* Rodolfo J. Paiz <[EMAIL PROTECTED]> [2003-09-08 20:36]:
> At 11:07 9/8/2003 -1000, you wrote:
> >Yes, I went ahead and forwarded port 80 to 192.168.1.222, which isn't
> >either of the two computers I've got on my network (192.168.1.100 and
> >192.168.1.101). Is that ok?
>
> Yes. It avoids the sm
At 11:07 9/8/2003 -1000, you wrote:
Yes, I went ahead and forwarded port 80 to 192.168.1.222, which isn't
either of the two computers I've got on my network (192.168.1.100 and
192.168.1.101). Is that ok?
Yes. It avoids the small danger of peoply trying to get to your Linksys
router's admin functio
[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Mon, 08 Sep 2003 01:27:45 -0600
Subject: Re: Linksys router and ssh connection
> At 21:03 9/7/2003 -1000, you wrote:
> >Great! This worked. There wasn't a button or box to indicate the
> >protocol, so maybe it's automatically s
* Marc Adler <[EMAIL PROTECTED]> [2003-09-07 22:40]:
> * Rodolfo J. Paiz <[EMAIL PROTECTED]> [2003-09-07 21:29]:
> > At 21:03 9/7/2003 -1000, you wrote:
> > >Great! This worked. There wasn't a button or box to indicate the
> > >protocol, so maybe it's automatically set for both protocols. Either
>
ssh connection
I want to configure my Linksys router to allow ssh connections. One and a
half seconds of Googling showed me how to change the default password on it,
and it makes me wonder whether more people shouldn't know that there is a
default password that is the *same* for all Linksys ro
EMAIL PROTECTED]
On Behalf Of Marc Adler
Sent: Sunday, September 07, 2003 4:53 PM
To: [EMAIL PROTECTED]
Subject: Linksys router and ssh connection
I want to configure my Linksys router to allow ssh connections. One and
a half seconds of Googling showed me how to change the default password
on it, a
I believe the Linksys allows you to shut off remote admin capability.
<>
-- Original Message ---
From: "Rodolfo J. Paiz" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Mon, 08 Sep 2003 01:27:45 -0600
Subject: Re: Linksys router and ssh connection
> At
On Mon, Sep 08, 2003 at 08:10:29AM -0500, Benjamin J. Weiss wrote:
> > Yes, it's vital. Unless you forward port 80 to somewhere, I can point
> > my browser (or application) at your Linksys firewall and start guessing
> > passwords. After you forward port 80 to a non-existent IP address, I
> > won
> > > Marc, you did change the password and forward port 80 to your real
> > > webserver or some non-existent host, right?
> >
> > I changed the password, but didn't touch port 80, only port 22. I don't
> > have a webserver. Is it vital to change port 80? Will changing it affect
> > anything on my
On Mon, 2003-09-08 at 06:41, Ed Wilts wrote:
> On Sun, Sep 07, 2003 at 11:42:38PM -0600, Rodolfo J. Paiz wrote:
> > At 19:57 9/7/2003 -0500, you wrote:
> > >And, you should *always* forward port 80 to something, even a
> > >non-existent host, to disallow any hopes that somebody that somebody can
>
On Sun, Sep 07, 2003 at 10:38:45PM -1000, Marc Adler wrote:
> * Rodolfo J. Paiz <[EMAIL PROTECTED]> [2003-09-07 21:29]:
> > At 21:03 9/7/2003 -1000, you wrote:
> >
> > Marc, you did change the password and forward port 80 to your real
> > webserver or some non-existent host, right?
>
> I changed
On Sun, Sep 07, 2003 at 11:42:38PM -0600, Rodolfo J. Paiz wrote:
> At 19:57 9/7/2003 -0500, you wrote:
> >And, you should *always* forward port 80 to something, even a
> >non-existent host, to disallow any hopes that somebody that somebody can
> >talk to it from the outside.
>
> Perhaps that shoul
* Rodolfo J. Paiz <[EMAIL PROTECTED]> [2003-09-07 21:29]:
> At 21:03 9/7/2003 -1000, you wrote:
> >Great! This worked. There wasn't a button or box to indicate the
> >protocol, so maybe it's automatically set for both protocols. Either
> >way, it works, so thanks!
>
> Marc, you did change the pass
At 21:03 9/7/2003 -1000, you wrote:
Great! This worked. There wasn't a button or box to indicate the
protocol, so maybe it's automatically set for both protocols. Either
way, it works, so thanks!
Marc, you did change the password and forward port 80 to your real
webserver or some non-existent host
* ABrady <[EMAIL PROTECTED]> [2003-09-07 11:22]:
> On Sun, 07 Sep 2003 10:52:46 -1000
> Marc Adler <[EMAIL PROTECTED]> wrote:
>
> > I want to configure my Linksys router to allow ssh connections. One
> > and a half seconds of Googling showed me how to change the default
> > password on it, and it
At 19:57 9/7/2003 -0500, you wrote:
And, you should *always* forward port 80 to something, even a
non-existent host, to disallow any hopes that somebody that somebody can
talk to it from the outside.
Perhaps that should be "...especially if possible to a non-existent host..."?
--
Rodolfo J. Paiz
[
On Sun, Sep 07, 2003 at 10:52:46AM -1000, Marc Adler wrote:
> I want to configure my Linksys router to allow ssh connections. One and
> a half seconds of Googling showed me how to change the default password
> on it, and it makes me wonder whether more people shouldn't know that
> there is a defaul
At 16:17 9/7/2003 -0500, you wrote:
You don't say what version of router you have. There's no guarantee they
all have the same setup. But on mine:
1. Login to the outer.
2. At the opening page, click "Advanced".
3. Click on "Forwarding".
4. Fill in both blocks for the "Service Port Range". If al
On Sun, 07 Sep 2003 10:52:46 -1000
Marc Adler <[EMAIL PROTECTED]> wrote:
> I want to configure my Linksys router to allow ssh connections. One
> and a half seconds of Googling showed me how to change the default
> password on it, and it makes me wonder whether more people shouldn't
> know that the
Look at the port forwarding. You need to forward port 22 to the private
address of the linux box.
-Original Message-
From: Marc Adler [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 07, 2003 4:53 PM
To: [EMAIL PROTECTED]
Subject: Linksys router and ssh connection
I want to configure
I want to configure my Linksys router to allow ssh connections. One and
a half seconds of Googling showed me how to change the default password
on it, and it makes me wonder whether more people shouldn't know that
there is a default password that is the *same* for all Linksys routers,
but that's be
Allright,
I know its bad form to reply to your own post. But after digging
through the RPMs I have upgraded recently I realized that I had upgraded
glibc. So I thought perhaps my sshd that was running both before and
after the glibc update wasn't able to use the libraries it previously
had b
Hello,
Ever since yesterday two of my hosts have been closing SSH connections.
Both are RedHat 8.0 running OpenSSH_3.4p1. I updated packages on the
machines yesterday too. Is anyone aware of some package that might make
a change that would cause this?
I have checked /etc/hosts.{allow,deny}
do not necessarily represent the
views of the company. The company accepts no responsibility once an e-mail
and any attachments is sent.
-Ursprüngliche Nachricht-
Von: Rudik A.A. [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 12. März 2003 22:22
An: [EMAIL PROTECTED]
Betreff: SSH Connecti
>> Connection closed by 65.113.59.13
>> debug1: Calling cleanup 0x8061610(0x0)
>> [EMAIL PROTECTED] .ssh]#
>>
>> What must be done ?
>>
>> - Original Message -
>> From: "Patrick Nelson" <[EMAIL PROTECTED]>
>> To: <[
.ssh]#
>
> What must be done ?
>
> - Original Message -
> From: "Patrick Nelson" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 12, 2003 6:57 PM
> Subject: RE: SSH Connection
>
>
>> Rudik A.A. wrote:
>>> Hello All
D]>
Sent: Wednesday, March 12, 2003 6:57 PM
Subject: RE: SSH Connection
> Rudik A.A. wrote:
> > Hello All,
> >
> > I am facing problem to login to my RH 7.1 server by SSH. After
typing
> > passwd for root it gets "Connection closed"
> > I mast say tha
Rudik A.A. wrote:
> Hello All,
>
> I am facing problem to login to my RH 7.1 server by SSH. After typing
> passwd for root it gets "Connection closed"
> I mast say that it was working good and today we could not login not
> only as root, but any other users also can not login by ssh.
> And also t
Hello All,
I am facing problem to login to my RH 7.1 server by SSH. After typing
passwd for root it gets "Connection closed"
I mast say that it was working good and today we could not login not
only as root, but any other users also can not login by ssh.
And also telnet is disabled.
Any idias ?
Sancho Neves-Graca said:
> The SSH connections drop after a few hours of inactivity on the client
> side. However, I would like to keep the connections open, such that the
> X11 applications are still alive from one day to another.
>
Well, it might not be the right answer, but after fighting it for
louie miranda wrote:
>Hi, im planning to limit 1 user connection per user ip on ssh, is this
>possible?
>
>=
>Thanks,
>Louie Miranda...
>
>WebUrl: http://axis0.endofinternet.org
>Email: [EMAIL PROTECTED] - [EMAIL PROTECTED]
>
>
>
I use the setup shown below to restrict the connection on ssh
Why not just use tcp wrappers?
On Thursday 08 August 2002 04:40 am, Jim Bija wrote:
> Heres a quick way to limit only certain IP's to your SSH server. Which i
> think every ssh server admin should do myself. As the exploits have run
> wild as of late..
> These are simple IPCHAINS commands. Which
Use IPFilter ... or under solaris look at the RBAC system
On Thu, 8 Aug 2002, louie miranda wrote:
> Hi, im planning to limit 1 user connection per user ip on ssh, is this
> possible?
>
>
>
>
>
>
> =
> Thanks,
> Louie Miranda...
>
> WebUrl: http://axis0.endofinternet.org
> Email: [EMAIL P
Two things to check, ssh -v remote-host whats does it spit out when you
fail to connect?
But main thing would be to see the logs on the remote-host to see if
your connection did reach it ...
On Mon, 2002-03-25 at 18:45, vincent li wrote:
> hi, folks
>
> i use ssh to connect remote host, sometime
hi, folks
i use ssh to connect remote host, sometime, i can
access remote host very quickly, but sometime, i can
not access it,it complains that remote host is not
reachable, remote host maybe down, or maybe a problem
with network connection. but my remote host work very
well, and i can ping to r
Tomas you may want to try starting sshd with the debug option; it may give
you some kind of hint. ./sshd -d
On Fri, 2 Feb 2001, Tomás García Ferrari wrote:
> Hi,
>
> Going further, I discovered something...
>
> I am having a conflict between inet and sshd: if I run sshd from
> /etc/rc.d/init.d/
At 04:02 PM 2/2/01 +0100, you wrote:
>Hi,
>
>Yes, you're right. I am using openssh-server-2.1.1p4-1 and is picking the
>values from hosts.allow and hosts.deny. We can then asume that TCP Wrappers
>support is already built in, right?
I would think so.
>Thanks,
>
>Tomas Garcia Ferrari
>
>Bigital
Hi,
Yes, you're right. I am using openssh-server-2.1.1p4-1 and is picking the
values from hosts.allow and hosts.deny. We can then asume that TCP Wrappers
support is already built in, right?
Thanks,
Tomas Garcia Ferrari
Bigital
http://bigital.com
> The are various implementations of ssh, but
At 10:46 AM 2/2/01 +0100, you wrote:
>Hi,
>
>Going further, I discovered something...
>
>I am having a conflict between inet and sshd: if I run sshd from
>/etc/rc.d/init.d/sshd then it works nicely. If I try to run it from tcp
>wrappers, adding this line
> ssh stream tcp nowait root /usr/sbin/
Hi,
Going further, I discovered something...
I am having a conflict between inet and sshd: if I run sshd from
/etc/rc.d/init.d/sshd then it works nicely. If I try to run it from tcp
wrappers, adding this line
ssh stream tcp nowait root /usr/sbin/tcpd sshd -i
to /etc/inetd.conf, then it doesn
> Anything in the logs?
Yes, the sshd is down and these are the errors when I try to bring it up:
Feb 2 14:19:57 extensa sshd[1886]: error: Bind to port 22 on 192.168.0.3
failed: Address already in use.
Feb 2 14:19:57 extensa sshd[1886]: fatal: Cannot bind any address.
Any clue?
Tomas Garcia
Tomás García Ferrari wrote:
> Hi,
>
> After a reboot with a new kernel (2.2.16-3) my server (RH 6.2,
> openssh-server-2.1.1p4-1) is closing any ssh connection inmediately after
> login.
>
> Any clue?
Anything in the logs?
Bret
__
Hi,
After a reboot with a new kernel (2.2.16-3) my server (RH 6.2,
openssh-server-2.1.1p4-1) is closing any ssh connection inmediately after
login.
Any clue?
Thanks
Tomas Garcia Ferrari
Bigital
http://bigital.com
___
Redhat-list mailing list
46 matches
Mail list logo
