this post was submitted on 02 Oct 2023
23 points (96.0% liked)

Apple

17484 readers
81 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:
  1. No NSFW Content
  2. No Hate Speech or Personal Attacks
  3. No Ads / Spamming
    Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago
MODERATORS
MichelleG@lemmy.world
RoyalEngineering@lemmy.world
thisisdee@lemmy.world
23
macOS Sonoma + GPG Mail: Lacking MailKit capabilities prevents release (gpgtools.com)
submitted 1 year ago by convene_depth@lemmy.ml to c/apple_enthusiast@lemmy.world
1 comments fedilink hide all child comments
 

Key points: Missing API functionalities which block the release of GPG Mail as a Mail Extension

Four of the major functionalities missing in the first official release of macOS Sonoma are:

Entire message data is not always passed to the extension making processing the encrypted message impossible
Reliably encrypted drafts
Support for setting the default state of the sign and encrypt button in compose windows which can lead to dangerous side-effects
Sign and encrypt button could go out of sync with internal state, if keyring changes are detected

Probably a good time to reach out to Apple: https://www.apple.com/feedback/mail.html

top 1 comments
sorted by: hot top controversial new old
[–] shadycomposer@lemmy.world 2 points 1 year ago

Honestly I'm not sure if I fully understand their points:

  1. "Entire message data is not always passed..." - so sometimes it works, while sometimes doesn't? At a glance MailKit seems to have the necessary hooks (MEMessageSecurityHandler) though i have not used it myself so can't say if it works as expected or not.

  2. When they say they'll release a version with 14.1 (or 14.0.1), do they have confirmation from Apple that the said blockers will be resolved in that release? If they need more time to implement this it's fair, but the wording of the 'key points' sounds like there are blockers out of their control, then how could they commit a release date without Apple's commitment?