Hi All,
This may not be the correct list to ask this question, so please
point me in the right direction in that case.
We are in the process of setting up a bastion host. One of the
things we'd like to do is to filter packets not only at the ip layer,
but by what program is listening on
At 2:42p -0400 18 Apr 2007, Bill Moran wrote:
We are in the process of setting up a bastion host. One of the
things we'd like to do is to filter packets not only at the ip
layer, but by what program is listening on a particular port. Is
this a possibility?
Are you saying that you want to
At 3:46p -0400 18 Apr 2007, Chuck Swiger wrote:
On Apr 18, 2007, at 12:17 PM, Kevin Hunter wrote:
At 2:42p -0400 18 Apr 2007, Bill Moran wrote:
Are you saying that you want to have the packet filter check to
see what application is listening on a particular port, then
allow/deny access
At 8:34a -0400 on 26 Apr 2007, Bill Moran wrote:
In response to "Andreas Widerøe Andersen" <[EMAIL PROTECTED]>:
I'm getting a lot of unauthorized ssh login attempts. I have a
pretty basic
FreeBSD 6.2 setup. I have compiled my own kernel. Here's what I
get from my
daily security run output:
At 11:22a -0400 on 26 Apr 2007, Hal wrote:
On Apr 26, 2007, at 8:34 AM, Kevin Hunter wrote:
In general, utilizing public/private keys for remote
authentication is /much/ more secure than passwords.
There is some debate about which is more secure
public/private keys or username/password
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
At 1:56p -0400 on 02 Jun 2007, sac wrote:
> On 6/2/07, Christopher Hilton <[EMAIL PROTECTED]> wrote:
>> VeeJay wrote:
>>> Could someone would like to describe that how we can disable to show
>>> last executed commands by pressing Up Arrow?
>>>
>>
>> That would depend on which shell you are runnin
At 4:42a -0400 on 03 Jun 2007, VeeJay wrote:
> Actually, it was for the security reason that if somebody breaks in the
> server then he/she doesn't see what commands are being executed, etc,
> etc
>
> and I am using /bin/sh
>
> any more comments?
I don't use /bin/sh on a regular basis (bash,
