Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spectest Triggers Firewall "Security Alert" #5888

Open
p6rt opened this issue Dec 16, 2016 · 5 comments
Open

Spectest Triggers Firewall "Security Alert" #5888

p6rt opened this issue Dec 16, 2016 · 5 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Dec 16, 2016

Migrated from rt.perl.org#130358 (status was 'open')

Searchable as RT130358$

@p6rt
Copy link
Author

p6rt commented Dec 16, 2016

From @zoffixznet

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.

@p6rt
Copy link
Author

p6rt commented Dec 16, 2016

From @zoffixznet

Untitled.png

@p6rt
Copy link
Author

p6rt commented Dec 16, 2016

From @lizmat

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-archive.perl.org/perl6/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

@p6rt
Copy link
Author

p6rt commented Dec 16, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Dec 16, 2016

From @nwc10

On Fri, Dec 16, 2016 at 09​:51​:11PM +0100, Elizabeth Mattijsen wrote​:

On 16 Dec 2016, at 15​:52, Zoffix Znet (via RT) <perl6-bugs-followup@​perl.org> wrote​:

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

@p6rt p6rt added the Windows label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant