Hong,
I think you are a little bit wrong! Since Windows NT the following
rule matches every situation:
If there are on two machines an account with the same username
and password - the machines will trust each other for this particular
user irrespective of the domain or computer-domain
Robert
It doesn't make sense because 90 days is too long. A password should be
changed
at least after 30 days - if they are strong enough. A cracker has 90 days
to find out the correspondig password .
Robert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent:
I think you should give snort a closer look!
Robert
--
http://board.protecus.de - Firewalls, Security and more ...
www.different-thinking.de - Netze, Protokolle, Sicherheit, ...
-Original Message-
From: Jennifer Fountain [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003
Hi Marco,
if you really wanna do something with security first upgrade to
an real operating system like Linux, BSD, Windows 2000 or Windows
XP Pro.
I would like to have some suggestion for software for security (port
scan, firewall, etc.); I have a Pentium III, 256 Mb of RAM, 20 GB of Hd,
The big scary-looking range of ports (1024-65535) are outbound UDP ports,
which is a very common requirement. A lot of firewalls allow this by
default because it can be (sometimes incorrectly) assumed that a
connection
originating from behind the firewall going out to the internet should be
Do you tried arpwatch? Or Languard Network Scanner from www.gfi.com
Robert
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Xaos
Gesendet: Samstag, 7. Dezember 2002 01:07
An: [EMAIL PROTECTED]
Betreff: IP conflict and mac
I recently came
18:43
An: Robert Sieber; [EMAIL PROTECTED]
Betreff: RE: How to authentificate an user via telephon?
Robert,
In a past life we would send the new password to a known email address
for the person whose account is reset. If email is not available we
would leave the reset password
From my point of view the only difference as you know is in connection
handling: tcp ist connection orientated and udp conection less.
You shouldn´t close ports - you should close al ports and only allow
needed ports. So you can figure out which ports are needed and if they
are udp or tcp.
Robert
From my point of view there will be a big lack of security if you open all
outbound ports. Every application would have full access to the internet
- do you really want it?
More then 50% of all security risks are base insinde your network. So it
is very important to have an strict policy for
I think there should be sth. like encrypted VNC - take a look
at google
R.
--
http://board.protecus.de - Firewalls, Security and more ...
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:security-basics-return-15751-rsieber=web.de;securityfocus.com]Im
Auftrag von SB CH
FTP over SSL? I use WSFTP Server and it works fine with
128 bit encryption and certificates.
There is also CuteFTP Server on Windows NT/2000 for
encrypted FTP.
http://www.eftp.org/ - 448 bit Blowfish encryption for
FTP
Robert
--
http://board.protecus.de - Firewalls, Security and more ...
FTP over SSL? I use WSFTP Server and it works fine with
128 bit encryption and certificates.
There is also CuteFTP Server on Windows NT/2000 for
encrypted FTP.
http://www.eftp.org/ - 448 bit Blowfish encryption for
FTP
Robert
--
http://board.protecus.de - Firewalls, Security and more ...
I think if there is no direct connection to your internal
network and your gateways there will be no real risks for
security.
Maybe it is possible to use a bandwidth limited internal
connection? If you have the abbility to limit bandwidth with
your switch you can simulate every bandwith for your
Are you looking for something like that:
http://www.foundstone.com/knowledge/proddesc/fport.html
Robert
--
http://protecus.de - Firewalls, Security and more ...
-Original Message-
From: R Pradeep Chandran [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 8:25 AM
14 matches
Mail list logo