Skip to content
BranchesTags

Repository files navigation

TaurusTLS

Copyright (c) 2026 TaurusTLS Developers All Rights Reserved

General Information

TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:

  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.

Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.

TaurusTLS supports the following operating systems:

  • Android
  • iOS
  • Linux
  • MacOS
  • Windows

License

TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.

The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.

To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.

RAD Studio Installation

TaurusTLS supports the following RAD Studio versions:

  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder

You may make packages for older versions of RAD Studio.

For Indy Included with Delphi

  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.

You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.

If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:

tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website

  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.

You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.

Making your own Packages

I suggest that you have 2 separate packages; a runtime only package and a design-time package.

The run-time package should depend upon your Indy package files and include the following:

  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas

The design-time package should depend upon the run-time package and include the following files:

  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas

Lazarus Installation

  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.

Deploying Your Applications

Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications

Component Reference

TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.

Demo Programs

Taurus TLS includes 3 demo programs.

TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj

This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:

This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:

[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:

  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.

TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr

This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:

For help using the client, just use the "help" command.

TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr

This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.

Tools I Use

Beyond Compare

Compares different versions of a file. https://www.scootersoftware.com/

Deleaker

Helps us find leaks. https://www.deleaker.com/

DocInsight

Converts XML Documentation comments into a .CHM file. https://devjetsoftware.com/products/documentation-insight/

Pascal Analyzer

Analyzes source-code to find various types of potential issues.

https://peganza.com/products_pal.html

TMS FixInsight

Analyzes source-code to find various types of potential issues.

https://www.tmssoftware.com/site/fixinsight.asp

Credits

Chad Z. Hower (Kudzu) and the Indy Pit Crew

author of the original code that was modified to create TaurusTLS.

Dave Nottage

for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS

Tony Whyman

for providing the OpenSSL headers that TaurusTLS is based upon

Third Party Notices

Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower (Kudzu) and the Indy Pit Crew – https://www.indyproject.org/

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.

  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.

THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

About

TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct

Resources

Readme
License
Activity
Custom properties

Stars

133 stars

Watchers

18 watching

Forks

21 forks
Report repository

Releases

Sponsor this project

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - TaurusTLS-Developers/TaurusTLS: TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct · GitHub
Skip to content
BranchesTags
Repository files navigation
TaurusTLS
Copyright (c) 2026 TaurusTLS Developers
All Rights Reserved
General Information
TaurusTLS provides 3.x and 4.x support for Indy - Internet Direct. It includes headers plus two components for Delphi and C++Builder. Those components are:
  • TTaurusTLSIOHandlerSocket - Enables TLS in a TIdTCPClientCustom descendant.
  • TTaurusTLSServerIOHandler - Enables TLS in a TIdCustomTCPServer descendant.
  • TTaurusTLSUnicodeLog - Triggers events when data is sent and received and data is provided in Unicode form if supported.
Both components are in the TaurusTLS.pas unit and the components are available on the IDE palette page, “TaurusTLS”.
TaurusTLS supports the following operating systems:
  • Android
  • iOS
  • Linux
  • MacOS
  • Windows
License
TaurusTLS is dual licensed. You can review which license better suits your needs, and use that license. You can even change your mind later if you have previously chosen one.
The TaurusTLS Modified BSD license is a very no nonsense license that allows you to do almost anything you want with TaurusTLS provided you provide proper attribution. Details are available in the Modified_BSD_LICENSE.md file included in the with this source-code.
To make it easier and consistent for JEDI users, we also offer an MPL license v1.1. Details are available in the LICENSE_MPL_1_1.txt file included with this source-code.
RAD Studio Installation
TaurusTLS supports the following RAD Studio versions:
  • Florence (Delphi 13) - packages in the TaurusTLS\Packages\d13 folder
  • Athens (Delphi 12) - packages in the TaurusTLS\Packages\d12 folder
  • Alexandria (Delphi 11) - package in the TaurusTLS\Packages\d11 folder
  • Sydney (Delphi 10.4) - package in the TaurusTLS\Packages\dsydney folder
  • Rio (Delphi 10.3) - package in the TaurusTLS\Packages\drio folder
  • Tokyo (Delphi 10.2) - package in the TaurusTLS\Packages\dtokyo folder
  • Berlin (Delphi 10.1) - package in the TaurusTLS\Packages\dberlin folder
  • Seattle (Delphi 10) - package in the TaurusTLS\Packages\dseattle folder
You may make packages for older versions of RAD Studio.
For Indy Included with Delphi
  1. Open TaurusAll.groupproj in the TaurusTLS\Packages\d12 folder.
  2. Compile TaurusTLS_RT.
  3. Compile TaurusTLS_DT and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
If you have TMS Smart Setup 2.0 with no credentials required, go to the "TMS Smart Setup Console", and do the following to install TaurusTLS:
tms config
tms install taurustls_developers.taurustls

For Indy that was Upgraded from the Website
  1. Set the INDY_PATH environment variable for your user account to the location where Indy is located.
  2. Open TaurusForIndy290All.groupproj in the TaurusTLS\Packages\d12 folder.
  3. Compile TaurusTLS_RTForIndy290.
  4. Compile TaurusTLS_DTForIndy290 and install it in the IDE.
You may install TaurusTLS into the 64-bit Integrated Development Environment (IDE) using the same procedure.
Making your own Packages
I suggest that you have 2 separate packages; a runtime only package and a design-time package.
The run-time package should depend upon your Indy package files and include the following:
  • Source\TaurusTLS.pas
  • Source\TaurusTLS_Files.pas
  • Source\TaurusTLS_NTLM.pas
  • Source\TaurusTLS_ResourceStrings.pas
  • Source\TaurusTLS_Utils.pas
  • Source\TaurusTLS_X509.pas
  • Source\TaurusTLSConsts.pas
  • Source\TaurusTLSExceptionHandlers.pas
  • Source\TaurusTLSFIPS.pas
  • Source\TaurusTLS_Unicode_Log.pas
  • Source\TaurusTLSHeaders_*.pas
  • Source\TaurusTLSLoader.pas
The design-time package should depend upon the run-time package and include the following files:
  • Source\TaurusTLS_Dsn_AboutDlg.pas
  • Source\TaurusTLS_Dsn_ComponentEditor.pas
  • Source\TaurusTLS_Dsn_Register.pas
  • Source\TaurusTLS_Dsn_ResourceStrings.pas
Lazarus Installation
  1. Open taurustlsldsgn.lpk from the TaurusTLS/Packages/lazarus.
  2. From "Required Packages", open "TaurusTLSRT" and compile it.
  3. Then compile the main package itself and install it in the IDE.
Deploying Your Applications
Deployment instructions are now on the TaurusTLS website's Deploying Your TaurusTLS Applications
Component Reference
TaurusTLS includes a component reference in "Compiled HTML Help file (.chm)" format in the Help\chm directory.
Demo Programs
Taurus TLS includes 3 demo programs.
TaurusTLS\src\demos\FTPServer\TaurusFTPServer.dproj
This is a FTP Server with TLS enabled that runs in the Windows console. This program has been tested with the following FTP clients:
This program requires a certificate to run. Instructions for creating a self-signed certificate are available at https://technotes.shemyak.com/posts/min-openssl-cnf/. You then need to create a server.ini file in the executable directory that enables the certificate that has the following lines:
[Certificate]
CertificateFile=[path to your public certificate file]
KeyFile=[path to your private SSL key]
Password=[password for your private SSL key]
RootCertFile=[path to your root certificate file if applicable]

You can also do the following:
  1. Copy the OpenSSL .dll's and openssl.exe to the directory where the FTP server demo .exe is built. Usually that is \$(platform)\Debug or \$(platform)\Release.
  2. Run the makecert.bat to generate a self-signed certificate. Just answer the prompts and the certificate is generated.
  3. Run the FTP Server .exe and it will create a default server.ini file that points to the certificate files generated in Step 2.
TaurusTLS\demos\TaurusFTPConsole\taurusftp.dpr and taurusftp.lpr
This is a fully functional cross-platform console FTP client that can be built with both Delphi and Lazaurus. It has been tested with the following servers:
For help using the client, just use the "help" command.
TaurusTLS\Demos\TaurusHTTPServer\taurusHTTPServer.dpr and taurusHTTPServer.lpr
This is a minimal HTTP Server that only replies with a 200 code and an empty page. This program is used for testing the server component for cross-platform usage. This program requires a certificate file (domain.crt) and a private key file (domain.key) that has to generated by the openssl.exe program.
Tools I Use
Beyond Compare
Compares different versions of a file.
https://www.scootersoftware.com/
Deleaker
Helps us find leaks.
https://www.deleaker.com/
DocInsight
Converts XML Documentation comments into a .CHM file.
https://devjetsoftware.com/products/documentation-insight/
Pascal Analyzer
Analyzes source-code to find various types of potential issues.
https://peganza.com/products_pal.html
TMS FixInsight
Analyzes source-code to find various types of potential issues.
https://www.tmssoftware.com/site/fixinsight.asp
Credits
Chad Z. Hower (Kudzu) and the Indy Pit Crew
author of the original code that was modified to create TaurusTLS.
Dave Nottage
for providing the code used for loading OpenSSL on MacOS, and for changes needed for static binding, and Android and iOS
Tony Whyman
for providing the OpenSSL headers that TaurusTLS is based upon
Third Party Notices
Portions of this software are Copyright (c) 1993 – 2018, Chad Z. Hower
(Kudzu) and the Indy Pit Crew – https://www.indyproject.org/
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation, about box and/or other materials provided with the distribution.
  2. No personal names or organizations names associated with the Indy project may be used to endorse or promote products derived from this software without specific prior written permission of the specific individual or organization.
THIS SOFTWARE IS PROVIDED BY Chad Z. Hower (Kudzu) and the Indy Pit Crew "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
About
TaurusTLS provides OpenSSL 3.x and 4.x support for Indy - Internet Direct
Resources
Readme
License
Activity
Custom properties
Stars
133 stars
Watchers
18 watching
Forks
21 forks
Report repository
Releases
Sponsor this project
Packages
Used by
Contributors
Languages