logcheck has started noticing the above error. I did a ls -lsa
/usr/bin/mlock and the result is:
8 -rwxr-sr-x1 root root 5668 Jan 13 2002 mlock
Does this mean that somehow the permissions have changed?
Should they have changed - and why?
How should I correct this? (Has my box bee
logcheck has started noticing the above error. I did a ls -lsa
/usr/bin/mlock and the result is:
8 -rwxr-sr-x1 root root 5668 Jan 13 2002 mlock
Does this mean that somehow the permissions have changed?
Should they have changed - and why?
How should I correct this? (Has my box bee
> > Wondering if some people know of some "content-aware" proxies/filters,
to
> > attempt to block [some of] those dangerous products (apart from
maintaining
> > a black-list...)
> If you allow out FTP I will be able to start an SSH connection over port
> 20 (FTP-Data) and it will look like a binar
> > Wondering if some people know of some "content-aware" proxies/filters,
to
> > attempt to block [some of] those dangerous products (apart from
maintaining
> > a black-list...)
> If you allow out FTP I will be able to start an SSH connection over port
> 20 (FTP-Data) and it will look like a binar
> >> 6346/tcp filteredgnutella
> >
> >"filtered" means there's no reply coming back on thos ports - most likely
> >your ISP is blocking those ports.
>
> Yeah, they said that gnutella was "limited".
Somewhat typical of ISPs - don't they realise that gnutella's port can be re-
configured? S
> >> 6346/tcp filteredgnutella
> >
> >"filtered" means there's no reply coming back on thos ports - most likely
> >your ISP is blocking those ports.
>
> Yeah, they said that gnutella was "limited".
Somewhat typical of ISPs - don't they realise that gnutella's port can be re-
configured?
6 matches
Mail list logo
