I am reading many hundred lines similar to below mentioned?
Could you please advise me what to do and how can I make my box more secure?
Jan 9 17:54:42 localhost sshd[5130]: reverse mapping checking getaddrinfo
for bbs-83-179.189.218.on-nets.com [218.189.179.83] failed - POSSIBLE
BREAK-IN ATTEM
In response to VeeJay <[EMAIL PROTECTED]>:
> I am reading many hundred lines similar to below mentioned?
>
> Could you please advise me what to do and how can I make my box more secure?
>
> Jan 9 17:54:42 localhost sshd[5130]: reverse mapping checking getaddrinfo
> for bbs-83-179.189.218.on-net
From: "VeeJay" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "FreeBSD-Questions"
Sent: Friday, January 12, 2007 11:43 PM
Subject: Please Help! How to STOP them...
I am reading many hundred lines similar to below mentioned?
Could you please advise me what to d
Thanks Reko
Just couple of more questions...
On 1/12/07, Reko Turja <[EMAIL PROTECTED]> wrote:
From: "VeeJay" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "FreeBSD-Questions"
Sent: Friday, January 12, 2007 11:43 PM
Subject: Please Help! How to STO
TECTED]>; "FreeBSD-Questions"
>>
>> Sent: Friday, January 12, 2007 11:43 PM
>> Subject: Please Help! How to STOP them...
>>
>>
>> >I am reading many hundred lines similar to below mentioned?
>> >
>> > Could you please advise
te:
>
> From: "VeeJay" <[EMAIL PROTECTED]>
> To: < [EMAIL PROTECTED]>; "FreeBSD-Questions"
>
> Sent: Friday, January 12, 2007 11:43 PM
> Subject: Please Help! How to STOP them...
>
>
> >I am reading many hundred lines similar to below mentioned
On Friday, January 12, 2007, at 01:34PM, "VeeJay" <[EMAIL PROTECTED]> wrote:
>What do you mean here?
>
>Remember to keep ssh1 disabled as well as direct root access into ssh
>> from the ssh config file.
>
>
>How to disable SSH1 and How to stop direct root access into ssh, where to
>change?
Sounds
On Friday January 12, 2007 at 04:54:37 (PM) Reko Turja wrote:
> >I am reading many hundred lines similar to below mentioned?
> >
> > Could you please advise me what to do and how can I make my box more
> > secure?
> >
> > Jan 9 17:54:42 localhost sshd[5130]: reverse mapping checking
> > getadd
VeeJay wrote:
I am reading many hundred lines similar to below mentioned?
Could you please advise me what to do and how can I make my box more
secure?
Jan 9 17:54:42 localhost sshd[5130]: reverse mapping checking
getaddrinfo
for bbs-83-179.189.218.on-nets.com [218.189.179.83] failed - POSS
Hiee,
Greetings,
I tried port knocking thing with Linux box,
Port knocking is a technique whereby attempting to connect to port A
enables access to port B from that same host.
Port knocking can be the solution for this. Tried with Linux iptables
only, I wonder if the similar thing can be done on
Jay Chandler <[EMAIL PROTECTED]> writes:
> Please, please, PLEASE RTFM. If that's too much to ask, try taking a
> class, hiring a consultant, or using a more user-friendly OS.
FreeBSD *is* user friendly. The simple (and fun to watch!) solution
involves using PF (not sure if this can be easily
On Fri, 12 Jan 2007 15:53:04 -0800
Jay Chandler <[EMAIL PROTECTED]> wrote:
> Please, please, PLEASE RTFM. If that's too much to ask, try taking a
> class, hiring a consultant, or using a more user-friendly OS.
I have been a user of FreeBSD for 8 years and it is very friendly to
me...not sur
VeeJay wrote:
I am reading many hundred lines similar to below mentioned?
Could you please advise me what to do and how can I make my box more secure?
Jan 9 17:54:42 localhost sshd[5130]: reverse mapping checking getaddrinfo
for bbs-83-179.189.218.on-nets.com [218.189.179.83] failed - POSSIBLE
On Sun, 14 Jan 2007 15:39:30 +0100
Erik Norgaard <[EMAIL PROTECTED]> wrote:
> - enforce key authentication
From memory, you still get the 'user unknown' messages if you have only key
auth.
> - restrict access to certain users or groups of users
I would say, idem here.
> - deny direct access as
On Mon, 15 Jan 2007 10:53:47 +1100
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> I would add to limit the number of passwords retries - so if they want to
> hammer you, at least they'll have to try a new connection. Of course, this
> leaves you open to a DOS ... but , well, i guess you are still o
Gerard Seibert wrote:
> Reko Turja wrote:
> > Moving your sshd port somewhere else than 22 - the prepackaged
> > "cracking" programs don't scan ports, just blindly try out the default
> > port - with determined/skilled attacker it's different matter entirely
> > though.
>
> Security thro
On 15 янв. 2007, at 19:05, Oliver Fromme wrote:
Gerard Seibert wrote:
Reko Turja wrote:
Moving your sshd port somewhere else than 22 - the prepackaged
"cracking" programs don't scan ports, just blindly try out the
default
port - with determined/skilled attacker it's different matter
entire
17 matches
Mail list logo
