033505afd7
To avoid blocking launch, file protection is now updated async for most moved files. Out of paranoia, the database files are also update redundantly on a sync code path. It's still critical that we update permissions recursively for two reasons: 1. Updating a containing directories FileProtection does not affect existing files in that directory. 2. Because we've changed the containers default file protection level (from unspecified to NSFileProtectionComplete), some existing files will have there file protection updated upon launching Signal 2.20. It's not clear to me which files this affects, and I haven't found any relevant documentation, but from observation, it seems to affect any top-level files in the container. Regardless, we're now doing the right thing: after launching 2.20, ensure all file permissions are what we expect. Also removed no-op file protection on legacy db files. They've already been moved by the time this method runs in AppSetup. // FREEBIE |
||
|---|---|---|
| .. | ||
| Example | ||
| fastlane | ||
| protobuf | ||
| Resources/Certificates | ||
| src | ||
| tests | ||
| Utilities | ||
| .clang-format | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
SignalServiceKit
SignalServiceKit is an Objective-C library for communicating with the Signal messaging service for iOS & OS X
To use SignalServiceKit via Cocoapods add the following to your Podfile
pod 'SignalServiceKit', git: 'https://github.com/signalapp/Signal-iOS.git'