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

Mavericks Support #1

Open
DavidBenko opened this issue Jan 13, 2014 · 5 comments
Open

Mavericks Support #1

DavidBenko opened this issue Jan 13, 2014 · 5 comments

Comments

@DavidBenko
Copy link

The script does not seem to work on OS X Mavericks

@dannvix
Copy link
Owner

dannvix commented Jul 26, 2014

Hi David, Thanks for your feedback.
However it seems to work for me on Mavericks (10.9.4)…

Did you try to install this program as a daemon (instruction could be found in the README) and reboot?

@jamesfolk
Copy link

Hello!
Thanks for doing a lot of the foot work to put together a basic keylogger!
I too am having issues having the keylogger run for Mavericks.
I believe i did all the steps correctly.
I have no issues in the build. I changed the output file to a directory where you don't need to log into. I copied the file to /usr/local/bin instead of /usr/local/sbin, because there is no such directory in Mavericks... I also changed the filepath in the launchd plist file and copied it to the directory you specified....
The step that I have questions with is Enabling Access. I believe this has changed since Mavericks. This article describes the change:

http://bit.ly/1I1tRgn

I know this code is for you, but I think it would be great if you could resolve these issues so others can use your code... Thanks!

@dannvix
Copy link
Owner

dannvix commented Mar 19, 2015

Hi @jamesfolk
Thanks for providing such detailed description. The Enabling Access has changed since Mavericks indeed, and I believe it is the problem. However, it worked for me on 10.9.4 as I've mentioned above— I have no idea why.
If my memory serves well, this toy keylogger is required to be packed as an .app to be enlisted in the Accessibility panel… 😞

@jamesfolk
Copy link

Hello! I thought the same, so i renamed the binary file from keylogger to keylogger.app… However i’m thinking that is isn’t as simple as that? It will not allow me to add it as an app that can control my computer…
I’m wondering if there is a special technique you need to do in code to pack it into a *.app file..

On Mar 19, 2015, at 10:23 AM, Shao-Chung Chen [email protected] wrote:

Hi @jamesfolk https://github.com/jamesfolk
Thanks for providing such detailed description. The Enabling Access has changed since Mavericks indeed, and I believe it is the problem. However, it worked for me on 10.9.4 as I've mentioned above— I have no idea why.
If my memory serves well, this toy keylogger is required to be packed as an .app to be enlisted in the Accessibility panel…


Reply to this email directly or view it on GitHub #1 (comment).

@Fingfing
Copy link

Hi!
I found a dirty workaround for this issue:

  1. Open Automator
  2. Choose Application as type
  3. Search for the action "Run Shell Script" and select it
  4. Replace "cat" with the path to the keylogger file (e.g. /usr/local/bin/keylogger)
  5. Save this file with the file format "Application"
  6. Now you can add this Application in the Accessibility panel

Happy logging! :)
@dannvix: Thanks for your work! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants