Aserver (audio) security file

[Ken Hunter]

You'd think I would learn about hitting Return in these webform prompts.

Here's my scenario:

We have J5600's running HP10.20. We have to create the audio.sec file so that we don't lose audio functionality when we failover from one network interface to the other.

Currently - Here's what we do:
1. /opt/audio/bin/asecure -C
2. /opt/audio/bin -d (allows any connection to the Aserver)

This works very well - however - We clone these workstation disks - for rapid distribution - when we do this - the audio file lists (/opt/audio/bin/asecure -l ) as Corrupted.

This happens when that audio.sec file is created on processor A, remove the disk (or clone it) - then boot up that disk (or its clone) on processors other than A.
Once booted up - with that corrupted file - of course - audio does not work. If we remove and recreate that file on that disk - running on that processor - of course audio behaves.

1. I don't mind recreating that audio.sec file during bootup -however - that /opt/audio/bin/asecure prompts for a password - which can not be piped in via a script. We don't care about the password.

2. Is there a way to configure this so that it will run without the audio.sec file?

3. Is there a way to pipe the password answer into that /opt/audio/bin/asecure executable when run?

4. Does anyone have a better way to do this?

5. Last but most important - thanks in advance :)

[Alex Glennie]

The answers no to 2 & 3 - there have been requests for this functionality : HP ref : CR# JAGab26137 charts such an enhancement request.

As yet I can see know official way to do this ...appologies.

Alex

[Ken Hunter]

Thanks...

I'm pretty sure the asecure is using the machine or cpu serial number as part of - I guess a hashing scheme or something. I'm not sure why this was done. That feature is more an annoyance than anything else.
The inability to move that file across machines is the friction point for us.

Even an officially unsupported beta or voodoo executable is welcome... there's gotta be a better way than recreating that file on each workstation.