| Simple Security |
| QTIPS - Hiding Symbolic Source Code |
| Using One Dictionary With Multiple Tables - Aaron Kaplan - SoftMart Inc |
| Bugs and PCs - Xlate with Multipart Keys |
| VROOM - Window Processing II |
| Indexing on Xlates |
| Collector Windows |
| QTIPS - Reusing Symbolics in Windows |
| QTIPS - Hiding Symbolic Source Code |
| Make.Index |
| QTIPS - Btree.Extract |
| !File Records |
| Index Sub Revisited |
| QTIPS - Stop Lists |
| Reader's Clinic - Stop Lists |
| Utility Diskette # 4 |
| QTIPS - Manipulating XREF formulae. |
| Make.Index |
| !File Records |
| Relational Indexes - Reordering |
| Referential Integrity |
| QTIPS - Deleting Master Relationally Indexed Records |
| Utility Diskette # 4 |
| QTIPS - @Date.Format |
| @ATTACK - @Date.Format |
| QTIPS - Short Cut Implicit Formatting |
| Utility Diskette # 4 |
| Creating Your Own Background Processes |
| @ATTACK - @Last.Select.Process |
| Reader's Forum |
| QTIPS - Menu Item Pre-Processing |
| Reader's Clinic - Fixing %Windows% Using Depend.Update |
| QTIPS - Updating Indexes |
| How Indexes Are Updated |
| REVMEDIA Revisted |
| SecureUser |
| VERBatim - V25 |
| @ATTACK - @Files.System |
| Advanced Revelation Initialisation Sequence (Overview) by Mike Pope |
| REVMEDIA Revisted |
| QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages |
| @ATTACK - @Lower.Case |
| @ATTACK - @Upper.Case |
| Sorting out Collation Sequences by Mike Pope |
| Reader's Clinic - Different Id Same Record |
| Reader's Clinic - Scaled Masked Decimal Conversions |
| Base Conversions |
| User Defined Conversions |
| Reader's Forum - Numeric Precision in R/Basic - Hal Wyman |
RevMedia FKB
| Document | V2I7A4 |
| Title | Simple Security |
| Keywords | SECURITY DICTIONARY INDEXING |
| Text | At the Advanced Indexing Training SESSION one of the topics discussed was that of how dictionary structure relates to indexing The following fields were documented < 6 > BTREE flag 1 if the item has a btree index otherwise false < 21 > Used when indexing on symbolics to tell the indexing system what additional items are involved in the construction of this symbolic Used when indexing XLATES (see Vol 2 Issue 4) < 22 > XREF information Contains name of symbolic used to cross reference index this field This field may be multi valued allowing multiple XREFs per item if required < 23 > RELATIONAL INDEX Contains the pointer to the target file / field in format FILE*FIELD*SORT_ORDER < 24 > RELATIONAL INDEX This records where this field is maintained FROM in the format FILE*FIELD < 25 > RELATIONAL INDEX Allow amendment flag If this field is set to 1 the only process allowed to update the field will be the relational index logic All other attempts to update the field will be rejected If it is set to 0 the user will be allowed to update the field The same functionality may be obtained by USING System LABELLED Common (See Vol 2 Issue 1) < 26 > Case Conversion Flag If set to 1 index values will not be converted to uppercase if 0 all values indexed will be upper case During the discussion a delegate asked if field 25 (allow amendment) could be used anywhere other than in a related index ie could ANY field be protected FROM amendment simply by SETTING this flag to 1 Investigation revealed that it could Regardless of whether INDEXES are installed on a file or not SETTING field 25 of a dictionary item to 1 prevents that field from being amended without either unsetting the flag or manipulating labelled common as documented above To accomplish this the system attaches SI MFS to the file This could therefore be used to provide a very simple security feature preventing unauthorised users FROM modifying individual fields (Volume 2 Issue 7 Page 7) |
Page last modified: 30/01/03