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

Jump to bottom

Firewall allow/deny incoming connections prompt #6492

Closed
cyberduck opened this issue Jan 22, 2012 · 3 comments
Closed

Firewall allow/deny incoming connections prompt #6492

cyberduck opened this issue Jan 22, 2012 · 3 comments
Assignees
@dkocher
Labels
bug core thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

d741770 created the issue

Environment:

  • Mac OS X 10.7.2
  • Cyberduck 4.2.1 (9350)
  • OS X Firewall is turned on and cyberduck is not listed in the allowed applications list.

Problem:
The first time you attempt to login to any service after cyberduck is started a dialogue is shown then dismissed again far too fast to read it. I resorted to taking a video of the screen (which can be done using Quicktime Player and choosing 'New Screen Recording' in recent versions of OS X). Having taken the video and freeze framing it the dialogue box turned out to be firewall allow/deny incoming connections box.

I have not including any transcript as this happens on login and nothing has been printed in the log window at that point.

Workaround:
I imagine this problem can be worked around by configuring the firewall manually to accept, or deny, connections to cyberduck but I have not tried it.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

That is annoying. We have to find out if we cause this (which we should not as we are never accepting incoming connections but when active FTP connections are used) or this is a generic issue out of our control.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot find the cause of this issue and it seems it is out of our control.

@cyberduck
Copy link
Collaborator Author

Matt Clare commented

Other sites suggest that it's only displayed while the socket is open. So if Cyberduck concludes that a host is unreachable and closes the socket the prompt will go away. -- I've never seen a single line of Cyberduck's code though.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug core thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck