Short:        A new compact TLS/HTTPS library OS1.3
Author:       aminet@jaehne.tk (Marcel Jähne)
Uploader:     aminet jaehne tk (Marcel Jähne)
Type:         util/libs
Version:      1.0
Architecture: m68k-amigaos
Distribution: Aminet

AmiTLS13 brings HTTPS support to AmigaOS 1.3 systems in a small, focused
library. It is not a full AmiSSL replacement, but a lightweight client-side
TLS wrapper designed for new applications that need to access HTTPS APIs or
web resources.

The library uses a trimmed BearSSL TLS backend and exposes a simple Amiga
shared-library API through amitls13.library. Applications can either use the 
included SDK stubs or link against the static proof-of-concept library. 
AmiTLS13 has been optimized for size and stack usage, and the current release
profile has been validated on real AmigaOS 1.3 setups with a 68020+ CPU and a
bsdsocket-compatible stack like thewire13.

Feature List

 v1.0

  - AmigaOS 1.3 compatible amitls13.library
  - Designed for 68020+ systems
  - Uses bsdsocket-compatible TCP/IP stacks
  - Plain C API for new Amiga applications
  - TLS 1.2 HTTPS client support
  - HTTP and HTTPS GET helper API
  - Trimmed BearSSL backend for reduced binary size
  - Current TLS suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  - P-256 ECDHE support
  - AES-128 GCM encryption
  - SHA-256 PRF/hash support
  - Public-key pinning support
  - Developers can find the SDK headers and client stubs in my github:
    https://github.com/amiga-stumpi/amitls13
  - Works with Amiga shared-library OpenLibrary() usage
  - Large TLS buffers allocated through AllocMem() to reduce stack pressure
  - Validated with stack 65000 in current smoke tests

  Requirements
  - AmigaOS compatible system
  - 68020 or better CPU
  - Working bsdsocket-compatible TCP/IP stack (e.g. TheWire13)
  - Recommended stack: 65000 bytes minimum, 131072 bytes preferred for larger
    applications

Important Note
--------------

AmiTLS13 currently accepts certificate chains without full CA/hostname
validation. Public-key pinning is available as an interim protection for known
endpoints. Full certificate validation is planned for a later version.

(c)2026 Marcel Jähne
If you like my work, you can spend me a coffee: paypal.me/mytubefree
:-)