FROM : Finlay Dobbie
DATE : Tue Jan 14 08:33:01 2003
On Tuesday, January 14, 2003, at 12:54 am, Chris Reed wrote:
> Yes, you can. But it is a system-wide config option. Take a look at
> the /etc/authorization config file. It has some "documentation" as
> comments at the top of the file.
>
> Alternatively, you need a separate process that you launch the first
> time the user authorizes and stays around until you explicitly quit.
> Then you can send it messages requesting that it run /bin/kill any
> time you need. The button to deauthenticate would cause this process
> to exit.
Or you could fix your code so you do authorization the "correct" way
and authorize against a non-expiring right. AuthSample shows this, as
does ThemeChanger (www.clichesw.com).
-- Finlay
DATE : Tue Jan 14 08:33:01 2003
On Tuesday, January 14, 2003, at 12:54 am, Chris Reed wrote:
> Yes, you can. But it is a system-wide config option. Take a look at
> the /etc/authorization config file. It has some "documentation" as
> comments at the top of the file.
>
> Alternatively, you need a separate process that you launch the first
> time the user authorizes and stays around until you explicitly quit.
> Then you can send it messages requesting that it run /bin/kill any
> time you need. The button to deauthenticate would cause this process
> to exit.
Or you could fix your code so you do authorization the "correct" way
and authorize against a non-expiring right. AuthSample shows this, as
does ThemeChanger (www.clichesw.com).
-- Finlay
| Related mails | Author | Date |
|---|---|---|
| Simone Manganelli | Jan 13, 15:19 | |
| Chris Reed | Jan 13, 17:01 | |
| Finlay Dobbie | Jan 14, 08:33 | |
| Simone Manganelli | Jan 14, 15:43 | |
| Finlay Dobbie | Jan 14, 15:51 | |
| Tobias Peciva | Jan 14, 16:18 | |
| Simone Manganelli | Jan 15, 12:58 |






Cocoa mail archive

