Karteikarten
COMP312 Revision
Karten in diesem Stapel (22)
- 1Describe Symmetric Encryption- Both parties have a secret shared key
- Faster than asymmetric encryption
If a key is revealed then all information is compromised (Un-secure) - 2Describe Asymmetric Encryption- Sender has a key pair (private and public)
- Slower than symmetric encryption
- Secure - 3Describe a one-way hashwhen you generate a fixed length checksum, the digest is hard to derive data from and it would be difficult to find a piece of data with the same hash
- 4Signing EmailProve that the emails sender sent the email as claimed
- 5DNS Responses (DNSSEC)Prove that the answer received in DNS is authentic and comes from the authoritative source rather than an intermediary
- 6BGP Route AdvertisementsProve that the network announcing a prefix is allowed to do so (is not hijacking address space)
Prove that the path taken by the prefix from announcer to receiver is authentic - 7What are 6 DNS Record Types? (Hint: AAAA)A: Address
PTR: Pointer
NS: Name server
CNAME: Canonical name
MX: Mail exchanger
TXT: Text record - 8What is 'A' Record?Maps name to IPv4 Address
- 9What is 'AAAA' Record?Maps name to IPv6 Address
- 10What is 'PTR' Record?Maps IP Address to name
- 11What is 'NS' Record?Who will answer DNS requests for specified domain
- 12What is 'CNAME' Record?Maps alias to a single true name
- 13What is 'MX' Record?Host willing to accept mail
- 14What is 'TXT' Record?Arbitrary Text
- 15What is the DNSSEC Chain of Trust?Trust root zone ket, and use that key to build up a chain of trust for other keys
- 16DNSSEC - RRSIGSign resource records with private key
- 17DNSSEC - DNSKEYPublic key used to verify RRSIG signatures
- 18DNSSEC - DSDelegation signer. Hash of the public key used to sign records. Stored in parent zone
- 19DNSSEC - NSEC/NSEC3Proof of record non-existence
- 20What are some DNSSEC issues?Response may require more space than the 512 byte limit originally standardised for DNS over UDP
- Need some secure mechanism to provide parent DNS server DS record
- Key rollovers should occur regularly (automated) - 21What do you do when a response is larger than 512 byte limit for DNS over UDP?- Use EDNS0 extension to indicate ability to cope with >512 bytes
- Use TCP (Not recommended)
- Large responses from small requests provide means for denial of service attack using amplification (But plenty of scope for amplification already) - 22—
Informationen
- Beschreibung
- Karteikarten am COMP312 Revision, erstellt von Cherese Eriepa am 25/03/2018.
- Erstellt von
- Cherese Eriepa
- Aufrufe
- 1
- Bewertung