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

Open in terminal fails in sandbox environment #7664

Open
cyberduck opened this issue Dec 5, 2013 · 20 comments
Open

Open in terminal fails in sandbox environment #7664

cyberduck opened this issue Dec 5, 2013 · 20 comments
Assignees
Labels

Comments

@cyberduck
Copy link
Collaborator

ee4355c created the issue

I had a fully working version of cyberduck... Downloaded from this website for free long time ago. But i wanted to buy it from the app store because i use it allot. I bought it... Uninstalled cyberduck and installed from the app store.
Now when i want to open in terminal the terminal window opens only the window for my mac not the window from the server i want to connect. How can i fix this?


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

05.12.13 09:27:54.000 kernel[0]: Sandbox: Cyberduck(43324) deny appleevent-send com.apple.terminal
05.12.13 09:27:54.620 appleeventsd[98]: Sandboxed application with pid 43324 attempted to lookup App:"Terminal"/276/0x0:0x8008 ????1010 sess=100004 but was denied due to sandboxing. (___ZL13handleMessageP17_xpc_connection_sPv_block_invoke260()/appleEventsD.cp #2413) client-reqs-q

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 70c39f6. We should use a com.apple.security.scripting-targets but this is not supported by Terminal.app.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Reopen issue with cb46ef3.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Proper error handling in 979f0d6.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Disabled the feature for Mac App Store builds in cb46ef3.

@cyberduck
Copy link
Collaborator Author

ee4355c commented

But from my understanding its not possible in the sandbox from the app store?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:8 gtube]:

But from my understanding its not possible in the sandbox from the app store?

The Send command feature documented in Custom Commands is not affected by this issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This ticket is about the feature Open in Terminal for SSH connections.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I do not currently see a way to make this work in a sandboxed environment.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8883 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Possible solution would be to use an implementation using NSUserScriptTask.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10186 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10623 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

8f8f833 commented

I just updated to the NON app store version of 7.4.0 and I am seeing this error for the first time. I also tried the version from the app store and got the same error.

Mac OS 10.15.4

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:19 agerson]:

I just updated to the NON app store version of 7.4.0 and I am seeing this error for the first time. I also tried the version from the app store and got the same error.

Mac OS 10.15.4
This is an unrelated issue we are looking into.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#11240 closed as duplicate.

@StrictLine
Copy link

There should be a useful solution for this issue: I thought, I donate for the app as I used it very often and get punished by a non-functioning version of the product.

Is the only workaround to claim the purchase in the App Store and get a registration key from the vendor?

@dkocher
Copy link
Contributor

dkocher commented Jan 4, 2023

There should be a useful solution for this issue: I thought, I donate for the app as I used it very often and get punished by a non-functioning version of the product.

Is the only workaround to claim the purchase in the App Store and get a registration key from the vendor?

Running the regular version from our website will detect the registration from the Mac App Store and disable the donation prompt.

@StrictLine
Copy link

Ok, cool, thanks for the quick reply! I'll try it.

@StrictLine
Copy link

This works! Awesome.

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

3 participants