Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security FullDisclosure
[Top] [All Lists]

Re: [Full-Disclosure] Re: !SPAM! Automated ssh scanning

Subject: Re: [Full-Disclosure] Re: !SPAM! Automated ssh scanning
Date: Sat, 28 Aug 2004 22:23:36 +0200
On Saturday 28 August 2004 13:32, gadgeteer@elegantinnovations.org wrote:
On Thu, Aug 26, 2004 at 03:14:27PM -0500, Ron DuFresne 
(dufresne@winternet.com) wrote:
Those do not make alot of difference, the key is not to accept any of the
defaults by any of these dists, pick and choose carefully which
individual packages you install.   I know redhat has dependancy hell with
various packages, from the experience of trying to do as minimal as
possible an install for a webhost while migrating from sunone on solaris
to
apache/redhat on the mainframe awhile back.  I do not doubt that some of
these additional dists are wraught with the same issues.  But, I do know
that slackware's installation process has the ability for one to do
finegrained installs and to determine specifically individual packages
from each package set.

Just because slack does not prevent one from installing or not, whatever
packages one chooses does not mean there is no dependency issues.  They
are there and they will break things.

True, but this does not address the issue that there are _really_stupid_ 
dependencies to be found if you look around.  Things that make only sense in 
special circumstances. I know of no example offhand, but I mean along the 
lines of <a package with a web frontend has netscape as dependency>, <a 
networksniffer needs libOpenGL> and such obviously flawed packages.
(I mean, just the fact that a networksniffer has a GUI in addition to 
commandline use, and that some functions in that GUI require openGL shouldn't 
be a large enough reason to put a hard dependency on OpenGL. Right? )

I remember well that at one time I wanted to install a SuSE system without X, 
and just one package triggered 4 other packages and those then triggered the 
full X eventually.  It really was a pain.  Mind you, that was a few years 
back, I get the distinct impression things have changed for the better now. 

Maarten

-- 
Yes of course I'm sure it's the red cable. I guarante[^%!/+)F#0c|'NO CARRIER

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

<Prev in Thread] Current Thread [Next in Thread>