Reorder RFCs in Bibtex file

This commit is contained in:
Jan Philipp Timme 2018-08-14 12:17:36 +02:00
parent b57fd5eafc
commit 8c1d6c6e98
2 changed files with 69 additions and 39 deletions

View File

@ -1,18 +1,12 @@
% Encoding: UTF-8
@techreport{RFC4301,
author = {S. Kent and K. Seo},
title = {Security Architecture for the Internet Protocol},
howpublished = {Internet Requests for Comments},
type = {RFC},
number = {4301},
year = {2005},
month = {December},
issn = {2070-1721},
publisher = {Internet Engineering Task Force},
institution = {Internet Engineering Task Force},
url = {https://tools.ietf.org/html/rfc4301.txt},
note = {\url{https://tools.ietf.org/html/rfc4301.txt}},
@Book{book:debian,
author = {Raphaël Hertzog and Roland Mas},
title = {The Debian Administrators Handbook},
year = {2015},
isbn = {979-10-91414-04-3},
url = {https://debian-handbook.info/},
urldate = {2018-07-17},
}
@Manual{man:openvpn,
@ -27,13 +21,19 @@
timestamp = {2018-07-17},
}
@Book{book:debian,
author = {Raphaël Hertzog and Roland Mas},
title = {The Debian Administrators Handbook},
year = {2015},
isbn = {979-10-91414-04-3},
url = {https://debian-handbook.info/},
urldate = {2018-07-17},
@TechReport{RFC4301,
author = {S. Kent and K. Seo},
title = {Security Architecture for the Internet Protocol},
institution = {Internet Engineering Task Force},
year = {2005},
type = {RFC},
number = {4301},
note = {\url{https://tools.ietf.org/html/rfc4301.txt}},
month = {December},
url = {https://tools.ietf.org/html/rfc4301.txt},
howpublished = {Internet Requests for Comments},
issn = {2070-1721},
publisher = {Internet Engineering Task Force},
}
@TechReport{RFC4302,
@ -66,6 +66,21 @@
publisher = {Internet Engineering Task Force},
}
@TechReport{RFC7296,
author = {C. Kaufman and P. Hoffman and Y. Nir and P. Eronen and T. Kivinen},
title = {Internet Key Exchange Protocol Version 2 (IKEv2)},
institution = {Internet Engineering Task Force},
year = {2014},
type = {RFC},
number = {7296},
note = {\url{https://tools.ietf.org/html/rfc7296.txt}},
month = {October},
url = {https://tools.ietf.org/html/rfc7296.txt},
howpublished = {Internet Requests for Comments},
issn = {2070-1721},
publisher = {Internet Engineering Task Force},
}
@TechReport{RFC7321,
author = {D. McGrew and P. Hoffman},
title = {Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)},
@ -81,16 +96,16 @@
publisher = {Internet Engineering Task Force},
}
@TechReport{RFC7296,
author = {C. Kaufman and P. Hoffman and Y. Nir and P. Eronen and T. Kivinen},
title = {Internet Key Exchange Protocol Version 2 (IKEv2)},
@TechReport{RFC8200,
author = {S. Deering and R. Hinden},
title = {Internet Protocol, Version 6 (IPv6) Specification},
institution = {Internet Engineering Task Force},
year = {2014},
type = {STD},
number = {79},
note = {\url{https://tools.ietf.org/html/rfc7296.txt}},
month = {October},
url = {https://tools.ietf.org/html/rfc7296.txt},
year = {2017},
type = {RFC},
number = {8200},
note = {\url{https://tools.ietf.org/html/rfc8200.txt}},
month = {July},
url = {https://tools.ietf.org/html/rfc8200.txt},
howpublished = {Internet Requests for Comments},
issn = {2070-1721},
publisher = {Internet Engineering Task Force},
@ -111,4 +126,19 @@
publisher = {Internet Engineering Task Force},
}
@TechReport{RFC8221,
author = {P. Wouters and D. Migault and J. Mattsson and Y. Nir and T. Kivinen},
title = {Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)},
institution = {Internet Engineering Task Force},
year = {2017},
type = {RFC},
number = {8221},
note = {\url{https://tools.ietf.org/html/rfc8221.txt}},
month = {October},
url = {https://tools.ietf.org/html/rfc8221.txt},
howpublished = {Internet Requests for Comments},
issn = {2070-1721},
publisher = {Internet Engineering Task Force},
}
@Comment{jabref-meta: databaseType:biblatex;}

View File

@ -308,7 +308,7 @@ Arbeitsschritte wie das Patchen und Kompilieren des Quellcodes, sowie Tests und
Die Authentizität der Pakete wird anhand von GPG-Signaturen durch den Paketmanager vor der Installation überprüft\cite{book:debian}[Siehe Kapitel 6.5].
Um den Wartungsaufwand des VPN-Servers zu reduzieren, kann die Installation von Updates durch den Debian-Paketmanager automatisiert werden\cite{book:debian}[Siehe Kapitel 6.7 und 6.8].
Somit muss der Systemadministrator lediglich Upgrades zur nächsthöheren Debian-Version durchführen.
Somit muss der Systemadministrator lediglich Upgrades zur nächsthöheren Debian-Version durchführen, da dabei Anpassungen an der Systemkonfiguration notwendig werden.
Im Folgenden werden mögliche Software-Kandidaten aus den Debian-Paketquellen vorgestellt.