In my previous article about secure coding in Swift, I discussed basic security vulnerabilities in Swift such as injection attacks. While injection attacks are common, there are other ways your app can be compromised. A common but sometimes-overlooked kind of vulnerability is race conditions.
From minimizing pointer use to strong type checking at compile time, Swift is a great language for secure development. But that means it’s tempting to forget about security altogether. There are still vulnerabilities, and Swift is also enticing to new developers who haven’t yet learned about security.
The main purpose of a digital signature is to verify the integrity of some information. For a simple example, let’s say you had a file that was transferred over the network and you want to check that the entire file was transferred correctly. In that case, you would use a checksum.
Why would you want to hack your own app? To find the security flaws before someone else does—and before your users’ data is compromised.