Thanks Paul. We did make some changes in Nmap 7.94 which could have caused
regressions. I've opened an issue for this on our upstream tracker (
https://github.com/nmap/nmap/issues/2685). Please let us know if you
figure anything else out.
-Gordon
On Tue, May 01, 2012 at 08:09:57PM +0100, Steven Chamberlain wrote:
>
> While here, I also saw what looked like Microsoft .exe redistributables
> in the source tarball / Git repository?
We currently include those in our upstream Nmap tarballs (they are
needed on Windows and MS gives permission to
On Fri, Mar 09, 2012 at 02:57:03PM +0100, chrysn wrote:
> Package: zenmap
> Version: 5.21-1.1
> Severity: grave
> Tags: security
>
> the zenmap script modifies its sys.path to include
> '/tmp/nmap-5.21/debian/tmp/usr/lib/python2.6/site-packages/', which is
> inserted at build time from setyp.py.
found is in the line
my $max = 1 << ($bytes * 8);
Theoretically overflow can happen here resulting in zero or negative result
and then the program can hang in the loop below this line. But for all
reasonable values this line is just fine.
Cheers,
Fyodor Menshikov.
--
To UNSUBSCRIBE, em
to use old approach (internal
rand without reseed) if --randomseed argument is specified. Anyway users of
--randomseed were warned that there are only 2^32 cases.
Cheers,
Fyodor Menshikov.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe&q
Package: makepasswd
Version: 1.10-4
Severity: critical
Tags: security
Justification: root security hole
By default makepasswd gets 32-bit random seed from /dev/urandom, initializes
Perl random numbers generator with it using srand function and then generates
password length and password chars usin
On Tue, Aug 18, 2009 at 06:59:51AM +0200, Ola Lundqvist wrote:
>
> As I'm the maintainer (and actually creator now when I look in the chnagelog)
> of ndiff and do not really have a problem to get that package removed.
> The "old ndiff" (ndiff package) is old as you
for
nearly 8 years. Our new Ndiff is actively maintained (distributed
with Nmap) and far more featureful than the ancient version. So the
Nmap Project recommends resolving this conflict by either removing the
old Ndiff package or renaming the ndiff executable from that package
to ndiff.pl sinc
ashed over by legal
minds much better than me in the Slashdot and Groklaw articles on the
topic.
Cheers,
Fyodor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
9 matches
Mail list logo
