[Info-vax] AXIS2/C, gSOAP

[VAXman- at SendSpamHere.ORG]

In article <i392db$dvg$1 at news.albasani.net>, Jan-Erik Soderholm <jan-erik.soderholm at telia.com> writes:
>On 2010-08-03 14:04, VAXman- @SendSpamHere.ORG wrote:
>
>> The VMSINSTAL issue DID affect the former products...
>> ... I still haven't seen even a release note mention.
>>
>
>The 8.4 Release Notes say :
>
>"3.4 HP Code Signing Service for OpenVMS V8.4
>On OpenVMS Version 8.4 and later, PCSI and VMSINSTAL based kits are
>signed using the HP Code Signing Service (HPCSS). The signature
>appears as a separate file. For example, DXDA053.A will have the
>signature file as DXDA053.A_HPC. The HPBINARYCHECKER provided along
>with operating system on Version 8.4 and later is used to validate
>these kits. For more information, see HP OpenVMS Version 8.4 New
>Features and Documentation Overview."
>
>And the 8.4 New Features and Documentation Overview says :
>
>....
>"From OpenVMS Version 8.4, a new product, HPBinarychecker, will
>get installed on OpenVMS systems to validate the kits signed using
>HPCSS. VMSINSTAL and PCSI are enhanced to use the validator."
>
>
>Now, if one is not specificaly looking/searching for that... :-)

But WHERE does it state that they HORKED VMSINSTAL? such that third-parties
can no longer use it as it was used previously???  It states that HP's PCSI
and VMSINSTAL kits are signed, and that "The HPBINARYCHECKER provided along
with operating system on Version 8.4 and later is used to validate these 
kits."  HPBINARYCHECKER, for those so concerned about those VMSINSTAL kits
they've downloaded, sounds like a standalone validation procedure.  Putting
it IN VMSINSTAL with a COMPLETE AND TOTAL DISREGARD for third-parties using
VMSINSTAL is and was unconscionable.

Sorry but I'm not relenting on this. 
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.