08-18-2008 10:13 AM
08-18-2008 11:59 PM
Simple answer "because". The definitive answer will be in the sources, but if you don't have a copy, you may be able to get some idea by enabling privilege auditing for OPER success (beware voluminous output). Another option would be to enable privilege auditing for OPER failure, then remove the privilege from the installed image and try running it.
Is this idle curiosity, or has an auditor seen it and assumed it's a hole that needs plugging?
(I agree OPER is a curious privilege to give the telnet client, but if that's the way it comes out of the box, why waste your time trying to work out why?)
08-19-2008 01:08 AM
May be the command after a telnet without options require it ?
I thought that may be it was for giving oper messages. So I enabled them. Worked without the priv. So that's not it.
08-19-2008 04:05 AM
08-19-2008 06:17 AM
08-19-2008 08:00 AM
I assume you noticed in the C.O.V discussion that I created a patch for the Alpha 8.3 version of SGMSHR ?!
Just use that while HP works on the reeal thing?
(If there are discrepancies with the version you use, then for mere money I'll create a similar patch for that. Just point me to an FTP site. :-)
Andy G send some of us an Email yesterday indicating an offical patch has been made a while back and will be made available on ITRC 'real soon now'.
It was kinda fun to create a binary patch for an Alpha image. Luckely I found some bogus code which I could hijack for the solution.
Hein van den Heuvel
HvdH Performance Consulting