Search Criteria
Package Details: tuwunel-git 0.5.0.5108.geb2949d6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/tuwunel-git.git (read-only, click to copy) |
---|---|
Package Base: | tuwunel-git |
Description: | successor to conduwuit with stable governance |
Upstream URL: | https://github.com/matrix-construct/tuwunel |
Keywords: | conduit conduwuit fork git rust tuwunel |
Licenses: | Apache-2.0 |
Conflicts: | conduwuit |
Provides: | conduwuit, tuwunel |
Submitter: | Kimiblock |
Maintainer: | None |
Last Packager: | Kimiblock |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2025-04-17 05:14 (UTC) |
Last Updated: | 2025-04-17 05:14 (UTC) |
Dependencies (12)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-eacAUR)
- liburing (liburing-gitAUR)
- autoconf (autoconf-gitAUR) (make)
- cargo (rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rustup-gitAUR, rust, rustup) (make)
- clang (llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- libc++ (libc++-with-libunwindAUR, libc++-msanAUR) (make)
- linux-api-headers (make)
- linux-headers (make)
- llvm (llvm-gitAUR, llvm-minimal-gitAUR) (make)
- rust (rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rustup-gitAUR, rustup) (make)
Latest Comments
Kimiblock commented on 2025-07-24 04:51 (UTC)
Dropping because maintainers has been banned by the foundation
Kimiblock commented on 2025-07-24 04:14 (UTC)
Warnings ahead, quoted from https://matrix.to/#/!offtopic-2:continuwuity.org/$WexE0LUPdFLu6s-rCR_OQ6VrCjYnGbEjvXZZVTylOXI?via=nexy7574.uk&via=matrix.org&via=continuwuity.org:
Keep in mind the claim of being official is not true: this is a claim by one of the former co-maintainers of conduwuit, to claim legitimacy over other projects like continuwuity. Additionally, tuwunel's maintainer has openly made threats against the maintainers of continuwuity, aswell as being formally banned from the foundation for actively abusing protocol exploits. I'm not sure I'd trust a project primarily maintained by them for these reasons. Additionally, it's maintainer appears to currently also be pushing for publishing how to exploit the security vulnerabilities from the upcoming security release.
claim legitimacy over or de legitimise other projects:
threats against the project:
personal threats:
attempting to get security details released early (knowing only he and two other servers have finished implementing):