![]() ![]() Instead of a “code signature mismatch”, Little Snitch’s connection alert now informs that “the program has been modified”. When editing a rule, Little Snitch Configuration no longer shows a checkbox titled “requires valid code signature” but instead one that is titled “check process identity” (or if the rule is for any process: “apply to trusted processes only”). This change leads to a different terminology. (There’s still a warning if a process is not signed, but only to inform you about a possible anomaly.) That is usually still the code signature but for programs that are not code signed, Little Snitch now computes a secure hash over the program’s executable. The focus is now on checking for modifications with the best means available. The focus was therefore on a program’s code signature.īeginning with version 4.3, Little Snitch can always check whether a program has been tampered with, even if it’s not code signed at all. Programs without a code signature could not be validated and Little Snitch warned accordingly. ![]() Previous versions required a program to have a valid code signature in order to be able to detect illegitimate modifications later on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |