30.11.2012 Views

Code and ciphers: Julius Caesar, the Enigma and the internet

Code and ciphers: Julius Caesar, the Enigma and the internet

Code and ciphers: Julius Caesar, the Enigma and the internet

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

164<br />

chapter 12<br />

eight-bit) character in <strong>the</strong> block <strong>and</strong> ano<strong>the</strong>r check sum, <strong>the</strong> longitudinal<br />

parity check, based upon <strong>the</strong> number of 1s in each of <strong>the</strong> six (or eight) separate<br />

streams, was generated at <strong>the</strong> end of <strong>the</strong> block. These check sums were<br />

typically constructed so that each stream of 0s <strong>and</strong> 1s had an odd number<br />

of 1s in it. This was sufficient to detect <strong>and</strong> correct a single error in <strong>the</strong><br />

block. If <strong>the</strong>re were two or more errors <strong>the</strong>y could not be corrected <strong>and</strong>,<br />

possibly, not even detected. The tape drives would carry out <strong>the</strong> checks<br />

automatically <strong>and</strong> re-read any block that failed <strong>the</strong> parity test. Dust on <strong>the</strong><br />

tape could cause a misread <strong>and</strong> <strong>the</strong> tapes would frequently be seen to<br />

oscillate backwards <strong>and</strong> forwards several times before moving on. Since<br />

<strong>the</strong> computer itself generated <strong>the</strong> parity check bits <strong>the</strong>re was no difficulty<br />

in changing <strong>the</strong> data if a genuine single error was detected. The parity<br />

checks were not designed to beat crooks, who might have managed to<br />

change both <strong>the</strong> data <strong>and</strong> <strong>the</strong> check sums; <strong>the</strong>y were <strong>the</strong>re only to protect<br />

<strong>the</strong> data from dust, including cigarette ash, <strong>and</strong> machine malfunctions.<br />

Smoking in <strong>the</strong> machine room, prevalent in <strong>the</strong> early days, was often<br />

found to be <strong>the</strong> cause of tape errors <strong>and</strong> was subsequently banned.<br />

Occasionally <strong>the</strong>re was nothing wrong with <strong>the</strong> data on <strong>the</strong> magnetic tape<br />

<strong>and</strong> it was <strong>the</strong> checking circuitry in <strong>the</strong> tape drives <strong>the</strong>mselves that was<br />

faulty. The computer operators soon discovered this <strong>and</strong> also found that,<br />

in <strong>the</strong> USA, a quarter-dollar inserted into <strong>the</strong> appropriate slot on <strong>the</strong> tape<br />

drive caused <strong>the</strong> checking circuits to be overridden.<br />

When it became possible to connect computers toge<strong>the</strong>r so that ‘messages’,<br />

which might be programs or data, could be passed between <strong>the</strong>m<br />

<strong>the</strong> question of how to ensure that <strong>the</strong> messages did not get ‘garbled’,<br />

ei<strong>the</strong>r accidentally or deliberately, en route had to be considered. Whilst<br />

parity checking, particularly if more sophisticated error correcting codes<br />

such as those described in [1.1], [1.2] <strong>and</strong> [1.3] were used, could provide<br />

protection against accidental corruption, a crook would be able to generate<br />

<strong>the</strong> appropriate check sums for any block that he had changed <strong>and</strong> so<br />

escape detection. It thus came to be realised that encipherment, using a<br />

system which a crook couldn’t replicate, was necessary.<br />

Encipherment of programs, data <strong>and</strong> messages<br />

By <strong>the</strong> beginning of <strong>the</strong> 1970s most major businesses, government offices<br />

<strong>and</strong> academic institutions were using computers, <strong>and</strong> computer networks<br />

were spreading. A typical installation would have one or more large<br />

machines, mainframes as <strong>the</strong>y were called, with numerous teletypes or, later,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!