Hi, On Sun, 19 Feb 2017 23:18:24 +0100 Marcos Fouces <mfou...@yahoo.es> wrote: > Hello Axel > > This compiler flag (-fno-strict-aliasing) is needed in libnids. You are > right. I will revert this change in dsniff. I added the other flag (-g) > in order to avoid creating an empty dbgsym package. > > I cannot reproduce this bug in amd64 with the current libnids package > version (1.21). In fact, dsniff works as expected with this testcase. > > I built and installed libnids 1.24 (which fix another minor issue > already solved in Ubuntu) with -fno-strict-aliasing. At least in amd64, > dsniff still works as expected and i did not noticed any difference.
So after discovering #855602 (and if this was the minor issue you were referring to - it really wasn't), I was thinking about NMUing this package. However like Axel I also cannot get dsniff to print anything at all on amd64 even when rebuilding libnids with -fno-strict-aliasing. > If the current maintainer of libnids (CC'ed) gives me permission, i can > import the package to pkg-security team repo, upload my work and > maintain (or co-maintain) it by now. This makes sense as dsniff seems to > be the only reverse dependence of libnids. It looks like the maintainer of libnids has been MIA for some time so I suggest you just go ahead and do this after stretch is released (unless he reappears again). Thanks, James
signature.asc
Description: OpenPGP digital signature
