Skip Menu |
Report information
Id: 130358
Status: open
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: cpan [at] zoffix.com
Cc:
AdminCc:

Severity: (no value)
Tag: (no value)
Platform: (no value)
Patch Status: (no value)
VM: (no value)



Subject: [WINDOWS] Spectest Triggers Firewall "Security Alert"
Download (untitled) / with headers
text/plain 609b
One of these tests trigger the firewall popup "security alert" on Windows 10 (see attachment): t\spec\S32-io\rename.t ............................................ ok t\spec\S32-io\slurp.t ............................................. ok t\spec\S32-io\socket-accept-and-working-threads.t ................. ok t\spec\S32-io\socket-recv-vs-read.t ............................... ok t\spec\S32-io\spurt.t ............................................. ok Not sure if we can do anything about it, but if it's possible, would be nice not to trigger any unnecessary warnings and alerts for people running the tests.
Subject: Untitled.png
Download Untitled.png
image/png 27k
Untitled.png
Subject: Re: [perl #130358] [WINDOWS] Spectest Triggers Firewall "Security Alert"
To: "Zoffix Znet (via RT)" <perl6-bugs-followup [...] perl.org>
Date: Fri, 16 Dec 2016 21:51:11 +0100
From: Elizabeth Mattijsen <liz [...] dijkmat.nl>
Show quoted text
> On 16 Dec 2016, at 15:52, Zoffix Znet (via RT) <perl6-bugs-followup@perl.org> wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #130358] > # in the subject line of all future correspondence about this issue. > # <URL: https://rt.perl.org/Ticket/Display.html?id=130358 > > > > One of these tests trigger the firewall popup "security alert" on Windows 10 (see attachment): > > t\spec\S32-io\rename.t ............................................ ok > t\spec\S32-io\slurp.t ............................................. ok > t\spec\S32-io\socket-accept-and-working-threads.t ................. ok > t\spec\S32-io\socket-recv-vs-read.t ............................... ok > t\spec\S32-io\spurt.t ............................................. ok > > Not sure if we can do anything about it, but if it's possible, would be nice not to > trigger any unnecessary warnings and alerts for people running the tests.<Untitled.png>
FWIW, a similar pop up occurs on MacOS. But it’s for starting up a listening socket. So, eh, not sure how you can test network functions without it? Liz
From: Nicholas Clark <nick [...] ccl4.org>
To: Elizabeth Mattijsen <liz [...] dijkmat.nl>
Date: Fri, 16 Dec 2016 22:12:17 +0000
CC: "Zoffix Znet (via RT)" <perl6-bugs-followup [...] perl.org>
Subject: Re: [perl #130358] [WINDOWS] Spectest Triggers Firewall "Security Alert"
Download (untitled) / with headers
text/plain 1.2k
On Fri, Dec 16, 2016 at 09:51:11PM +0100, Elizabeth Mattijsen wrote: Show quoted text
>
> > On 16 Dec 2016, at 15:52, Zoffix Znet (via RT) <perl6-bugs-followup@perl.org> wrote:
Show quoted text
> > One of these tests trigger the firewall popup "security alert" on Windows 10 (see attachment): > > > > t\spec\S32-io\rename.t ............................................ ok > > t\spec\S32-io\slurp.t ............................................. ok > > t\spec\S32-io\socket-accept-and-working-threads.t ................. ok > > t\spec\S32-io\socket-recv-vs-read.t ............................... ok > > t\spec\S32-io\spurt.t ............................................. ok > > > > Not sure if we can do anything about it, but if it's possible, would be nice not to > > trigger any unnecessary warnings and alerts for people running the tests.<Untitled.png>
> > FWIW, a similar pop up occurs on MacOS. But it’s for starting up a listening socket. So, eh, not sure how you can test network functions without it?
Is the popup for any listening socket, or only for those bound to external addresses? If the latter, then is the test binding to the default address (which IIRC is all interfaces), and hence can the warning be fixed by explicitly binding only to localhost? Nicholas Clark


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org