Sending SIGUSR1 to a process
site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=2019; t=1706512029; i=@uni-bremen.de; bh=H4QY6tJMMCI/yjecqJpnxS+rsF0dJozWrCr90Ce5Do8=; h=From:Date:To; b=KvdMBkM0r8vHR8MeZp1QnaKaRv+2PxeDX9PVgGycdfys5s4USygZ+AfV8TgQ1J2Ip xq5eHRmS4aarzgk1egGHNhqwhFKa53bjCDKWX0rILZknLTXBCu/sX3p4TCpp9PBUFv dBBc8VTRxyF8wu1quY4JsktGSfpW0J4qNNy7J/Mg9P/ACtozPrGBpAvgXA9RlmCvxL RX5/91CQ5xRMF3Z4kLbHWqTjHxQPVg5x/TRcsipRxYVVAhCPmiKKj6SEcbuU9xX6qI lvXKOh+RylM36JaiubdYXlzyW5lQCVLjUjwLAHHss+xHnGJfowFXjQaeZmTaOafx+w gMn93NT6DunPQ== IIRC, one process cannot send a Unix signal to another one. At least, not any more, and not without special privileges. But would it be possible for a user to send a SIGUSR1 (using 'kill -30 <pid>' on the command line) to a process they own? I couldn't find information about that. In fact, in the developer docs i couldn't find any info about Unix signals, what is possible or not under the new security regime in macOS. (I can't remember where i read about the new limitations regarding signals under the new security regime.) Any info will be highly appreciated. Best regards, Gabriel _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com smime.p7s
participants (1)
-
Gabriel Zachmann via Cocoa-dev