Anonymous ID: fd0fe5 Feb. 13, 2018, 5:14 p.m. No.368246   🗄️.is 🔗kun   >>8301 >>8358 >>8420

>>368232

>>368213

 

RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000 RS/6000

 

 

memory keyboard network scsi speaker ok

0 dev / ok

0 ls

00c5a398: /cpus

00c5b0d8: /PowerPC,POWER3@0

00c5b650: /l2-cache

00c5c198: /PowerPC,POWER3@1

00c5c710: /l2-cache

00c5cb08: /PowerPC,POWER3@2

00c5d080: /l2-cache

00c5d478: /PowerPC,POWER3@3

00c5d9f0: /l2-cache

00c5dde8: /reserved@ff000000

00c5e390: /event-sources

00c5e3f8: /epow-events

00c5e490: /chosen

00c5e5f8: /memory@0

00c61510: /IBM,memory-module@0

00c61920: /IBM,memory-module@1

00c61d30: /IBM,memory-module@2

00c62140: /IBM,memory-module@3

00c62558: /IBM,memory-module@4

00c62968: /IBM,memory-module@5

00c62d78: /IBM,memory-module@6

00c63190: /IBM,memory-module@7

00c635a8: /IBM,memory-module@8

00c639b8: /IBM,memory-module@9

00c63dc8: /IBM,memory-module@a

00c641e0: /IBM,memory-module@b

00c645f8: /IBM,memory-module@c

00c64a08: /IBM,memory-module@d

00c64e18: /IBM,memory-module@e

00c65230: /IBM,memory-module@f

00c65648: /IBM,memory-module@10

00c65a58: /IBM,memory-module@11

00c65e68: /IBM,memory-module@12

00c66278: /IBM,memory-module@13

00c66690: /IBM,memory-module@14

00c66aa0: /IBM,memory-module@15

00c66eb0: /IBM,memory-module@16

00c672c8: /IBM,memory-module@17

00c676e0: /IBM,memory-module@18

00c67af0: /IBM,memory-module@19

00c67f00: /IBM,memory-module@1a

00c68318: /IBM,memory-module@1b

00c68730: /IBM,memory-module@1c

00c68b40: /IBM,memory-module@1d

00c68f50: /IBM,memory-module@1e

00c69368: /IBM,memory-module@1f

00c69780: /memory-controller@ff001000

00c699b0: /nvram@ff800000

00c69e80: /IBM,sp@ff880000

00c79c08: /rom@fff00000

00c7acb8: /interrupt-controller@ffc00000

00c7b060: /openprom

00c80238: /options

00c80e28: /aliases

00c828e8: /packages

00c82990: /deblocker

00c83470: /disk-label

00c86b38: /tape-label

00c86db8: /obp-tftp

00c900d0: /prep-boot

00c90688: /fat-files

00c920c0: /iso-13346-files

00c99270: /disassembler

00c9e5b8: /assembler

00caf468: /platform

00cafdf0: /utilities

00cb9aa8: /net

00cbb2b0: /iso-9660-files

00cbc1c0: /boot-mgr

00cd0550: /chrp-loader

00cd06e0: /pe-loader

00cd0f00: /elf-loader

00cd3090: /terminal-emulator

00d2ccf8: /gui

00db8ab0: /post

00cd3128: /rtas

00ce2470: /pci@fef00000

00cecd10: /isa@b

00cee920: /reserved@i78

00ceea28: /rtc@i70

00cf0640: /serial@i3f8

00cf1758: /serial@i2f8

00cf2870: /fdc@i3f0

00cf5ed8: /timer@i40

00cf6420: /interrupt-controller@i20

00cf6658: /dma-controller@i0

00cf6c30: /ethernet@c

00cff2d8: /scsi@d

00d04b58: /sd

00d05ab8: /st

00ce6930: /pci@fee00000

00d06e20: /ethernet@b

00ce9440: /pci@fed00000

00d0f5c8: /ethernet@b

00cebc40: /IBM,TB3MX@fb000000

ok

0 " ibm,loc-code" 00cf6c30 get-package-property ok

3 . 0 ok

2 dump

00cf6c70: 50 32 2f 45 31 00 :P2/E1.: ok

0 " vendor-id" 00cf6c30 get-package-property ok

3 . 0 ok

2 dump

00cf6c98: 00 00 10 23 :…#: ok

0 " device-id" 00cf6c30 get-package-property ok

3 . 0 ok

2 dump

00cf6cc0: 00 00 20 00 :.. .: ok

0 " revision-id" 00cf6c30 get-package-property ok

3 . 0 ok

2 dump

00cf6ce8: 00 00 00 26 :…&: ok

0 dev /pci@fef00000/ethernet@c ok

0 " ethernet,100,rj45,full" encode-string " chosen-network-type" property ok

0 " 000.000.000.000" " ibm,fw-clientipaddr" $setenv ok

0 " 000.000.000.000" " ibm,fw-serveripaddr" $setenv ok

0 " 000.000.000.000" " ibm,fw-gatewayipaddr" $setenv ok

0 " 255.255.255.000" " ibm,fw-netmask" $setenv ok

0 boot /pci@fef00000/ethernet@c

BOOTP S = 1

FILE: /tftpboot/e1

Load Addr=0x4000 Max Size=0xbfc000

FINAL Packet Count = 15853

FINAL File Size = 8116590 bytes.

 

38dU#9=0;9S2wB0vMzsW)!{|b$dZ?~~FukaKuqb=6PDfrp}OMZ<y/V}/VDB`[Wy

Anonymous ID: fd0fe5 Feb. 13, 2018, 5:28 p.m. No.368360   🗄️.is 🔗kun   >>8368

(∴)FNORD.

 

ALL THAT IS GOING ON IS "REAL".

 

WHILE IT MAY BE "NEW" IN SCIENCE, IT IS NOT "MAGIC".

 

THESE ARE NOT SECRET POWERS OR KEYS TO THE UNIVERSE.

 

ATLEAST NOT IN THE ESOTERIC FORM.

Anonymous ID: fd0fe5 Feb. 13, 2018, 5:52 p.m. No.368575   🗄️.is 🔗kun   >>8732

>>368517

 

FOR EVERYONE ELSE.

 

I KNOW YOU GUYS KNOW THIS BUT EVERYONE IS ASKING "WHY THE IMAGES?"

 

We are asked "WHY THE NAME?"

 

READ HERE-→https:// en.wikipedia.org/wiki/Lucifer_(cipher) …

 

#QAnon #UraniumOne

 

GOOD HERE

rVm!D{AgV]8t4CcO^}7M]_LxZx{I>"RK]Jz}(n&ac(k@{!>|C`,DHL~:7psgS@'

Anonymous ID: fd0fe5 Feb. 13, 2018, 6:08 p.m. No.368732   🗄️.is 🔗kun

The federal encryption standard for unclassified government computer data and communications, an encryption algorithm called Lucifer, had been developed by IBM in the early 70s.

It was later certified by a civilian agency, the National Bureau of Standards (now NIST), as the Data Encryption Standard (DES) in 1976.

Unlike public key cryptography which uses two keys (either one of which may be used to encrypt, and the other to decrypt), DES was a symmetric key system, using a single key to both encrypt and decrypt.

Because of the single key, DES could be used for encryption or authentication, but not both simultaneously.

 

Through the American Bankers Association and ANSI's Financial Institution Wholesale Security Working Group, Lucifer Encryption, now renamed DES, entered the banking world as a method of encryption and message authentication in electronic funds transfer. >>368575