So in short, you let the hackers have the public key but they can't do anything with it as you need the private key to decrypt the data at the other end?
So in short, you let the hackers have the public key but they can't do anything with it as you need the private key to decrypt the data at the other end?
Basically, but of course it's not just hackers who can have it, anyone wanting to send data to you needs your public key as well to encrypt the data that they're going to send you, which you can then decrypt using your private key.
AQA can go suck a big fat one!! That trace table was complete BS, I barely have the patience for a little, never mind that one! And also, just curious, but are trace tables actually used in the industry?
Ok, did it. Bear in mind there's a good chance a couple of these are wrong. Any ones left blank were longer answer questions that I didn't have time to put into my calculator.
Ok, did it. Bear in mind there's a good chance a couple of these are wrong. Any ones left blank were longer answer questions that I didn't have time to put into my calculator.
Spoiler
For question 4B I'm pretty sure the answers was 13.25 not 13.625
For question 4B I'm pretty sure the answers was 13.25 not 13.625
Yeah, it was 13.25 Everything went real nice. Not sure about the ER diagram (i got many to many appointments and patients, and one to many from the others to appointments) Or the normalisation of the database (cant remember) though
Yeah, it was 13.25 Everything went real nice. Not sure about the ER diagram (i got many to many appointments and patients, and one to many from the others to appointments) Or the normalisation of the database (cant remember) though
It was many-to-one for appointments to patients. it was 1 appointment has only one patient, but patients could have multiple appointments.