Re: protecting passwords in properties
Re: protecting passwords in properties
- Subject: Re: protecting passwords in properties
- From: Jeremy Reichman <email@hidden>
- Date: Mon, 24 Mar 2008 09:06:52 -0400
- Thread-topic: protecting passwords in properties
On 3/20/2008 10:00:30 PM, "Vince Angeloni" <email@hidden> wrote:
> I'm sticking to my suspicious scripting questions... ; )
>
> At any rate, I would like to use to the unix cmd 'shutdown' to bounce my kids
> off the computer when they exceed their time, and they don't pay attention to
> the more gentle system event "log out" I use previously to encourage them to
> get off the computer. To use this, I have to use an applescript 'with
> administrator privileges', so if I want this script to run on the kids'
> accounts, I'll need to put my admin account name and password into a property.
> I understand this is not secure.
>
> I am thinking of leaving the properties empty when I compile and when the
> script first runs, it will ask for my admin account name and password and then
> place it into the property, only after having run it through the unix cmd
> 'openssl' to encrypt it. Thus, the property will only show the encry rd for
> the openssl command itself will be derived from an applescript which generates
> it by picking certain letters from a string of text stored in a temporary
> variable.
>
> I am assuming that since this is compiled as a run-only application, the admin
> account password stored as a property will be encrypted and my password for
> openssl will be hidden in the compiled run-only applescript code. Are there
> any obvious holes here that I am missing?
Joining in what sounds like mid-discussion, I am taking a step back and
wondering if you've exhausted the possibilities already presented by
Parental Controls in System Preferences.
In Leopard, there are a lot of new options, including weekday and weekend
time limits, and a "bedtime" setting to prevent access separately for school
nights and weekends. You can even have these settings controlled from
another computer.
If that really weren't sufficient or you can't upgrade the kids' computer to
Leopard, I would consider doing something with a cron job or launchd
(launchd being much improved in Leopard), since you can have an associated
script executing with system privileges all of the time. Then, you don't
need to store a password.
--
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden