On Fri, May 12, 2017 at 1:00 PM, Mathieu Trudel-Lapierre
<email address hidden> wrote:
> There's a subscriber and the package generally looks fine; modulo
> looking to see if tests can be run at build time.
I've got a patch locally that does seem to do this, but the tests
fail, because I think they require open-isns-server (specifically
isnsd and its configuration files) to be installed. So I'm not sure we
can run them during the build properly.
But we should run the self-tests in an autopkgtest (which I don't
think currently is happening). I will work on that at least.
> However, since this is for iSNS, name services tend to be security-
> sensitive and there is some CVE history (not for open-isns specifically,
> but...) for iSNS on Linux (for tgt specifically); I would like there to
> be a security review.
On Fri, May 12, 2017 at 1:00 PM, Mathieu Trudel-Lapierre
<email address hidden> wrote:
> There's a subscriber and the package generally looks fine; modulo
> looking to see if tests can be run at build time.
I've got a patch locally that does seem to do this, but the tests
fail, because I think they require open-isns-server (specifically
isnsd and its configuration files) to be installed. So I'm not sure we
can run them during the build properly.
But we should run the self-tests in an autopkgtest (which I don't
think currently is happening). I will work on that at least.
> However, since this is for iSNS, name services tend to be security-
> sensitive and there is some CVE history (not for open-isns specifically,
> but...) for iSNS on Linux (for tgt specifically); I would like there to
> be a security review.
Agreed.