× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MI400
  3. March 2005

Re: How will new system state restrictions work? was: Attention Users of *SYSTEM State


It may be just as Bruce said, a restriction on the restoration of non-IBM system state programs. Kind of like an internal extension of the QVFYOBJRST system value that controls object restoration (can restrict user state programs without signatures). The system value was introduced in V5R1. Object signing may have began earlier (V4R5 ?).

CHKOBJITG might also be changed to report the new violation, but verifying signatures at program activation does not seem very practical. 



Keith


Steve Richter wrote: 
-----Original Message-----
From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx]On
Behalf Of Bruce Vining
Sent: Monday, March 07, 2005 11:16 AM
To: MI Programming on the AS400 / iSeries
Subject: [MI400] Attention Users of *SYSTEM State


Within two years IBM plans to remove the i5/OS ability to restore system
state programs not digitally signed by IBM. Only programs provided by IBM
will be able to use system state. Any other system state programs will have
to be changed to use supported interfaces accessible from user state.



So what is the speculation on how "Only programs provided by IBM will be
able to use system state." will be implemented?  From the statement, there
will still be a system state.  Will the bit settings in the system object
header continue to control whether a program runs in system state or not?
Will SST continue to be used to set those bits?  Is the digital signature
something new to the system?

-Steve

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.