OctetView
0x00000…00100 (0, 0, 0) Sector 03854130333835 ┆ A0385A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00fcfeffff00 ┆ |~ | ` | ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x42, d01=0x22, d02=0x41, ptr=(55,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x42, d01=0x31, d02=0x41, ptr=(40,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x42, d01=0x36, d02=0x41, ptr=( 1,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x42, d01=0x37, d02=0x41, ptr=(67,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x42, d01=0x39, d02=0x41, ptr=(69,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x42, d01=0x40, d02=0x41, ptr=(73,0, 0), d05=0x00}
0x00324…00340 42 40 41 33 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆B@A3 ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 ┆ $┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 8 7 Q? > 7 d N N ~<) 0u &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; B1A 2 C h x h V W O 8 :g g 4231A h b | {C < ; 1 u! u uW f 9 8 : t xx_ 8 g : f N N ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentHead {hdr=WangSectHead {next=( 1,0, 1), len=0xff, h3=41423641}, f00=»4236A «, f01=»LKSAA tech.prop. part 1 «, f02=»jaa «, f03=»GT «, f04=»afsnit 5 remote conn «, f05=31-10-83 14:00, f06=» «, f07=»04 «, f08=» 541 «, f09=01-11-83 11:03, f10=» «, f11=»00 «, f12=» 8 «, f13=01-11-83 11:08, f14=05-03-84 13:04, f15=»0385A «, f16=» 2 «, f17=» «, f18=»04 «, f19=» 8 «, f20=» 556 «, f21=» «, f22=» «, f99=020010000110462710110060aaca15050000000000000138030600df}
0x01100…01200 (1, 0, 1) WangDocumentBody
[…0x4…]
0x01600…01700 (1, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x6…]
0x01f00…02000 (1, 0, 15) Sector 00000000000000 ┆ ┆
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0xf…]
0x03000…03100 (3, 0, 0) Sector 03018f00424041 ┆ B@A-down to such a level that all SW modules can be identified taken all functional areas defined in section 2.2 and 4.1.1 into account. of a normal package design process. 4 PACKAGE DESIGN (4.1) PACKAGE OVERVIEW Section 4.1 of the packag┆
0x03100…03200 (3, 0, 1) Sector 0302ff00424041 ┆ B@A 1 (4.2.x.2) Software Structure This section shall contain a description which identifies all software components to be implemented (Refer 4.1.2). (4.2.x.3) Data Flow and Contro┆
0x03200…03300 (3, 0, 2) Sector 0303ff00424041 ┆ B@Al Logic Data flow and control logic related to major transactions within a subpackage shall be described. The mandatory tool to specify flow/logic is HIPO for sequential processing. Where functions are made up of complex algorithms or decisions ┆
0x03300…03400 (3, 0, 3) Sector 0304ff00424041 ┆ B@Athe HIPO charts may be supplemented by flowgrams, structured pseudocode and/or decision table. Where concurrent processing exist blockdiagrams shall be used to specify communication between software components. (4.2.x.4) Subpackage Data This┆
0x03400…03500 (3, 0, 4) Sector 0305ff00424041 ┆ B@A section shall define data which are pertinent to the sub-package only. Package data or common data shall be defined in 4.1.4 and 4.1.5. (4.2.x.5) Interfaces This section shall specify interfaces between subpackages within the package. Package┆
0x03500…03600 (3, 0, 5) Sector 03068300424041 ┆ B@A interfaces or external interfaces shall be defined in the appropriate ICDs and referenced/defined in section 4.1.6. 2.6.3onal break-down shall be continued to the level where all common functions can be isolated. (4.1.2) Software Structure ┆
0x03600…03700 (3, 0, 6) Sector 0000fc00424041 ┆ | B@A Configuration Control Configuration Control is described in Volume II, section 7.3 2.6.4 Project Management An Automated Project Management System including critical path analysis is available on the CR16 and can be offered as an option. efi┆
[…0x1…]
0x03800…03900 (3, 0, 8) Sector 0309ff00424041 ┆ B@Aure shall be presented by a chart which shows the software break-down. (Similar to chart presented in section 4.1.1). (4.1.3) Data Flow and Control Logic Data flow and control logic related to major transaction within a package shall be descri┆
0x03900…03a00 (3, 0, 9) Sector 030aff00424041 ┆ B@Abed to the sub-package level. The functional flow must give the normal flow (as 2.2) and the special flow (2.3). The tools to document flow/logic are block diagrams for process synchronization/communication and HIPO for sequential processing. ┆
0x03a00…03b00 (3, 0, 10) Sector 030ba300424041 ┆ # B@A (4.1.4) Common Data Elements (Internal) This should identify common data element (but not give detailed layout in order to make 4.1.5 more readable). oftware 2) Development Software The system software is defined to consist of the fol┆
0x03b00…03c00 (3, 0, 11) Sector 030cff00424041 ┆ B@A 1 (4.1.5) External Data Elements This should identify data shared with other packages which are defined in Data Def. Doc. (4.1.6) Interfaces The section shall define external┆
0x03c00…03d00 (3, 0, 12) Sector 030dff00424041 ┆ B@A interfaces as well as software package to package interfaces (excl. DAMOS, IOC, CSF, and MMS). At minimum shall be references to the appropriate ICDs shall be included. Sub-package interfaces shall, furthermore, be identified but not specified in┆
0x03d00…03e00 (3, 0, 13) Sector 030eff00424041 ┆ B@A details, as this shall take place in section 4.2.x.5. General Commments to 4.1.4, 4.1.5, and 4.1.6 In order to obtain a selfcontained and readable document it may be necessary to include detailed information in section 4.1.4 - 4.1.6. It shall h┆
0x03e00…03f00 (3, 0, 14) Sector 030fff00424041 ┆ B@Aowever be emphasized that the master source for definition of data and package interfaces are the AMSS data definition document and the AMSS software interface control document. (4.2.x) Sub-package Specifications This section shall expand the ┆
0x03f00…04000 (3, 0, 15) Sector 0300ff00424041 ┆ B@Asubpackage design, as described in section 4.1 to a level where all modules (less than 250 source statements, refer SRS) are identified and the functions defined. (4.2.x.1) Functional Specification This section shall contain a functional break┆
0x04000…04100 (4, 0, 0) Sector 0401ff00424041 ┆ B@A 1 2.6.2.5 Package Design Standard The following pages are an example of a normal package design process. 4 PACKAGE DESIGN (4.1) PACKAGE OVERVIEW Section 4.1 of the packag┆
0x04100…04200 (4, 0, 1) Sector 0402ff00424041 ┆ B@Ae specification has at package level the same mission as chapter 4 in the SDS at system level. In total 4.1 gives the concurrent and sequential processing within the package with clear definition of the role of each sub-package which are described┆
0x04200…04300 (4, 0, 2) Sector 0403ff00424041 ┆ B@A more detailed in section 4.2.x. (4.1.1) Functional Specification This should be the first step in the analysis. The package functions desolved in section 2.2.1 and 2.2.2 should be broken down to the level functional which justifies allocation┆
0x04300…04400 (4, 0, 3) Sector 0404ff00424041 ┆ B@A of the subpackages described further in section 4.2.x. A B C ┆
0x04400…04500 (4, 0, 4) Sector 0405c700424041 ┆ G B@A Common functions for the package to deal with changing situations e.g. o┆
0x04500…04600 (4, 0, 5) Sector 0406ff00424041 ┆ B@A 1 Where common functions exist within a package the functional break-down shall be continued to the level where all common functions can be isolated. (4.1.2) Software Structure ┆
0x04600…04700 (4, 0, 6) Sector 0407ff00424041 ┆ B@A This section describes the allocation of functions onto processes, shared procedures (between two processes), monitor procedures (only for CSF, SSC, and DAMOS) or co-routines. Based on the above software component types sub-packages shall be defi┆
0x04700…04800 (4, 0, 7) Sector 0308ff00424041 ┆ B@Aned. For each of the sub-packages the following elements shall be contained. 1) Functions allocated to the subpackage (refer 4.1.1). 2) Software structure which corresponds with the functional break-down of section 4.1.1. The software struct┆
0x04800…04900 (4, 0, 8) WangDocumentBody
[…0x23f…]
0x28800…28900 (40, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(40,0, 9), len=0xff, h3=41423141}, f00=»4231A «, f01=»LKSAA PROPOSAL - VOL II «, f02=»jaa/kw «, f03=»JAL (Part 1) «, f04=»fra kptl. 2.7 «, f05=31-10-83 12:00, f06=» 1 «, f07=»01 «, f08=» 1215 «, f09=13-06-84 15:43, f10=» «, f11=»02 «, f12=» 30 «, f13=13-06-84 16:28, f14=26-06-84 11:18, f15=»0385A «, f16=» 64 «, f17=» 3 «, f18=»31 «, f19=» 1016 «, f20=» 3698 «, f21=» «, f22=» «, f99=120010000110462710110260aaca15050000000000000132033f01df}
0x28900…28a00 (40, 0, 9) WangDocumentBody
[…0xc…]
0x29600…29700 (41, 0, 6) Sector 0000d000422241 ┆ P B"Alaved from the display; this is a built-in feature of the word processing system. As for the duty center, a dynamic assignment of equipment can be done allowing for flexibility and increased work load. software module would ensure that incoming tex┆
0x29700…29800 (41, 0, 7) Sector 00000000000000 ┆ ┆
0x29800…29900 (41, 0, 8) WangDocumentBody
[…0x12…]
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cff00423141 ┆* B1A 1 LKSAA - VOLUME II Issue 1.4 Part 1 SYS/84-04.24 TECHNICAL PROPOSAL ┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0d1700423141 ┆* B1A Page =2#<! <6 M1' R+/M )M2&MP'I:^=~ B;/IMC'!e=6 *(=~ RN/C}/:]=2#<:b= Rc/! <6 Ch/! <6 M)(:^=~ Bt/I:\=2#<C /:]=2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff00423141 ┆* B1A 1 2.7 SECURITY 2.7.1 Security Assurance Via Hardware 2.7.1.1 Principal Hardware Architecture The principal hardware architecture is shown on figure 2.7.1-1. The principal co┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0fff00423141 ┆* B1Amponents are: - PU RAM The main memory of the system. It is only accessible by the CPU's and only via the MAP. The PU RAM consists of up to 2M words of 16 bits. - CPU Up to 5 central processes units. CPU's may access PU RAM, CU RAM and ┆
0x2af00…2b000 (42, 0, 15) Sector 2808ff00423141 ┆( B1APeripheral Processors via MAP. - Peripheral Module A peripheral module controls a device or a set of similar devices (disks, communication lines etc.) It consists of CU RAM and a Peripheral Processor. - CU RAM Random access memory in a p┆
0x2b000…2b100 (43, 0, 0) WangDocumentBody
[…0x1d…]
0x2ce00…2cf00 (44, 0, 14) Sector 2c0fff00421841 ┆, B Aon the other hand can record the events as they occur, provide a record of all events pertinent to the function without interfering with the operator task, and without being interspersed with operator commands. Furthermore the VDU- printer concept a┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00e500421841 ┆, e B Allow for a modern man-machine interface with various levels of operator support e.g. menu selection, fill in the blanks, and help functions, all of which provide for on the job training and support to the uninitiated user. cally provide the 3 functi┆
0x2d000…2d100 (45, 0, 0) WangDocumentBody
[…0x9f…]
0x37000…37100 (55, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(55,0, 1), len=0xff, h3=41422241}, f00=»4222A «, f01=»LKSAA PROPOSAL - VOL II «, f02=»ba «, f03=»RH «, f04=»kap. 4 - 4.4.1 «, f05=30-10-83 11:45, f06=» 1 «, f07=»23 «, f08=» 5229 «, f09=08-03-84 21:57, f10=» «, f11=»02 «, f12=» 61 «, f13=08-03-84 22:05, f14=09-03-84 11:29, f15=»0385A «, f16=» 7 «, f17=» 3 «, f18=»34 «, f19=» 160 «, f20=» 14522 «, f21=» «, f22=» «, f99=700010000110462710110260aaca15050000000000000138032e00df}
0x37100…37200 (55, 0, 1) WangDocumentBody
[…0xc6…]
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41423741}, f00=»4237A «, f01=»LKSAA vol. II part 1 «, f02=»jaa «, f03=»FE «, f04=»7 - 7.12 «, f05=31-10-83 14:03, f06=» 4 «, f07=»27 «, f08=» 20358 «, f09=20-06-84 15:13, f10=» «, f11=»00 «, f12=» 8 «, f13=20-06-84 15:20, f14=26-06-84 11:19, f15=»0385A «, f16=» 49 «, f17=» 8 «, f18=»32 «, f19=» 1020 «, f20=» 34518 «, f21=» «, f22=» @ «, f99=443002000110462710110060aaca15050000000000000138032e01df}
0x43900…43a00 (67, 0, 9) WangDocumentBody
[…0x1e…]
0x45800…45900 (69, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(69,0, 9), len=0xff, h3=41423941}, f00=»4239A «, f01=»LKSAA - vol. II part 1 «, f02=»jaa «, f03=»GT «, f04=»6 - 6.1 «, f05=31-10-83 14:06, f06=» «, f07=»12 «, f08=» 2333 «, f09=13-06-84 15:45, f10=» «, f11=»03 «, f12=» 125 «, f13=13-06-84 16:33, f14=26-06-84 11:20, f15=»0385A «, f16=» 14 «, f17=» 3 «, f18=»08 «, f19=» 236 «, f20=» 17434 «, f21=» «, f22=» «, f99=410010000110462710110260aaca15050000000000000138034b00df}
0x45900…45a00 (69, 0, 9) WangDocumentBody
[…0x36…]
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41424041}, f00=»4240A «, f01=»LKSAA Vol. II part 1 «, f02=»jaa «, f03=»FE «, f04=»2.3 - 2.6 «, f05=31-10-83 16:14, f06=» 1 «, f07=»01 «, f08=» 1202 «, f09=21-06-84 17:46, f10=» «, f11=»00 «, f12=» 5 «, f13=21-06-84 17:46, f14=26-06-84 11:20, f15=»0385A «, f16=» 77 «, f17=» 8 «, f18=»48 «, f19=» 1284 «, f20=» 17819 «, f21=» «, f22=» 0 «, f99=631045000110462710110060aaca15050000000000000138037801df}
0x49100…49200 (73, 0, 1) WangDocumentBody
[…0x6…]
0x49800…49900 (73, 0, 8) Sector 4909ff00423941 ┆I B9A 1 The CR16 is in this configuration equipped as a compact desk top integrated work station, which includes an intelligent terminal, one mini-Winchester rigid drive and one mini flopp┆
0x49900…49a00 (73, 0, 9) Sector 490aff00423941 ┆I B9Ay disk drive. The Crypto System is equipped with one XTA for interface to the papertape reader, one XTA for interface to the printer and two XTA for communication with the Central Communication System. This communication includes requests for ke┆
0x49a00…49b00 (73, 0, 10) Sector 490bc400423941 ┆I D B9Ay allocation to the Cryptos and status information to be exchanged between the two systems. The paths for data to/from cryptos and the paths for crypto keys is depicted in figure 6.2-2. SYS/84-03-01 Part 1 TECHNICAL PROPOSAL ┆
0x49b00…49c00 (73, 0, 11) Sector 490c9f00423941 ┆I B9A 1 Figure 6.1.-1 Crypto Control System ^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x49c00…49d00 (73, 0, 12) Sector 490da000423941 ┆I B9A 1 Figure 6.1-2 Paths for Keys and Data 6 CRYPTO SYSTEM .................................... 275a 6.1 CRYPTO CONTRO┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00423941 ┆I B9A 1 6.1.1 System Interface to Off-Line Cryptographic Equipment The information provided in the request for proposal is insufficient to evaluate this interface. This proposal is base┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00423941 ┆I B9Ad on the assumption that the 5-bit bytes of the keys are transferred under control of some control signals. Additional information like the number of the key and the number of the byte in the key is reported in parallel with the key data. The key in┆
0x49f00…4a000 (73, 0, 15) Sector 3508ff00423941 ┆5 B9Aformation is only transferred once to the cryptos each time the Central Communication System requests a new key to be used. A special XTA is developed for this purpose. The Crypto System is equipped with 4 XTAs for interface to 4 off line crypto's┆
0x4a000…4a100 (74, 0, 0) Sector 4a01fd00423941 ┆J } B9A........... 280b 6.4 CRYPTO SECURITY .............................. 280b 6.5 CRYPTO RACKS ................................. 280b 6.5.1 Racks for Off-line Cryptos ............... 280b 6.5.2 Racks for On-line Cryptos ................ 280c ! ┆
0x4a100…4a200 (74, 0, 1) Sector 4a02ff00423941 ┆J B9A 1 6 CRYPTO SYSTEM Christian Rovsing A/S's extensive experience in designing and implementing crypto system will ensure a well functioning LKSAA. Christian Rovsing A/S has deli┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00423941 ┆J B9Avered a very cost effective crypto system as part of the FIKS system for the Danish MOD. In this system, several trunk lines share only one crypto device, which acts as a multiplexor between the various trunks. Although AA's outline of the crypto sy┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00423941 ┆J B9Astem for LKSAA is different, we believe that we in close cooperation with AA can design a well functioning and secure crypto system. The Crypto System consists of the Crypto Control System, 4 Off Line Cryptos and 90 On Line Cryptos. The purpose ┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00423941 ┆J B9Aof the Crypto Control System is to store the crypto key's, and make the keys available to the crypto units under control of the Central Communication System. The procedure by which the Central Communication System requests keys to be sent to the c┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00423941 ┆J B9Aryptos is found in section 2.1.5.2. 6.1 CRYPTO CONTROL SYSTEM HARDWARE The proposed Crypto Control System is a separate system configured around a dualized X-net (Non-tempest). A schematic of the Crypto Control System is shown in figure 6.1-1. ┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00423941 ┆J B9A For a general description of the X-net and X-net components refer to section 2.1.2. The process capacity in the CRYPTO System is provided by a work stations, called X-net Administrator, XNA. This work station is based on the CR16 Terminal. For┆
0x4a700…4a800 (74, 0, 7) Sector 49084800423941 ┆I H B9A redundancy purposes the Crypto System is equipped with 2 XNA's. ┆
0x4a800…4a900 (74, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(74,0, 9), len=0xff, h3=41423941}, f00=»4239A «, f01=»LKSAA - vol. II part 1 «, f02=»jaa «, f03=»GT «, f04=»6 - 6.1 «, f05=31-10-83 14:06, f06=» «, f07=»12 «, f08=» 2333 «, f09=04-03-84 12:20, f10=» «, f11=»02 «, f12=» 65 «, f13=04-03-84 12:23, f14=05-03-84 12:58, f15=»0385A «, f16=» 11 «, f17=» 2 «, f18=»21 «, f19=» 216 «, f20=» 12262 «, f21=» «, f22=» «, f99=100010000110462710110460aaca15050000000000000138033900df}
0x4a900…4aa00 (74, 0, 9) Sector 4a0a0b00423941 ┆J B9A J J J I I I I 5 5 4 4 4 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprett┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00423941 ┆J B9A 1 Issue 1.1 LKSAA - VOLUME II SYS/84-03-01 Part 1 TECHNICAL PROPOSAL ┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0c2300423941 ┆J # B9A Page ]=~ BC.MP- R5.> IM)-:^=~ BC.C~.M_* RM.> I:^=~ B[.Mr)Cp.:]=~ Bp.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00423941 ┆J B9A 1 1 6 CRYPTO SYSTEM .................................... 275a 6.1 CRYPTO CONTRO┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00423941 ┆J B9AL SYSTEM HARDWARE ............... 275a 6.1.1 System Interface to Off-Line Crypto- graphic Equipment ........................ 277 6.1.2 Interface to On-Line Crypto .............. 277 6.2 SOFTWARE OF THE CRYPTO CONTROL SYSTEM ........┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00423941 ┆J B9A 277 6.2.1 Crypto Key Management .................... 278 6.2.1.1 Input of Crypto Keys ................. 278 6.2.1.2 Management of Crypto Keys ............ 278 6.2.1.3 Initiation of Crypto Keys ............ 279 6.2.1.3.1 Tim┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00423941 ┆J B9Ae- and Usage Crypto Keys ...... 279 6.2.1.3.2 Modify Present Crypto Key Number . 279 6.2.2 Management of The OFFLINE Crypto Device .. 279 6.2.3 Management of ONLINE Crypto Devices ...... 280a 6.3 CRYPTO KEY SUPERVISION ............┆
0x4b000…4b100 (75, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(75,0, 1), len=0xff, h3=41424041}, f00=»4240A «, f01=»LKSAA Vol. II part 1 «, f02=»jaa «, f03=»FE «, f04=»2.3 - 2.6 «, f05=31-10-83 16:14, f06=» 1 «, f07=»01 «, f08=» 1202 «, f09=03-03-84 17:47, f10=» «, f11=»00 «, f12=» 15 «, f13=03-03-84 17:48, f14=05-03-84 12:59, f15=»0385A «, f16=» 61 «, f17=» 2 «, f18=»01 «, f19=» 1032 «, f20=» 3638 «, f21=» «, f22=» 0 «, f99=030010000110462710110480aaca15050000000000000138033e01df}
0x4b100…4b200 (75, 0, 1) Sector 4b023d00424041 ┆K = B@A K K 3 Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : : : ┆
0x4b200…4b300 (75, 0, 2) Sector 4b03ff00424041 ┆K B@A 1 Issue 1.1 LKSAA - VOLUME II SYS/84-03-01 Part 1 TECHNICAL PROPOSAL ┆
0x4b300…4b400 (75, 0, 3) Sector 4b042200424041 ┆K " B@A Page :]=~ BC.MP- R5.> IM)-:^=~ BC.C~.M_* RM.> I:^=~ B[.Mr)Cp.:]=~ Bp.MP- Rm.> IM)-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00424041 ┆K B@A 1 2.3 AVAILABILITY REQUIREMNETS The availability of the proposed equipment is very high due to not only a high reliability of individual system elements, but mainly due to the chose┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00424041 ┆K B@An CR80 computer configuration, where functional like elements substitute each other automatically in case of failure. The actual availability will be very close to 100%, due to the exceptional design of the CR80 configuration for the LKSAA. 2┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00424041 ┆K B@A.3.1 General Considerations The high system availability has been achieved by the use of highly reliable modules, redundant processor units and automatic reconfiguration facilities. Care has been taken to ensure that single point errors do not cau┆
0x4b700…4b800 (75, 0, 7) Sector 3300ff00424041 ┆3 B@Ase total system failure. The reliability criteria imposed on the computer systems have been evaluated and the proposed hardware/software operational system analysed to determine the degree of availability and data integrity provided. In this chapt┆
0x4b800…4b900 (75, 0, 8) Sector 00000000000000 ┆ ┆
[…0x17…]
