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

Allow Apple to scan for malware #11

Open
crstauf opened this issue Nov 17, 2022 · 11 comments
Open

Allow Apple to scan for malware #11

crstauf opened this issue Nov 17, 2022 · 11 comments

Comments

@crstauf
Copy link

crstauf commented Nov 17, 2022

No description provided.

@relikd
Copy link
Owner

relikd commented Nov 17, 2022

Could you add a description so that I know whats your issue?
I can only assume you talk about the notarization service. The app is signed but not notarized. The notarization service is for subscribed developers only (paid developer account, which I do not have).

@crstauf
Copy link
Author

crstauf commented Nov 17, 2022

I know that I can bypass this warning, but I typically don't, especially with something optional.

2022-11-17T175857

which I do not have

Understood.

@tchek
Copy link

tchek commented Nov 17, 2022

Right clic and open

@crstauf
Copy link
Author

crstauf commented Nov 17, 2022

I know that I can bypass this warning, but I typically don't, especially with something optional.

@tchek Read: #11 (comment).

@tchek
Copy link

tchek commented Nov 17, 2022

and ??? what's the problem?, personally I don't see any

@crstauf
Copy link
Author

crstauf commented Nov 17, 2022

and ??? what's the problem?, personally I don't see any

I'm not going to bypass the warning. It's up to each individual whether they want to or not.

I personally am very careful with what I install. Others not so much.

@tchek
Copy link

tchek commented Nov 17, 2022

relikd explained to you perfectly

@crstauf
Copy link
Author

crstauf commented Nov 17, 2022

Yes I know, and I responded that I understood. That was the end of it, but then you started telling me how to bypass the warning, which I had already said I knew how to do.

✌️

@tchek
Copy link

tchek commented Nov 17, 2022

Your are welcome 😎

@relikd
Copy link
Owner

relikd commented Nov 17, 2022

I know that it would be better to have the app notarized so that this message does not appear. But as I said, this is only possible with a paid developer account. I am very selective with my installations as well. For me it is especially frustrating that Apple chose this error message.

The message conveys an urgency and security harm, which in reality does not apply. One can easily distribute malware as long as they are paying Apple for the Notarization service. That is, until the malware is found and Apple provides a heuristic for that specific app version and blocks the developer account. Then you would make changes to the app so that the heurstic does not match anymore and create a new account.
On the other hand, the message tells you that it is dangerous to run unnotarized apps. Which is also not true (at least in most cases).

With that behavior Apple forces developers to sign up for a paid account so they can publish software without that message banner. And most do because its easier and not that expensive. But that is one of the reasons I refuse to pay money to Apple. I just hate the dark pattern to be silently ignored. Apple is slowly building a closed garden where you can only publish if you pay. Similar to the iOS App Store.

I will not say that I wont ever publish a notarized version, but honestly, I get more frustrated each year. If I do, I will create an AppStore version as well though.

@tchek
Copy link

tchek commented Nov 17, 2022

Appalling behavior on the part of Apple but we know the house

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

3 participants