[GH-ISSUE #134] enhance code security #109

New issue

Open

opened 2026-05-05 04:56:07 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 04:56:07 -06:00

Owner

Originally created by @maxheld83 on GitHub (Jan 8, 2019).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/134

I love the project and the devs generosity, but this being a full-accessibility keylogger of sorts, I wonder whether the devs could heighten security around here (e.g. by only allowing GPG-signed commits) or just generally write a sentence or two as to security design of the program.
Maybe I'm just being paranoid.

also see security concern in #133

Originally created by @maxheld83 on GitHub (Jan 8, 2019). Original GitHub issue: https://github.com/keycastr/keycastr/issues/134 I love the project and the devs generosity, but this being a full-accessibility keylogger of sorts, I wonder whether the devs could heighten security around here (e.g. by only allowing GPG-signed commits) or just generally write a sentence or two as to security design of the program. Maybe I'm just being paranoid. also see security concern in #133

gitea-mirror commented

2026-05-05 04:56:15 -06:00

Author

Owner

@coolaj86 commented on GitHub (Oct 11, 2021):

Yes.

I'm looking around for the "Pay me Money" button because this is exactly the kind of tool that I expect to pay for and paying gives me a sense of security that there's a truly responsible party who passes the bare minimum requirements to sign up for merchant services with PayPal, FastSpring, 2Checkout, or whatever.

@coolaj86 commented on GitHub (Oct 11, 2021): Yes. I'm looking around for the "Pay me Money" button because this is exactly the kind of tool that I _expect_ to pay for and paying gives me a sense of security that there's a truly responsible party who passes the bare minimum requirements to sign up for merchant services with PayPal, FastSpring, 2Checkout, or whatever.