Joe Tsai 9294fd680e logtail/iopipe: new log buffer implementation
This adds a new ring buffer implementation that aims to replace
logtail.Buffer and the on-disk implementation in filch.Filch.

There are several problems with filch.Filch:

* Filching stderr should not be done at the buffer layer.
This makes more structured representation within the buffer
difficult as arbitrary stderr data may unexpectedly appear,
which hinders attempts at more structured data.

* Log messages are assumed to be discreet lines rather
than arbitrary bytes. This makes it harder to switch
the structured representation (e.g., using CBOR instead).

* Data that appears asynchronously through stderr
never triggers a wake-up within logtail.
Consequently logs may never be uploaded.

* Relatedly, there is no mechanism for notifying
that data has newly arrived in the buffer.

* There is no two-stage exfiltration.
The TryReadLine method may or may not persist the fact
that the data was read. It arbitrarily depends on whether
we cross a magical file boundary in the dual-file approach.
A failed upload followed by a restart results in dropped logs.
A successful upload followed by a restart results in duplicated logs.

The new Buffer interface and VolatileBuffer and PersistentBuffer
implementations are step in the direction to resolving these problems.

* In the future, filching will output to a separate pipe that
we explicitly process the data for, before putting it into the log buffer.
By processing the data, we can protect against stderr garbage being
inserted into the buffer unexpectedly breaking any structure.

* The Buffer.Peek and Buffer.Discard methods provide a way to
exfiltrate in a two-step manner. When uploading, we peek
at a chunk of data to upload. When successful, we discard the data,
ensuring that the buffer knows not to provide that data again.
The Len method can be used to suggest to the logging service
the amount of back pressure that exists.

Updates tailscale/corp#21363

Signed-off-by: Joe Tsai <joetsai@digital-static.net>
2025-09-23 14:12:32 -07:00
2025-08-28 15:12:19 -07:00
2025-04-02 07:36:04 -07:00
2024-04-16 15:32:38 -07:00
2025-08-28 15:41:07 -07:00
2025-04-08 09:18:38 -07:00
2024-03-08 15:24:36 -08:00
2025-07-24 12:25:57 -06:00

Tailscale

https://tailscale.com

Private WireGuard® networks made easy

Overview

This repository contains the majority of Tailscale's open source code. Notably, it includes the tailscaled daemon and the tailscale CLI tool. The tailscaled daemon runs on Linux, Windows, macOS, and to varying degrees on FreeBSD and OpenBSD. The Tailscale iOS and Android apps use this repo's code, but this repo doesn't contain the mobile GUI code.

Other Tailscale repos of note:

For background on which parts of Tailscale are open source and why, see https://tailscale.com/opensource/.

Using

We serve packages for a variety of distros and platforms at https://pkgs.tailscale.com.

Other clients

The macOS, iOS, and Windows clients use the code in this repository but additionally include small GUI wrappers. The GUI wrappers on non-open source platforms are themselves not open source.

Building

We always require the latest Go release, currently Go 1.23. (While we build releases with our Go fork, its use is not required.)

go install tailscale.com/cmd/tailscale{,d}

If you're packaging Tailscale for distribution, use build_dist.sh instead, to burn commit IDs and version info into the binaries:

./build_dist.sh tailscale.com/cmd/tailscale
./build_dist.sh tailscale.com/cmd/tailscaled

If your distro has conventions that preclude the use of build_dist.sh, please do the equivalent of what it does in your distro's way, so that bug reports contain useful version information.

Bugs

Please file any issues about this code or the hosted service on the issue tracker.

Contributing

PRs welcome! But please file bugs. Commit messages should reference bugs.

We require Developer Certificate of Origin Signed-off-by lines in commits.

See commit-messages.md (or skim git log) for our commit message style.

About Us

Tailscale is primarily developed by the people at https://github.com/orgs/tailscale/people. For other contributors, see:

WireGuard is a registered trademark of Jason A. Donenfeld.

Description
The easiest, most secure way to use WireGuard and 2FA.
Readme BSD-3-Clause 155 MiB
Languages
Go 95.5%
C 1.7%
TypeScript 1.1%
Shell 0.6%
Swift 0.3%
Other 0.5%