Live data from Hacker News

Swift-Keylogger – Keylogger for MacOS written in Swift using HID

github.com

41–50 of 84 posts

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#41
post #5

Earlier quoted context omitted.

This would effectively kill innovation. There is a reason you can't do half the things you do on a laptop on a phone unless you root said phone.

The idea is not to prevent programs doing those things, it's to prevent programs doing those things without user permission .

That's not the problem. The problem is that the whitelist of permissions is limited, fixed, i have no control over it and i can't easily work around it.

I can't create a great way to batch install/update/migrate my phone because everything requires manual approval.

I can't use my own browser or sms app on ios cause it's not allowed by the permissions system.

I can't install a new driver on my phone.

Remember the bs update apple did that broke the home button, forcing people to buy a new phone ? I can't prevent that either.

I'm actually for permissions and sandboxes for most apps. But i want a manual override when i need one.

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#42
post #7

Earlier quoted context omitted.

I'm not sure I buy that requiring user opt-in to camera access is why the Mac app ecosystem is is much larger than that of iOS. Can you elaborate on what apps/innovations would become impossible because of a mandatory opt-in? I cannot think of any...

Everything that is either very low level or is used for deep introspection of other parts of the system. I'm not against sandboxing, but if there should be a way to say i know what i'm installing, go with it. Otherwise you will say good bie to new ways of debugging, alternative drivers, unusual way of routing network packets, innovative UI interactions that are not part of the standards widgets, or anything you haven…

[deleted]

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#43

Earlier quoted context omitted.

You'd have to listen to both, right? Otherwise it'd be the same issue when the user tabs into the password input rather than out of.

No. You could listen for the keydown, but you wouldn't hear it, so you may as well ignore what you can't hear.

You should get a key down event when moving into the password field since you're coming from a field which is not secure.

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#45
post #23

".. Heck, even the $300 chromebook we recently got has 16GB of RAM.. " I don't think sth like that exists.. which one is it?

I mean, you can get the HP Chromebook 13 with 16GB of RAM.. but not for $300.

No shit sherlock !

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#48
post #47

Readme: License MIT Free Software, Hell Yeah! Code (Keylogger.swift, lines 5 & 6): // Created by Skrew Everything on 14/01/17. // Copyright © 2017 Skrew Everything. All rights reserved. Umm.

Please articulate your concerns with this. Is it because it's copyrighted? I think most open source software is under copyright; but the license (MIT in this case) grants end-users certain rights that can be revoked if that license is broken.

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#49
post #47

Readme: License MIT Free Software, Hell Yeah! Code (Keylogger.swift, lines 5 & 6): // Created by Skrew Everything on 14/01/17. // Copyright © 2017 Skrew Everything. All rights reserved. Umm.

Please articulate your concerns with this. Is it because it's copyrighted? I think most open source software is under copyright; but the license (MIT in this case) grants end-users certain rights that can be revoked if that license is broken.

Correct, copyright is what enables the license, free software or otherwise.

Re: Swift-Keylogger – Keylogger for MacOS written in Swift using HID

#50
post #47

Readme: License MIT Free Software, Hell Yeah! Code (Keylogger.swift, lines 5 & 6): // Created by Skrew Everything on 14/01/17. // Copyright © 2017 Skrew Everything. All rights reserved. Umm.

Please articulate your concerns with this. Is it because it's copyrighted? I think most open source software is under copyright; but the license (MIT in this case) grants end-users certain rights that can be revoked if that license is broken.

Hey. Sorry, it appears that I am totally wrong. I just assumed that those statements were totally conflicting, but ten seconds on Google tells me that’s not so.

At least I learned something. My apologies.

Post reply on HN