git: f0fa1c40e8 - main - Replace more http links with https, if possible
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 29 Oct 2026 14:11:34 UTC
The branch main has been updated by bcr:
URL: https://cgit.FreeBSD.org/doc/commit/?id=f0fa1c40e83603725fa770c57875ea675470398b
commit f0fa1c40e83603725fa770c57875ea675470398b
Author: Sarder Kamal <s.kamal@mdx.ac.uk>
AuthorDate: 2026-10-29 14:08:55 +0000
Commit: Benedict Reuschling <bcr@FreeBSD.org>
CommitDate: 2026-10-29 14:11:13 +0000
Replace more http links with https, if possible
Event: Oslo Hackathon 2026
---
.../content/en/articles/bsdl-gpl/_index.adoc | 14 +++++++-------
.../en/articles/building-products/_index.adoc | 16 ++++++++--------
.../content/en/articles/contributing/_index.adoc | 4 ++--
.../content/en/articles/contributors/_index.adoc | 22 +++++++++++-----------
.../contributors/contrib-develinmemoriam.adoc | 8 ++++----
.../en/articles/freebsd-questions/_index.adoc | 6 +++---
.../content/en/articles/ldap-auth/_index.adoc | 4 ++--
.../content/en/articles/remote-install/_index.adoc | 4 ++--
.../content/en/articles/vpn-ipsec/_index.adoc | 2 +-
9 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/documentation/content/en/articles/bsdl-gpl/_index.adoc b/documentation/content/en/articles/bsdl-gpl/_index.adoc
index ac3cc7a0f2..2f65a79a15 100644
--- a/documentation/content/en/articles/bsdl-gpl/_index.adoc
+++ b/documentation/content/en/articles/bsdl-gpl/_index.adoc
@@ -53,7 +53,7 @@ It can also be read as a BSD versus GPL Open Source License introduction and sum
== Very Brief Open Source History
Long before the term "Open Source" was used, software was developed by loose associations of programmers and freely exchanged.
-Starting in the early 1950's, organizations such as http://www.share.org[SHARE] and http://www.decus.org[DECUS] developed much of the software that computer hardware companies bundled with their hardware offerings.
+Starting in the early 1950's, organizations such as https://www.share.org[SHARE] and https://web.archive.org/web/20000620163923/http://www.decus.org/[DECUS] developed much of the software that computer hardware companies bundled with their hardware offerings.
At that time computer companies were in the hardware business;
anything that reduced software cost and made more programs available made the hardware companies more competitive.
@@ -112,7 +112,7 @@ UCB soon terminated its support for BSD.
[[current-bsdl]]
== The Current State of FreeBSD and BSD Licenses
-The so-called http://www.opensource.org/licenses/bsd-license.php[new BSD license] applied to FreeBSD within the last few years is effectively a statement that you can do anything with the program or its source,
+The so-called https://opensource.org/license/BSD-2-Clause[new BSD license] applied to FreeBSD within the last few years is effectively a statement that you can do anything with the program or its source,
but you do not have any warranty and none of the authors has any liability (basically, you cannot sue anybody).
This new BSD license is intended to encourage product commercialization.
Any BSD code can be sold or included in proprietary products without any restrictions on the availability of your code or your future behavior.
@@ -131,7 +131,7 @@ Stallman became upset when he found that he could not legally add minor improvem
(Many of Stallman's co-workers had left to form two companies based on software developed at MIT and licensed by MIT;
there appears to have been disagreement over access to the source code for this software).
Stallman devised an alternative to the commercial software license and called it the GPL, or "GNU Public License".
-He also started a non-profit foundation, the http://www.fsf.org[Free Software Foundation] (FSF),
+He also started a non-profit foundation, the https://www.fsf.org[Free Software Foundation] (FSF),
which intended to develop an entire operating system, including all associated software, that would not be subject to proprietary licensing.
This system was called GNU, for "GNU is Not Unix".
@@ -142,7 +142,7 @@ As the last paragraph of the GPL states:
"This General Public License does not permit incorporating your program into proprietary programs."<<one>>
-The http://www.opensource.org/licenses/gpl-license.php[GPL] is a complex license so here are some rules of thumb when using the GPL:
+The https://opensource.org/license/GPL-3.0[GPL] is a complex license so here are some rules of thumb when using the GPL:
* you can charge as much as you want for distributing, supporting, or documenting the software, but you cannot sell the software itself.
* the rule-of-thumb states that if GPL source is required for a program to compile, the program must be under the GPL. Linking statically to a GPL library requires a program to be under the GPL.
@@ -166,7 +166,7 @@ The source for this code must thus be made available to the user of the program.
Dynamic linking, however, is not considered a violation of the GPL.
Pressure to put proprietary applications on Linux became overwhelming.
Such applications often must link with system libraries.
-This resulted in a modified version of the GPL called the http://www.opensource.org/licenses/lgpl-license.php[LGPL] ("Library", since renamed to "Lesser", GPL).
+This resulted in a modified version of the GPL called the https://opensource.org/license/LGPL-3.0[LGPL] ("Library", since renamed to "Lesser", GPL).
The LGPL allows proprietary code to be linked to the GNU C library, glibc.
You do not have to release the source code which has been dynamically linked to an LGPLed library.
@@ -293,12 +293,12 @@ In addition, since the BSD license does not come with the legal complexity of th
[bibliography]
== Bibliographical References
-* [[[one,1]]] http://www.gnu.org/licenses/gpl.html
+* [[[one,1]]] https://www.gnu.org/licenses/gpl.html
* [[[two,2]]] http://archives.cnn.com/2000/TECH/computing/03/28/cyberpatrol.mirrors/
* [[[three,3]]] Open Source: the Unauthorized White Papers, Donald K. Rosenberg, IDG Books, 2000. Quotes are from page 114, "Effects of the GNU GPL".
-* [[[four,4]]] In the "What License to Use?" section of http://www.oreilly.com/catalog/opensources/book/brian.html
+* [[[four,4]]] In the "What License to Use?" section of https://www.oreilly.com/catalog/opensources/book/brian.html
This whitepaper is a condensation of an original work available at http://alumni.cse.ucsc.edu/~brucem/open_source_license.htm
diff --git a/documentation/content/en/articles/building-products/_index.adoc b/documentation/content/en/articles/building-products/_index.adoc
index 80d9fad16d..3a3a31dc50 100644
--- a/documentation/content/en/articles/building-products/_index.adoc
+++ b/documentation/content/en/articles/building-products/_index.adoc
@@ -135,7 +135,7 @@ FreeBSD can also provide a stable cross-development environment for the other co
In this model, organizations contribute useful infrastructural frameworks to the FreeBSD project (for example, see man:netgraph[3]).
The widespread exposure that the code gets helps to quickly identify performance issues and bugs.
The involvement of top-notch developers also leads to useful extensions to the infrastructure that the contributing organization also benefits from.
-* As a development environment supporting cross-development for embedded OSes like http://www.rtems.com/[RTEMS] and http://ecos.sourceware.org/[eCOS].
+* As a development environment supporting cross-development for embedded OSes like https://www.rtems.com/[RTEMS] and https://ecos.sourceware.org/[eCOS].
+
There are many full-fledged development environments in the {numports}-strong collection of applications ported and packaged with FreeBSD.
* As a way to support a Unix-like API in an otherwise proprietary OS, increasing its palatability for application developers.
@@ -374,26 +374,26 @@ The article concluded with a list of best-practices that could help organization
[bibliography]
== Bibliography
-[[Carp1996]] [Carp1996] http://www.ietf.org/rfc/rfc1958.txt[The Architectural Principles of the Internet] B. Carpenter. The Internet Architecture Board.The Internet Architecture Board. Copyright(R) 1996.
+[[Carp1996]] [Carp1996] https://www.ietf.org/rfc/rfc1958.txt[The Architectural Principles of the Internet] B. Carpenter. The Internet Architecture Board.The Internet Architecture Board. Copyright(R) 1996.
[[ComGuide]] [ComGuide] extref:{committers-guide}[Committer's Guide] The FreeBSD Project. Copyright(R) 2005.
-[[GoldGab2005]] [GoldGab2005] http://dreamsongs.com/IHE/IHE.html[Innovation Happens Elsewhere: Open Source as Business Strategy] Ron Goldman. Richard Gabriel. Copyright(R) 2005. Morgan-Kaufmann.
+[[GoldGab2005]] [GoldGab2005] https://dreamsongs.com/IHE/IHE.html[Innovation Happens Elsewhere: Open Source as Business Strategy] Ron Goldman. Richard Gabriel. Copyright(R) 2005. Morgan-Kaufmann.
[[Hub1994]] [Hub1994] extref:{contributing}[Contributing to the FreeBSD Project] Jordan Hubbard. Copyright(R) 1994-2005. The FreeBSD Project.
-[[McKu1999]] [McKu1999] http://www.usenix.org/publications/library/proceedings/usenix99/mckusick.html[Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystem] Kirk McKusick. Gregory Ganger. Copyright(R) 1999.
+[[McKu1999]] [McKu1999] https://www.usenix.org/publications/library/proceedings/usenix99/mckusick.html[Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystem] Kirk McKusick. Gregory Ganger. Copyright(R) 1999.
-[[McKu1999-1]] [McKu1999-1] http://www.oreilly.com/catalog/opensources/book/kirkmck.html[Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable] Marshall Kirk McKusick. http://www.oreilly.com/catalog/opensources/book/toc.html[Open Sources: Voices from the Open Source Revolution] O'Reilly Inc.. Copyright(R) 1993.
+[[McKu1999-1]] [McKu1999-1] https://www.oreilly.com/catalog/opensources/book/kirkmck.html[Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable] Marshall Kirk McKusick. https://www.oreilly.com/catalog/opensources/book/toc.html[Open Sources: Voices from the Open Source Revolution] O'Reilly Inc.. Copyright(R) 1993.
[[Mon2005]] [Mon2005] extref:{bsdl-gpl}[Why you should use a BSD style license for your Open Source Project] Bruce Montague. The FreeBSD Project. Copyright(R) 2005.
[[Nik2005]] [Nik2005] extref:{dev-model}[A project model for the FreeBSD Project] Niklas Saers. Copyright(R) 2005. The FreeBSD Project.
-[[Nor1993]] [Nor1993] http://www.norvig.com/luv-slides.ps[Tutorial on Good Lisp Programming Style] Peter Norvig. Kent Pitman. Copyright(R) 1993.
+[[Nor1993]] [Nor1993] https://www.norvig.com/luv-slides.ps[Tutorial on Good Lisp Programming Style] Peter Norvig. Kent Pitman. Copyright(R) 1993.
-[[Nor2001]] [Nor2001] http://www.norvig.com/21-days.html[Teach Yourself Programming in Ten Years] Peter Norvig. Copyright(R) 2001.
+[[Nor2001]] [Nor2001] https://www.norvig.com/21-days.html[Teach Yourself Programming in Ten Years] Peter Norvig. Copyright(R) 2001.
-[[Ray2004]] [Ray2004] http://www.catb.org/~esr/faqs/smart-questions.html[How to ask questions the smart way] Eric Steven Raymond. Copyright(R) 2004.
+[[Ray2004]] [Ray2004] https://www.catb.org/~esr/faqs/smart-questions.html[How to ask questions the smart way] Eric Steven Raymond. Copyright(R) 2004.
[[RelEngDoc]] [RelEngDoc] extref:{releng}[FreeBSD Release Engineering] Murray Stokely. Copyright(R) 2001. The FreeBSD Project.
diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc
index ee4c022771..f2ae0b4a10 100644
--- a/documentation/content/en/articles/contributing/_index.adoc
+++ b/documentation/content/en/articles/contributing/_index.adoc
@@ -466,7 +466,7 @@ These are the tasks you need to perform to ensure your port is able to be built:
====
. Watch for build failures
+
-Check your mail for mail from `pkg-fallout@FreeBSD.org` and the http://portscout.FreeBSD.org[distfiles scanner] to see if any of the port which are failing to build are out of date.
+Check your mail for mail from `pkg-fallout@FreeBSD.org` and the https://portscout.FreeBSD.org[distfiles scanner] to see if any of the port which are failing to build are out of date.
. Collect information
+
Once you are aware of a problem, collect information to help you fix it.
@@ -612,7 +612,7 @@ Following this article will greatly assist us in reducing the time needed to han
The https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla Problem Report database].
-The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] can show you ports for which the distfiles are not fetchable.
+The https://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] can show you ports for which the distfiles are not fetchable.
You can check on your own ports or use it to find ports that need their `MASTER_SITES` updated.
package:ports-mgmt/poudriere[] is the most thorough way to test a port through the entire cycle of installation, packaging, and deinstallation.
diff --git a/documentation/content/en/articles/contributors/_index.adoc b/documentation/content/en/articles/contributors/_index.adoc
index c28d66e25d..79e7138a67 100644
--- a/documentation/content/en/articles/contributors/_index.adoc
+++ b/documentation/content/en/articles/contributors/_index.adoc
@@ -157,9 +157,9 @@ As of 2010, the section below was several years out-of-date.
The following individuals and businesses made it possible for the FreeBSD Project to build a new central server machine, which has replaced `freefall.FreeBSD.org` at one point, by donating the following items:
-* {mbarkah} and his employer, http://www.hemi.com/[Hemisphere Online], donated a _Pentium Pro (P6) 200MHz CPU_.
-* http://www.asacomputers.com/[ASA Computers] donated a _Tyan 1662 motherboard_.
-* Joe McGuckin <mailto:joe@via.net[joe@via.net]> of http://www.via.net/[ViaNet Communications] donated a _Kingston ethernet controller_.
+* {mbarkah} and his employer, https://web.archive.org/web/20041130014050/http://hemi.com/[Hemisphere Online], donated a _Pentium Pro (P6) 200MHz CPU_.
+* https://www.asacomputers.com/[ASA Computers] donated a _Tyan 1662 motherboard_.
+* Joe McGuckin <mailto:joe@via.net[joe@via.net]> of https://www.via.net/[ViaNet Communications] donated a _Kingston ethernet controller_.
* Jack O'Neill <mailto:jack@diamond.xtalwind.net[jack@diamond.xtalwind.net]> donated an _NCR 53C875 SCSI controller card_.
* Ulf Zimmermann <mailto:ulf@Alameda.net[ulf@Alameda.net]> of http://www.Alameda.net/[Alameda Networks] donated _128MB of memory_, a _4 Gb disk drive and the case_.
@@ -169,24 +169,24 @@ The following individuals and businesses have generously contributed direct fund
* Annelise Anderson <mailto:andrsn@hoover.stanford.edu[andrsn@hoover.stanford.edu]>.
* {dillon}.
-* http://www.bluemountain.com/[Blue Mountain Arts].
+* https://www.bluemountain.com/[Blue Mountain Arts].
* http://www.epilogue.com/[Epilogue Technology Corporation].
* {sef}.
-* http://www.gta.com/[Global Technology Associates, Inc].
+* https://www.gta.com/[Global Technology Associates, Inc].
* Don Scott Wilde.
* Gianmarco Giovannelli <mailto:gmarco@masternet.it[gmarco@masternet.it]>.
* Josef C. Grosch <mailto:joeg@truenorth.org[joeg@truenorth.org]>.
* Robert T. Morris.
* {chuckr}.
-* Kenneth P. Stox <mailto:ken@stox.sa.enteract.com[ken@stox.sa.enteract.com]> of http://www.imagescape.com/[Imaginary Landscape, LLC.].
+* Kenneth P. Stox <mailto:ken@stox.sa.enteract.com[ken@stox.sa.enteract.com]> of https://www.imagescape.com/[Imaginary Landscape, LLC.].
* Dmitry S. Kohmanyuk <mailto:dk@dog.farm.org[dk@dog.farm.org]>.
* http://www.cdrom.co.jp/[Laser5] of Japan (a portion of the profits from sales of their various FreeBSD CDROMs).
* http://www.mmjp.or.jp/fuki/[Fuki Shuppan Publishing Co.] donated a portion of their profits from _Hajimete no FreeBSD_ (FreeBSD, Getting started) to the FreeBSD and XFree86 projects.
* http://www.ascii.co.jp/[ASCII Corp.] donated a portion of their profits from several FreeBSD-related books to the FreeBSD project.
-* http://www.yokogawa.co.jp/[Yokogawa Electric Corp] has generously donated significant funding to the FreeBSD project.
+* https://www.yokogawa.co.jp/[Yokogawa Electric Corp] has generously donated significant funding to the FreeBSD project.
* http://www.buffnet.net/[BuffNET].
* http://www.pacificsolutions.com/[Pacific Solutions].
-* http://www.siemens.de/[Siemens AG] via Andre Albsmeier <mailto:andre.albsmeier@mchp.siemens.de[andre.albsmeier@mchp.siemens.de]>.
+* https://www.siemens.com/[Siemens AG] via Andre Albsmeier <mailto:andre.albsmeier@mchp.siemens.de[andre.albsmeier@mchp.siemens.de]>.
* Chris Silva <mailto:ras@interaccess.com[ras@interaccess.com]>.
=== Hardware contributors
@@ -194,19 +194,19 @@ The following individuals and businesses have generously contributed direct fund
The following individuals and businesses have generously contributed hardware for testing and device driver development/support:
* BSDi for providing the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are being used for our development work, to say nothing of the network access and other donations of hardware resources.
-* http://www.compaq.com[Compaq] has donated a variety of Alpha systems to the FreeBSD Project. Among the many generous donations are 4 AlphaStation DS10s, an AlphaServer DS20, AlphaServer 2100s, an AlphaServer 4100, 8 500Mhz Personal Workstations, 4 433Mhz Personal Workstations, and more! These machines are used for release engineering, package building, SMP development, and general development on the Alpha architecture.
+* https://web.archive.org/web/19990202120711/http://www2.compaq.com/[Compaq] has donated a variety of Alpha systems to the FreeBSD Project. Among the many generous donations are 4 AlphaStation DS10s, an AlphaServer DS20, AlphaServer 2100s, an AlphaServer 4100, 8 500Mhz Personal Workstations, 4 433Mhz Personal Workstations, and more! These machines are used for release engineering, package building, SMP development, and general development on the Alpha architecture.
* TRW Financial Systems, Inc. provided 130 PCs, three 68 GB file servers, twelve Ethernets, two routers and an ATM switch for debugging the diskless code
* Dermot McDonnell donated the Toshiba XM3401B CDROM drive currently used in _freefall_.
* Chuck Robey <mailto:chuckr@glue.umd.edu[chuckr@glue.umd.edu]> contributed his floppy tape streamer for experimental work.
* Larry Altneu <mailto:larry@alr.com[larry@alr.com],> and {wilko}, provided Wangtek and Archive QIC-02 tape drives to improve the [.filename]#wt# driver.
* Ernst Winter (http://berklix.org/ewinter/[Deceased]) contributed a 2.88 MB floppy drive to the project. This will hopefully increase the pressure for rewriting the floppy disk driver.
-* http://www.tekram.com/[Tekram Technologies] sent one each of their DC-390, DC-390U and DC-390F FAST and ULTRA SCSI host adapter cards for regression testing of the NCR and AMD drivers with their cards. They are also to be applauded for making driver sources for free operating systems available from their FTP server link:ftp://ftp.tekram.com/scsi/FreeBSD/[ftp://ftp.tekram.com/scsi/FreeBSD/].
+* https://www.tekram.com/[Tekram Technologies] sent one each of their DC-390, DC-390U and DC-390F FAST and ULTRA SCSI host adapter cards for regression testing of the NCR and AMD drivers with their cards. They are also to be applauded for making driver sources for free operating systems available from their FTP server link:ftp://ftp.tekram.com/scsi/FreeBSD/[ftp://ftp.tekram.com/scsi/FreeBSD/].
* Larry M. Augustin contributed not only a Symbios Sym8751S SCSI card, but also a set of data books, including one about the forthcoming Sym53c895 chip with Ultra-2 and LVD support, and the latest programming manual with information on how to safely use the advanced features of the latest Symbios SCSI chips. Thanks a lot!
* {kuku} donated an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver development.
* Mike Tancsa <mailto:mike@sentex.ca[mike@sentex.ca]> donated four various ATM PCI cards to help increase support of these cards as well as help support the development effort of the netatm ATM stack.
=== Special contributors
-* http://www.osd.bsdi.com/[BSDi] (formerly Walnut Creek CDROM) has donated almost more than we can say (see the 'About the FreeBSD Project' section of the extref:{handbook}[FreeBSD Handbook] for more details). In particular, we would like to thank them for the original hardware used for `freefall.FreeBSD.org`, our primary development machine, and for `thud.FreeBSD.org`, a testing and build box. We are also indebted to them for funding various contributors over the years and providing us with unrestricted use of their T1 connection to the Internet.
+* https://web.archive.org/web/20001110060000/http://www.osd.bsdi.com/[BSDi] (formerly Walnut Creek CDROM) has donated almost more than we can say (see the 'About the FreeBSD Project' section of the extref:{handbook}[FreeBSD Handbook] for more details). In particular, we would like to thank them for the original hardware used for `freefall.FreeBSD.org`, our primary development machine, and for `thud.FreeBSD.org`, a testing and build box. We are also indebted to them for funding various contributors over the years and providing us with unrestricted use of their T1 connection to the Internet.
* The http://www.interface-business.de/[interface business GmbH, Dresden] has been patiently supporting {joerg} who has often preferred FreeBSD work over paid work, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or flaky to work with it.
* http://www.bsdi.com/[Berkeley Software Design, Inc.] has contributed their DOS emulator code to the remaining BSD world, which is used in the `doscmd` command.
diff --git a/documentation/content/en/articles/contributors/contrib-develinmemoriam.adoc b/documentation/content/en/articles/contributors/contrib-develinmemoriam.adoc
index bd0863552c..35fdd3dc56 100644
--- a/documentation/content/en/articles/contributors/contrib-develinmemoriam.adoc
+++ b/documentation/content/en/articles/contributors/contrib-develinmemoriam.adoc
@@ -81,19 +81,19 @@ Andrey contributions to FreeBSD can not be overstated. Having been involved for
Jürgen made a number of contributions to FreeBSD, including work on libvirt, the graphics stack, and QEMU. Jürgen's contributions and helpfulness were appreciated by people around the world. That work continues to improve the lives of thousands every day.
* {alexbl} (2006 - 2011; RIP 2012)
+
-http://www.legacy.com/obituaries/sfgate/obituary.aspx?pid=159801494[Alexander] was best known as a major contributor to FreeBSD's Python ports and a founding member of {python} as well as his work on XMMS2.
+https://www.legacy.com/us/obituaries/sfgate/name/alexander-botero-lowry-obituary?id=19221675[Alexander] was best known as a major contributor to FreeBSD's Python ports and a founding member of {python} as well as his work on XMMS2.
* {jb} (1997 - 2009; RIP 2009)
+
http://hub.opensolaris.org/bin/view/Community+Group+ogb/In+Memoriam[John] made major contributions to FreeBSD, the best known of which is the import of the man:dtrace[1] code. John's unique sense of humor and plain-spokenness either ruffled feathers or made him quick friends. At the end of his life, he had moved to a rural area and was attempting to live with as minimal impact to the planet as possible, while at the same time still working in the high-tech area.
* {jmz} (1994 - 2009; RIP 2009)
+
-http://www.obs-besancon.fr/article.php3?id_article=323[Jean-Marc] was an astrophysicist who made important contributions to the modeling of the atmospheres of both planets and comets at http://www.obs-besancon.fr/[l'Observatoire de Besançon] in Besançon, France. While there, he participated in the conception and construction of the Vega tricanal spectrometer that studied Halley's Comet. He had also been a long-time contributor to FreeBSD.
+http://www.obs-besancon.fr/article.php3?id_article=323[Jean-Marc] was an astrophysicist who made important contributions to the modeling of the atmospheres of both planets and comets at https://www.obs-besancon.fr/[l'Observatoire de Besançon] in Besançon, France. While there, he participated in the conception and construction of the Vega tricanal spectrometer that studied Halley's Comet. He had also been a long-time contributor to FreeBSD.
* {itojun} (1997 - 2001; RIP 2008)
+
-Known to everyone as http://astralblue.livejournal.com/350702.html[itojun], Jun-ichiro Hagino was a core researcher at the http://www.kame.net/[KAME Project], which aimed to provide IPv6 and IPsec technology in freely redistributable form. Much of this code was incorporated into FreeBSD. Without his efforts, the state of IPv6 on the Internet would be much different.
+Known to everyone as https://astralblue.livejournal.com/350702.html[itojun], Jun-ichiro Hagino was a core researcher at the https://www.kame.net/[KAME Project], which aimed to provide IPv6 and IPsec technology in freely redistributable form. Much of this code was incorporated into FreeBSD. Without his efforts, the state of IPv6 on the Internet would be much different.
* {cg} (1999 - 2005; RIP 2005)
+
http://www.dbsi.org/cam/[Cameron] was a unique individual who contributed to the project despite serious physical disabilities. He was responsible for a complete rewrite of our sound system during the late 1990s. Many of those who corresponded with him had no idea of his limited mobility, due to his cheerful spirit and willingness to help others.
* {alane} (2002 - 2003; RIP 2003)
+
-http://freebsd.kde.org/memoriam/alane.php[Alan] was a major contributor to the KDE on FreeBSD group. In addition, he maintained many other difficult and time-consuming ports such as autoconf, CUPS, and python. Alan's path was not an easy one but his passion for FreeBSD, and dedication to programming excellence, won him many friends.
+https://freebsd.kde.org/memoriam/alane.php[Alan] was a major contributor to the KDE on FreeBSD group. In addition, he maintained many other difficult and time-consuming ports such as autoconf, CUPS, and python. Alan's path was not an easy one but his passion for FreeBSD, and dedication to programming excellence, won him many friends.
diff --git a/documentation/content/en/articles/freebsd-questions/_index.adoc b/documentation/content/en/articles/freebsd-questions/_index.adoc
index 8dc469173d..0a895ffb65 100644
--- a/documentation/content/en/articles/freebsd-questions/_index.adoc
+++ b/documentation/content/en/articles/freebsd-questions/_index.adoc
@@ -108,9 +108,9 @@ The criteria above still apply, and it is in your interest to stick to them, sin
You can (and should) do some things yourself before asking a question on one of the mailing lists:
* Try solving the problem on your own. If you post a question which shows that you have tried to solve the problem, your question will generally attract more positive attention from people reading it. Trying to solve the problem yourself will also enhance your understanding of FreeBSD, and will eventually let you use your knowledge to help others by answering questions posted to the mailing lists.
-* Read the manual pages, and the FreeBSD documentation (either installed in [.filename]#/usr/doc# or accessible via WWW at http://www.FreeBSD.org[http://www.FreeBSD.org]), especially the extref:{handbook}[handbook] and the extref:{faq}[FAQ].
+* Read the manual pages, and the FreeBSD documentation (either installed in [.filename]#/usr/doc# or accessible via WWW at https://www.FreeBSD.org[https://www.FreeBSD.org]), especially the extref:{handbook}[handbook] and the extref:{faq}[FAQ].
* Browse and/or search the archives for the mailing list, to see if your question or a similar one has been asked (and possibly answered) on the list. You can browse and/or search the mailing list archives at https://www.FreeBSD.org/mail[https://www.FreeBSD.org/mail] and https://www.FreeBSD.org/search/#mailinglists[https://www.FreeBSD.org/search/#mailinglists] respectively.
-* Use a search engine such as http://www.google.com[Google] or http://www.yahoo.com[Yahoo] to find answers to your question.
+* Use a search engine such as https://www.google.com[Google] or https://www.yahoo.com[Yahoo] to find answers to your question.
== How to Submit a Question
@@ -123,7 +123,7 @@ When submitting a question to FreeBSD-questions, consider the following points:
Do not underestimate the effect that a poorly formatted mail message has, not just on the FreeBSD-questions mailing list.
Your mail message is all people see of you, and if it is poorly formatted, one line per paragraph, badly spelt, or full of errors, it will give people a poor impression of you.
+
-A lot of badly formatted messages come from http://www.lemis.com/email.html[bad mailers or badly configured mailers].
+A lot of badly formatted messages come from http://www.lemis.com/grog/email/email.php[bad mailers or badly configured mailers].
The following mailers are known to send out badly formatted messages without you finding out about them:
** exmh
diff --git a/documentation/content/en/articles/ldap-auth/_index.adoc b/documentation/content/en/articles/ldap-auth/_index.adoc
index 95a2cd5393..c25c9e1356 100644
--- a/documentation/content/en/articles/ldap-auth/_index.adoc
+++ b/documentation/content/en/articles/ldap-auth/_index.adoc
@@ -65,10 +65,10 @@ This article should be considered to lay the theoretical groundwork only, and an
== Configuring LDAP
LDAP stands for "Lightweight Directory Access Protocol" and is a subset of the X.500 Directory Access Protocol.
-Its most recent specifications are in http://www.ietf.org/rfc/rfc4510.txt[RFC4510] and friends.
+Its most recent specifications are in https://www.ietf.org/rfc/rfc4510.txt[RFC4510] and friends.
Essentially it is a database that expects to be read from more often than it is written to.
-The LDAP server http://www.openldap.org/[OpenLDAP] will be used in the examples in this document; while the principles here should be generally applicable to many different servers, most of the concrete administration is OpenLDAP-specific.
+The LDAP server httpis://www.openldap.org/[OpenLDAP] will be used in the examples in this document; while the principles here should be generally applicable to many different servers, most of the concrete administration is OpenLDAP-specific.
There are several server versions in ports, for example package:net/openldap26-server[].
Client servers will need the corresponding package:net/openldap26-client[] libraries.
diff --git a/documentation/content/en/articles/remote-install/_index.adoc b/documentation/content/en/articles/remote-install/_index.adoc
index c32943bb68..3d6b268739 100644
--- a/documentation/content/en/articles/remote-install/_index.adoc
+++ b/documentation/content/en/articles/remote-install/_index.adoc
@@ -94,7 +94,7 @@ This way the new system can be accessed from the network, and the rest of the in
The mfsBSD tool-set can be used to build a tiny FreeBSD image.
As the name of mfsBSD suggests ("mfs" means "memory file system"), the resulting image runs entirely from a ramdisk.
Thanks to this feature, the manipulation of hard drives will not be limited, therefore it will be possible to install a complete FreeBSD operating system.
-The mfsBSD http://mfsbsd.vx.sk/[home page] includes pointers to the latest release of the toolset.
+The mfsBSD https://mfsbsd.vx.sk/[home page] includes pointers to the latest release of the toolset.
Please note that the internals of mfsBSD and how it all fits together is beyond the scope of this article.
The interested reader should consult the original documentation of mfsBSD for more details.
@@ -103,7 +103,7 @@ Download and extract the latest mfsBSD release and change your working directory
[source,shell]
....
-# fetch http://mfsbsd.vx.sk/release/mfsbsd-2.1.tar.gz
+# fetch https://mfsbsd.vx.sk/release/mfsbsd-2.1.tar.gz
# tar xvzf mfsbsd-2.1.tar.gz
# cd mfsbsd-2.1/
....
diff --git a/documentation/content/en/articles/vpn-ipsec/_index.adoc b/documentation/content/en/articles/vpn-ipsec/_index.adoc
index b4fac04c2b..63f091e260 100644
--- a/documentation/content/en/articles/vpn-ipsec/_index.adoc
+++ b/documentation/content/en/articles/vpn-ipsec/_index.adoc
@@ -22,7 +22,7 @@ toc::[]
Internet Protocol Security (IPsec) is a set of protocols which sit on top of the Internet Protocol (IP) layer.
It allows two or more hosts to communicate in a secure manner by authenticating and encrypting each IP packet of a communication session.
-The FreeBSD IPsec network stack is based on the http://www.kame.net/[http://www.kame.net/] implementation and supports both IPv4 and IPv6 sessions.
+The FreeBSD IPsec network stack is based on the https://www.kame.net/[https://www.kame.net/] implementation and supports both IPv4 and IPv6 sessions.
IPsec is comprised of the following sub-protocols: