Skip to content

Releases

v11.1.518

Choose a tag to compare

@github-actions github-actions released this 15 Nov 15:22

C-Kermit 11.1.518

November 15, 2026

  • Fixed unit test building on 32-bit PowerPC/Linux.

  • During testing with a real US Robotics Courier modem, I observed RTS/CTS flow control settings were lost when the line moved out of CONNECT mode. It turns out that after CONNECT, INPUT, or OUTPUT, a Kermit or external protocol transfer ran with RTS/CTS off. CONNECT after a transfer had the same problem. The bug dates to C-Kermit 5A(190) in 1994, where it was introduced in commit 609e2f3. Half of this was fixed in 9.0.302 in 2010 (commit 0fd869b) but the other half was never fixed.

  • While looking into this, observed that SET FLOW XON/XOFF and KEEP were also broken by 9.0.302, in which packet mode disabled IXON and IXOFF for every flow setting. This contradicted the description in HELP SET FLOW. That change appears to have originated in a 2007 debugging experiment for ZMODEM over ptys. Corrected XON/XOFF and KEEP behavior.

  • HELP SET FLOW and HELP TRANSMIT document the existing and current behavior of TRANSMIT /BINARY: it disables XON/XOFF for the duration of the transmit.

  • After completing its work, TRANSMIT restored serial line settings to what they were when Kermit first opened the port. The next CONNECT, INPUT, OUTPUT, or Kermit protocol operation would put them back the way they should be. During that interval, data received could be mishandled. For instance, a CR from the other end could become LF with the default settings, so running INPUT after TRANSMIT could have a race with incoming data. Also, since the flow control settings were part of those reset, incoming data could be lost. TRANSMIT now follows the behavior of other commands and leaves the line in the settings requested by the user. The bug dates to C-Kermit 6.0.192 in 1996 (commit 4b5edde).

  • SET FLOW RTS/CTS had no effect on FreeBSD and MacOS. Kermit accepted the command, but never changed the setting on the line. SET FLOW KEEP also didn't preserve it. Both platforms now use the same termios code as Linux, NetBSD, and OpenBSD. This bug was present in every version back to C-Kermit 5A(190) in 1994.

  • Fixed a bug that caused an out-of-bounds array index in rare situations of a closed socket. First noticed by a CI failure on Debian/hppa.

  • Initial support for the GNU/Hurd operating system. Like Linux, it uses glibc, so the __GNU__ macro's presence usually works with paths that were designed for Linux.

  • CVEs have now been assigned for bugs fixed in C-Kermit 11.1.515. Updated the changelog entries for that version to reflect this.

v11.1.517

Choose a tag to compare

@github-actions github-actions released this 11 Nov 03:36

November 10, 2026

  • IKSD tests were failing on some distro CI systems that didn't set home directories.

  • Updated NetBSD platform notes.

  • Updated musl builds static library versions.

  • Fixed a test failure on NetBSD. The underlying investigation found an incompatibility between rz and IEXTEN on all three BSDs, which also occurs in contexts without Kermit. Documented this in doc/platforms.md.

v11.1.516

Choose a tag to compare

@github-actions github-actions released this 31 Oct 19:37

C-Kermit 11.1.516

Halloween 2026

  • The faultinj tests can have portability issues. Disable by default, but keep running in CI where they're most useful and I can directly control and test the environment better.

  • Fix tests such that a nonstandard path to iksd.conf will still work.

  • Added a static 32-bit x86 build, compatible down to the 486.

  • Fix for building on x32 (amd64 ISA with 32-bit pointers)

  • The musl static builds now carry built-in ncurses entries for common terminal types.

  • Fixed make linux+musl with ncurses.

  • Address some rare OpenBSD test flakes.

  • Fixed IKSD so it honors existing option SET TCP REVERSE-DNS-LOOKUP OFF, which can be used to speed up connection negotiation.

v11.1.515

Choose a tag to compare

@github-actions github-actions released this 31 Oct 01:41

C-Kermit 11.1.515

October 30, 2026

Summary

C-Kermit 11.1 is a correctness and security release. As part of preparing this release, over 900 compiler warnings were eliminated and a subsequent code review was performed. Additionally, the test suite received extensive attention, reducing the runtime for the full suite by 75% and finding additional bugs.

Where appropriate, descriptions of bugfixes identify the major C-Kermit version in which the bug was introduced and are prefixed with a tag (such as "[9]", indicating the bug was introduced in C-Kermit 9). History of C-Kermit only goes back to version 4, so bugs tagged as "[4]" may actually go back further.

Most bugfixes are accompanied by the introduction of new regression tests covering their situations.

Major Architectural Improvements

  • Eliminated over 900 -Wconversion warnings. Each conversion between integer types of different widths or signedness is now explicit or removed. This work identified numerous bugs, which are among those listed below.

  • Elimination of certain buggy internal SSL/TLS functions, which were duplicitive of those introduced in OpenSSL 1.0.2. Consequently, C-Kermit now needs OpenSSL 1.0.2 or later, or LibreSSL, for SSL and TLS. ck_ssl.h stops the build with an older OpenSSL. The code for OpenSSL 0.9.x, 1.0.0, and 1.0.1, is removed. OpenSSL 1.0.2 was released 21 years ago in 2015.

New Features

  • SET AUTHENTICATION SSL MINIMUM-VERSION { SSL3.0, TLS1.0, TLS1.1, TLS1.2, TLS1.3 } sets the lowest protocol version that Telnet, raw SSL/TLS, IKSD, HTTPS and FTP connections accept. The default is TLS1.2. OpenSSL 3 also needs @SECLEVEL=0 in the cipher list for a version older than TLS 1.2. SHOW AUTHENTICATION displays the setting.

  • SET FTP TLS-FALLBACK { ON, OFF } selects what FTP OPEN does when the server accepts AUTH TLS or AUTH SSL and the TLS session fails. OFF is the default and closes the connection. ON reconnects and tries the next authentication type. If none succeeds, ON logs in without encryption. Releases before 11.1 behaved as ON does.

  • SET FTP TRUST-PASV-ADDRESS { ON, OFF } selects the address of a passive-mode data connection. OFF, the default, connects to the control connection's address. ON connects to the address in the PASV reply, as releases before 11.1 did. It suits a server that names a different host for data.

  • SET HOST * 0 listens on a port the system chooses. The "Waiting to Accept" message names the port. The IPv4 and IPv6 sockets share it. If the port is in use for IPv6, SET HOST tries a new port, up to 8 times, and then warns and listens on IPv4 only.

Major Improvements

  • [8, 9] The default file-list string space on 64-bit builds is now 32MB instead of 2GB. Wildcard expansion allocates this space on first use. Lazy allocation on modern operating systems often hid the 2GB allocation. SET FILE STRINGSPACE raises the limit, and SHOW FILE displays it. SET FILE STRINGSPACE with a value of 1024 or less also failed. Commit 0fd869b introduced the 2GB default in C-Kermit 9.0.302 of 2011. Commit c88d9b8 introduced the STRINGSPACE bug in C-Kermit 8.0.200 of 2001.

Major Bugfixes

  • [6, 7, 8, 11] Fixed handling of files of size 2GB or above in several places. HTTP PUT and POST sent a wrong Content-Length. kermit -s and command-line FTP -p rejected 2-4 GB files. REMOTE DELETE skipped 2-4 GB files, and DELETE reported a wrong bytes-freed total. WAIT FILE treated a file of 2^32-1 bytes as deleted. HTTP Content-Length values over 2GB, or negative or empty ones, became 0, so a large download produced an empty file and reported success. Commit 4b5edde introduced the REMOTE DELETE and DELETE bugs in C-Kermit 6.0.192 of 1996. Commit d0f8b1d introduced the HTTP PUT/POST and WAIT bugs in C-Kermit 7.0.197 of 2000. Commit c88d9b8 introduced the -s, FTP -p, and HTTP Content-Length type bugs in C-Kermit 8.0.200 of 2001. Commit 42cfd07 introduced the clamp to 0 in C-Kermit 11.0.501 of 2026.

  • [8] Fixed FTP GET's handling of write errors. FTP GET in binary mode reported success when the local file could not be written, such as on a full disk, and left a truncated file. In text mode the failure came only from the server's reply, and SET FILE INCOMPLETE AUTO kept the partial file. Bug was introduced in commit c88d9b8, in C-Kermit 8.0.200 of 2001.

  • [11] GET or RECEIVE with an existing directory as the destination (e.g. get foo.txt /some/dir/) failed with "?Syntax error". A regression from the -Wshadow work, present in 11.0.511 through 11.0.514. Bug was introduced in commit 9be7054 in C-Kermit 11.0.511.

  • [11] INPUT on a TLS connection failed after one second with an I/O error. Bug was introduced in commit 4521c6b in C-Kermit 11.0.510 of 2026.

  • External protocol transfers (ZModem and similar):

    • [7] When the child process of SET HOST /PTY or an external protocol could not signal that its pty was ready, Kermit reported the connection as failed, but the child ran the command anyway. Kermit also left the pty open. Bug was introduced in commit d0f8b1d in C-Kermit 7.0.197 of 2000.

    • [9] A transfer could be reported as failed with "No files were transferred" after it succeeded. Bug dates from the introduction of ttptycmd() in C-Kermit 9.0.302 of 2011.

    • [9] Fixed several bugs that could cause the external program's last output to be lost. Bugs were introduced in commit 0fd869b in C-Kermit 9.0.302 of 2011.

    • [9] Ctrl-C during a transfer left the protocol program running with its pty open, and left the connection non-blocking. On systems without openpty(), it also left SIGCHLD ignored for the rest of the session. Bugs were introduced in commit 0fd869b in C-Kermit 9.0.302 of 2011.

    • [9, 11] Fixed a bug relating to buffering external protocol data, significantly improving performance. The code that waited was introduced in commit 0fd869b in C-Kermit 9.0.302 of 2011. Commit 04e8275 in C-Kermit 11.0.501 replaced the wait with the 100 ms poll. Commit ce6628a in C-Kermit 11.0.509 introduced the 2-second stall.

    • [11] On the BSDs, an external protocol over a SET HOST /PTY connection didn't notice when the connection ended. Bug was introduced in commit dab36d9 in C-Kermit 11.0.501.

    • [11] An external protocol over an SSL or TLS connection held each burst of incoming data for 2 seconds. lrz 0.13 gave up on the transfer and older versions were slow. Bug was introduced in commit 04e8275 in C-Kermit 11.0.501 of 2026. Bug originally reported at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150880

Security and Reliability Improvements

C-Kermit 11.1 corrects these security issues. Most issues tagged "[11]" fall into one of two categories: tighter security defaults in C-Kermit 11.0 exposed weaknesses in older code, and hardening code added in 11.0 had gaps. Few are corrections for security regressions in 11.0, aside from SET COMPATIBILITY.

File transfer and the server

  • [4] A Kermit server ran REMOTE WHO and REMOTE SPACE through the shell with the client's text unquoted. remote who {x;touch y} ran a command on the server even with DISABLE HOST. The server now runs who and df via exec() without the shell. A Unix server refuses a REMOTE WHO name, since that never worked anyway, and it was interpreted as a file rather than a username. This appears to have been broken on Unix hosts since the very beginning. A REMOTE SPACE argument must name an existing directory. A REMOTE SPACE directory name with spaces now works. A command too long for the command buffer is refused instead of overflowing it. Bug dates from C-Kermit 4C(057) of 1985. GHSA-c5px-7h4c-gj8p. Fixes CVE-2026-129124.

  • [4] A Kermit server or receiver now refuses a server command, GET command, or file name that decodes to more than its command buffer holds. Before, repeat counts could make such a packet write past the buffer. This bug was present in the oldest extant version of C-Kermit. GHSA-c5px-7h4c-gj8p. Fixes CVE-2026-129126.

  • [4, 5, 6, 7] The server trusted the field lengths in generic commands, Extended GET parameters, attribute packets and REMOTE SET. A length past the data made it read stale buffer contents. REMOTE SET values were also stored without range checks. REMOTE LOGIN copied a user name of up to 255 bytes into a 64-byte stack buffer in builds without BIGBUFOK. REMOTE CD, COPY and RENAME took a last field over 94 characters as empty, so REMOTE CD went to the home directory. Each field is now checked. The REMOTE CD bug was introduced in commit 16d830e in C-Kermit 4F(095) of 1989. The others were introduced in commits a213649 (5A(188) of 1992), 609e2f3 (5A(190) of 1994), 4b5edde (6.0.192 of 1996) and d0f8b1d (7.0.197 of 2000).

  • [4, 5, 7] Malformed packets were accepted or read past their data. A packet whose data ended with a repeat, control or 8th-bit prefix and no operand was incorrectly decoded with the operand taken from the block check. A trailing repeat prefix wrote 224 copies of a block check byte to the file. Such a packet now ends the transfer with the error "Malformed packet data". A packet whose length was shorter than its block check passed with a negative data length. With an extended header of length 0, the header check served as the block check, so a packet of any type was accepted. Such a packet is now refused as a bad length. A malformed packet could leave a sequence number outside 0-63 that was later used as a table index. rpack() computed the block check of a packet that claimed more bytes than arrived over unwritten buffer space. spar() read past the Send-Init parameters it was given. Bugs were introduced in commits f16b451 (4C(057) of 1985), 9438f56 (4E(072) of 1989), a213649 (5A(188) of 1992) and d0f8b1d (7.0.197 of 2000).

  • [5] Attribute handling read and wrote outside its buffers. A recei...

Read more

v11.0.514

Choose a tag to compare

@github-actions github-actions released this 01 Oct 01:57

C-Kermit 11.0.514

September 30, 2026

  • Fixed a bug in a test that could cause a spurious failure with certain-sized tmpdirs. Fixes #40. Making a new release with the fix to unblock Fedora.
  • Fixed a bug in tests where an IPv6 port collision while testing was mishandled.

v11.0.513

Choose a tag to compare

@github-actions github-actions released this 30 Sep 15:57

C-Kermit 11.0.513

September 30, 2026

  • Fixed the armhf binary build in Github CI. The platform was already being tested, but the final binaries weren't being built.

  • On platforms where long is 32 bits but time_t is 64 bits, keep received times in excess of the 32-bit limit intact, skipping an unnecessary conversion truncation. This bug dates back to C-Kermit 5A of 1992 in commit a213649 and threads through changes since.

  • Added additional tests for time_t that run everywhere, including platforms where time_t is 32 bits. Some of the tests added previously intentionally skip on those platforms, as they were validating proper 64-bit operation. This ensures adequate coverage everywhere.

  • Fix a bug in which tests could fail when started locally with a controlling tty (as opposed to the CI environment which lacks that).

v11.0.512

Choose a tag to compare

@github-actions github-actions released this 30 Sep 05:58

C-Kermit 11.0.512

September 30, 2026

This is primarily a cleanup and maintenance release. I have been adding numerous tests in anticipation of more work reducing warnings on modern toolchains, with the aim of having a good chance of catching any accidental regressions. Along the way, the tests and analysis have surfaced some bugs, which have been fixed.

Additionally, due to being broken for over 25 years and the impracticality of restoring support, I removed support for 16-bit Unix platforms from the codebase. This removed over 1900 lines of code from the project. See further notes in commit 30ab9d4. For instance, I had made a solid effort to get C-Kermit to build again on 2BSD on PDP-11, but according to the historic notes, C-Kermit 7 was already iffy on that platform, and the last real published binaries were from C-Kermit 6. Memory issues with the compiler, preprocessor, and compiled binaries were significant and insurmountable without significantly harming both the maintainability of the code and the featureset present on the old platforms.

At the same time, I added the first 32-bit platform as part of CI, which is 32-bit Linux armhf. This serves the twin goals of providing a useful binary for platforms such as Raspberry Pi, and providing a measure of validation in CI that we don't break things on 32-bit platforms.

Additional changes:

  • Behavior change: In some cases, particularly when reliable isn't assumed, file names could be silently truncated if they were larger than would fit in a single packet. Now, an error packet is generated and returned if the filename would require truncation. This is an unusual case impacting files with very long names, so I don't think it likely anyone will notice this change, but it should avoid unpleasant surprises.

  • Behavior change: rounding -0 now produces 0 instead of -0.

  • Report sizeof(time_t) in SHOW FEATURES and associated regression test. Note 32-bit Linux platforms have transitioned to 64-bit time_t, but this is not universally true across the BSDs, so we don't require 64-bit time_t on every CI platform.

  • Fix a number of time-related overflows.

  • Fix a heap buffer overflow in getlocalipaddrs() and add associated test. 64-bit platforms try to read 8 bytes from a 4-byte allocation. However, on Linux at least, this isn't an exploitable security hole as malloc() on Linux allocates more than 8 bytes at a time anyhow. The original bug was introduced when the code in question was written, in C-Kermit 7.0.197 of 2000, commit d0f8b1d.

  • Close pipe fds on exec where appropriate. This prevents leakage and issues with failing to shut down.

  • Added testing for \fsexpression() past 4GB. Fixed \fsexpression() wrong results near the 2^53 double boundary, discovered by new tests.

  • Fixed handling in cases where a filename length causes a packet to exceed the current packet size.

  • Fixed invalid JPEG segment length handling in \fpictureinfo()

  • Fixed FILE COUNT for files >2GB in size on platforms that support a 64-bit CK_OFF_T. Platforms that don't support that won't support large file size reporting anyhow.

  • Fix incorrect handling of file dates before 1970 or after 2106.

  • Fix a shxpand() buffer overflow, detected with ASan.

  • SHOW TERMINAL now properly will reflect SET TERMINAL AUTODOWNLOAD ASK on all platforms.

  • Fix building unit tests on ppc64 platforms.

  • Fix IPv6 tests on systems were /etc/hosts gives a name for ::1 that isn't localhost.

  • Reject a SEND AS-NAME that doesn't fit in a buffer instead of leaking stack.

  • Fixed an asan-detected issue in newerrmsg()

  • When a SEND or GET switch is given more than once, fixed edge cases that could cause a double free.

  • Used safer string generation for switch values and login names (makestr() instead of malloc() and strcpy())

  • Correct an obscure data corruption bug that could occur when a telnet command arrives at a certain buffer boundary.

  • Several chunk length handling fixes in the HTTP client code:

    • Fixed a length truncation bug on 64-bit platforms and added a regression test for it. The original bug was introduced in C-Kermit 8.0.200 of 2001, commit c88d9b8.
    • Use CK_OFF_T instead of int for the chunk size, causing 32-bit platforms to use a 64-bit size, enabling support for large chunks on 32-bit platforms.
    • Fixed parsing the chunk size when an extension (beginning with a semicolon) follows it. Previously, it would truncate a numeric digit.
  • Added numerous additional tests:

    • Validating off_t and general large file (>2GB, >4GB) support on 32-bit and 64-bit platforms
    • For DIR and DIR /SUMMARY with files >4GB, including on 32-bit platforms
    • For REGET resuming files >4GB, validating encoding/decoding large file sizes in the Kermit protocol
    • Testing \fsexpression() past 4GB.
    • Added a test for telnet IAC negotiation.
    • Generally, many regression tests in preparation for work to remove -Wconversion warnings.
    • Tests for filename length, including the prompt in autodownload ask mode.
    • Tests for username length.
    • Testing \fjoin CSV quoting of a large field.
    • Testing GET handling of large patterns for /MOVE-TO, /AS-NAME, /FILTER, and /EXCEPT with large parameters.
    • Testing SEND, CONNECT, and ADD SEND-LIST with values >255 chars.
    • Test IKSD login with large username and password.
    • Direct telnet and FTP tests with supplied protocol data

v11.0.511

Choose a tag to compare

@github-actions github-actions released this 19 Sep 20:28

C-Kermit 11.0.511

September 19, 2026

  • Continued the warning sweep begun with 11.0.509. Addressed numerous -Wshadow warnings.

  • CI: Allowed retrying of certain timing-dependent tests due to flakiness on Mac and OpenBSD.

  • Tests: Set a 2-second timeout on IPv6 tests expected to fail.

v11.0.510

Choose a tag to compare

@github-actions github-actions released this 18 Sep 04:41

C-Kermit 11.0.510

September 17, 2026

  • Refactor to reduce use of siglongjmp(), eliminating races

  • Added SET TCP CONNECT-TIMEOUT to provide a new timeout for establishing a TCP connection, defaulting to 30 seconds. This can be useful for scripts and tests. The previous default was no timeout enforced by C-Kermit; setting this value to 0 will restore that behvior.

  • Continued the warning sweep begun with 11.0.509. Along the way, fixed these bugs:

    • A chmod failure was ignored when SET ATTRIBUTE PROTECTION is on. Fixed in commit 4ddb464. Bug dates back to C-Kermit 7.0.197 of 2000, commit d0f8b1d, when this code was introduced.
  • Include time.h earlier in ckcnet.c to address compilation issue on Gentoo

v11.0.509

Choose a tag to compare

@github-actions github-actions released this 21 Aug 01:50
  • Fixed a bug in statements like \fcvtdate(..., -4) where there was no space between the day and the year, producing outputs like Sat Nov 262005 instead of Sat Nov 26 2005.

  • Fixed an out-of-bounds month lookup in shuffledate() for month values outside 1-12, and corrected off-by-one whitespace stripping in date parsing. Added unit tests for these date-handling functions.

  • Fixed an issue where SIGWINCH window-resize signals were not forwarded to child processes after running an external protocol such as Zmodem.

  • Fixed pty cleanup after external protocol execution, preventing a transfer-interrupting Ctrl-C from terminating PTY connections.

  • Fixed a bug in the telnet buffer processing loop that could cause individual or repeated 1-second stalls in certain circumstances

  • Enable SET DEBUG TIMESTAMPS during tests to help pinpoint timeouts and performance problems

  • Save off localtime() results in zdtstr()/zstrdt() to prevent mtime skew when SET DEBUG TIMESTAMPS is ON.

  • Converted tabs to spaces in the source. Inconsistent use of tabs vs. spaces was causing confusion, for humans and also possibly for gcc with -Wmisleading-indentation. This was done using the expand(1) command.

  • Ran with various warning-enable options, cleaning up warnings along the way.

  • Fixed bugs identified during the warning sweep:

    • Corrected operator precedence grouping in \femail().
    • Fixed array indexing with signed char.
    • Fixed uninitialized seek offsets in FILE SEEK.
    • Fixed an uninitialized buffer read during DNS TXT record lookups.
    • Fixed a comment-parsing defect in cmcvtdate().
    • Replaced an unbounded vsprintf() in ckxprintf() with vsnprintf() and added GCC format attributes to printf wrappers.
    • Fixed a potential buffer overflow in UNIX domain socket path handling in ckcnet.c.
    • SET DIAL TIMEOUT reset DIAL ESCAPE-CHARACTER to 43. Also, an unexpected DIAL STRING parameter caused control to pass to DIAL FLOW-CONTROL. These bugs introduced in C-Kermit 6.0.192 of 1996, commit 4b5edde.
    • REPEAT and CD switch value handling could fall into handler for different commands.
    • \funtab() with a parameter over the maximum length would fall into \funhex().
    • FILE SEEK /FIND without an argument corrupted rsize.