Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
tcpflow — TCP/IP packet demultiplexer. Download from: | Kitploit
도구/GitHubGitHub/simsong/tcpflow
Packet Sniffing & AnalysisNetwork ForensicsForensicsDigital Forensics
GitHubsimsong/tcpflow

tcpflow

TCP/IP packet demultiplexer. Download from:

저장소 보기
1.8k2454510일 전Kitploit 검토 완료
공유
웹사이트
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

TCPFLOW CI (c++14)

TCPFLOW 1.7.0

Downloads: https://github.com/simsong/tcpflow/releases

CI and releases

The Autotools build is the supported CI and release path. Run checks from a checkout with make -f Makefile.ci bootstrap native; distcheck also rebuilds, tests, installs and uninstalls the generated source distribution. After ./configure, make ci builds and tests the current build directory, including in-tree builds; its regression tests run serially. Separate asan, tsan, ubsan, clang-analyzer, clang-tidy, cppcheck, and coverage targets use isolated .build/ directories. CI also runs Windows runtime tests, Debian compatibility and FreeBSD/OpenBSD checks. CodeQL runs separately through the repository's existing GitHub default setup. See the detailed CI/release procedure and comparison with the reference repositories.

An annotated v<version> tag on a commit already merged into main triggers all release gates and produces a source .tar.gz, native amd64/arm64 .snap packages, an Authenticode-signed standalone tcpflow64.exe, and SHA256SUMS. The EXE requires no application DLLs and processes offline PCAP files; its build does not include live capture, BPF filters, Wi-Fi decoding or Cairo PDF reports. Windows replaces colons in generated IPv6/MAC/timestamp filename components with underscores; network address values in reports retain their normal format. The Snaps retain native PCAP/PDF support and are published only on GitHub. The workflow verifies the complete draft's downloads before publishing it.

Configuration (never put secret values in source files):

VariablePurpose
CI_JOBSParallel compilation jobs, default 2; shell regressions run serially.
CI_BUILD_ROOTIsolated build/report root, default .build under the invoking directory.
CONTAINER_ENGINE, CHECKContainer CLI (default finch) and Makefile.ci targets for container-check.
CC, CXX, CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS, LIBS, PKG_CONFIG_LIBDIRStandard compiler, include/library and target pkg-config settings.
SDKROOTInstalled macOS SDK selected explicitly for local Clang analysis.
ASAN_OPTIONS, TSAN_OPTIONS, UBSAN_OPTIONSSanitizer runtime diagnostics; CI stops on errors and enables Linux leak detection.
WINDOWS_DEPSStatic MinGW dependency prefix for the windows target.
VCPKG_ROOT, VCPKG_COMMITWindows dependency directory and pinned vcpkg revision in CI.
SNAPCRAFT_BUILD_ENVIRONMENTSnapcraft build provider; CI uses lxd.
FONTCONFIG_FILE, XDG_CACHE_HOMESnap-provided bundled-font configuration and writable font-cache location for PDF reports.
RELEASE_TAG, RELEASE_COMMITAnnotated version tag and exact immutable source commit for preflight.
EXEStandalone executable path for windows-test.
CODECOV_TOKENGitHub secret for authenticated coverage submission.
AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_SUBSCRIPTION_IDNon-secret identity settings for GitHub OIDC login.
AZURE_SIGNING_ENDPOINT, AZURE_SIGNING_ACCOUNT, AZURE_SIGNING_PROFILENon-secret Artifact Signing service/profile settings.
WINDOWS_PUBLISHERExact public certificate subject required by the signature verifier.
GH_TOKENWorkflow-provided GitHub token for draft creation, download verification and publication.

GitHub supplies GITHUB_* and RUNNER_* context variables. Signing is restricted to the protected windows-signing environment; no private signing key is stored in the repository. CMake remains a legacy build path and is not a release gate.

Installation

Most common GNU/Linux distributions ship tcpflow in their repositories. So on Debian/Ubuntu/etc you can say

sudo apt-get install tcpflow

and on Fedora/RedHat/CentOS/etc you can say

sudo dnf install tcpflow

And that's it. If this isn't good-enough for whatever reason, you can build from source:

Building from source

To compile for Linux

Be sure you have the necessary precursors. There are files in the root directory that will do this for you, depending on your host operating system:

CONFIGURE_ARCH_17_8.sh CONFIGURE_FEDORA_18.sh CONFIGURE_FEDORA_26.sh CONFIGURE_UBUNTU_16_04.sh

Depending on your OS, just:

# sudo bash CONFIGURE_<YOUROS>.sh

Once you have configured your OS, compile and install with:

./configure
make
sudo make install

If you want do download the development tree with git, be sure to do a complete checkout with --recursive and then run bootstrap.sh, configure and make:

git clone --recursive https://github.com/simsong/tcpflow.git
cd tcpflow
bash bootstrap.sh
./configure
make
sudo make install  

To download and compile for Amazon AMI:

ssh ec2-user@<your ec2 instance>
sudo bash yum -y install git make gcc-c++ automake autoconf boost-devel cairo-devel libpcap-devel openssl-devel zlib-devel
git clone --recursive https://github.com/simsong/tcpflow.git
sh bootstrap.sh

To Compile for Windows with mingw on Fedora Core:

yum -y install mingw64-gcc mingw64-gcc-c++ mingw64-boost mingw64-cairo mingw64-zlib
mingw64-configure
make

To use CMake, see detailed instructions: cmake/README.md

Build RPM

From a clean repository as normal user (not root):

./bootstrap.sh     # Generates the file ./configure
./configure        # Generates the file tcpflow.spec
rpmbuild -bb tcpflow.spec --build-in-place

Check the specfile and resulted RPM:

rpmlint tcpflow.spec
rpmlint ~/rpmbuild/RPMS/x86_64/tcpflow-....rpm

Install:

sudo dnf install ~/rpmbuild/RPMS/x86_64/tcpflow-....rpm

Introduction To tcpflow

tcpflow is a program that captures data transmitted as part of TCP connections (flows), and stores the data in a way that is convenient for protocol analysis and debugging. Each TCP flow is stored in its own file. Thus, the typical TCP flow will be stored in two files, one for each direction. tcpflow can also process stored 'tcpdump' packet flows.

tcpflow stores all captured data in files that have names of the form:

   [timestampT]sourceip.sourceport-destip.destport[--VLAN][cNNNN]

where: timestamp is an optional timestamp of the time that the first packet was seen T is a delimiter that indicates a timestamp was provided sourceip is the source IP address sourceport is the source port destip is the destination ip address destport is the destination port VLAN is the VLAN port c is a delimiter indicating that multiple connections are present NNNN is a connection counter, when there are multiple connections with the same [time]/sourceip/sourceport/destip/destport combination.
Note that connection counting rarely happens when timestamp prefixing is performed.

HERE are some examples:

   128.129.130.131.02345-010.011.012.013.45103

The contents of the above file would be data transmitted from host 128.129.131.131 port 2345, to host 10.11.12.13 port 45103.

   128.129.130.131.02345-010.011.012.013.45103c0005

The sixth connection from 128.129.131.131 port 2345, to host 10.11.12.13 port 45103.

   1325542703T128.129.130.131.02345-010.011.012.013.45103

A connection from 128.129.131.131 port 2345, to host 10.11.12.13 port 45103, that started on at 5:19pm (-0500) on January 2, 2012

   128.129.130.131.02345-010.011.012.013.45103--3
도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

아직 인기 데이터가 없습니다.

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →