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

CyberDuck always causes a Leopard firewall warning #1903

Closed
cyberduck opened this issue Apr 7, 2008 · 4 comments
Closed

CyberDuck always causes a Leopard firewall warning #1903

cyberduck opened this issue Apr 7, 2008 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 7, 2008

908a9d9 created the issue

CyberDuck always causes a Leopard firewall warning: "Do you wish to allow incoming connections..." It doesn't matter if you click Allow or Deny, they still happen once each launch, when you first access an FTP server. This happens even though I added CyberDuck to the System Preferences firewall app list (with Allow, not Block).

It may be that this only occurs if you are not an Admin user. (I don't run as admin, for extra security, so I haven't tested that way.)

Thanks!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2008

04d3114 commented

Still occurs when running as Administrator. This is because the Leopard firewall is no longer port-based, but uses code-signing instead. I can't find the article at the moment, but there's something in the developer documentation that tells you how to fix this.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2008

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2008

@dkocher commented

There must be something wrong on your system. Cyberduck comes signed (try codesign -dv Cyberduck.app).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 9, 2008

04d3114 commented

Seems to have fixed it. Nevermind!

Loading

@cyberduck cyberduck closed this Apr 9, 2008
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants