Displaying 5 results from an estimated 5 matches for "frankye".
Did you mean:
franke
2004 Apr 05
4
Q: Controlling access at the Ethernet level
Hi Adrian,
Sunday, April 4, 2004, 10:22:33 PM, you wrote:
AP> We have thought about using static MAC entries per port on managed
AP> switches installed at the client endpoints, but that would require a
AP> overwhelming budget. We are also thinking about L2TP and PPPoE, but I
AP> am uncertain about compatibility.
AP> What would you recommand ? Are there any other elegant
2004 Sep 18
8
Attacks on ssh port
Hi,
Is there a security problem with ssh that I've missed???
Ik keep getting these hords of:
Failed password for root from 69.242.5.195 port 39239 ssh2
with all kinds of different source addresses.
They have a shot or 15 and then they are of again, but a little later on
they're back and keep clogging my logs.
Is there a "easy" way of getting these ip-numbers added to
2004 May 03
1
Bad VuXML check on PNG port ?
Hello,
The current png-1.2.5_4 port has no more vulnerability.
It has been corrected by ache@FreeBSD.org yesterday.
But when i try to install the updated port to remplace
the vulnerable one this is what i am told :
# make install
===> png-1.2.5_4 has known vulnerabilities:
>> libpng denial-of-service.
Reference:
2004 May 17
4
Multi-User Security
Hello list.
I would like to get your opinion on what is a safe multi-user environment.
The scenario:
We would like to offer to some customers of ours some sort of network
backup/archive. They would put daily or weekly backups from their local
machine on our server using rsync and SSH. Therefore, they all have a user
account on our server. However, we must ensure that they would absolutely
not be
2004 Apr 20
3
[Full-Disclosure] IETF Draft - Fix for TCP vulnerability (fwd)
Forwarded message:
> From full-disclosure-admin@lists.netsys.com Wed Apr 21 11:49:12 2004
> To: full-disclosure@lists.netsys.com
> From: Darren Bounds <dbounds@intrusense.com>
> Subject: [Full-Disclosure] IETF Draft - Fix for TCP vulnerability
> Date: Tue, 20 Apr 2004 18:19:58 -0400
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>