| 1 |
Source: golang-github-arceliar-ironwood |
| 2 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 3 |
Uploaders: John Goerzen <[email protected]> |
| 4 |
Section: golang |
| 5 |
Testsuite: autopkgtest-pkg-go |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13), |
| 8 |
dh-golang, |
| 9 |
golang-go (>= 2:1.25~0), |
| 10 |
golang-github-arceliar-phony-dev (>= 0.0~git20220903), |
| 11 |
golang-github-bits-and-blooms-bloom-dev (>= 3.7.1), |
| 12 |
golang-github-bits-and-blooms-bitset-dev (>= 1.24.4), |
| 13 |
golang-golang-x-crypto-dev (>= 0.51.0) |
| 14 |
Standards-Version: 4.6.0 |
| 15 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-arceliar-ironwood |
| 16 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-arceliar-ironwood.git |
| 17 |
Homepage: https://github.com/Arceliar/ironwood |
| 18 |
Rules-Requires-Root: no |
| 19 |
XS-Go-Import-Path: github.com/Arceliar/ironwood |
| 20 |
|
| 21 |
Package: golang-github-arceliar-ironwood-dev |
| 22 |
Architecture: all |
| 23 |
Multi-Arch: foreign |
| 24 |
Depends: golang-github-arceliar-phony-dev (>= 0.0~git20220903), |
| 25 |
golang-github-bits-and-blooms-bloom-dev (>= 3.7.1), |
| 26 |
golang-github-bits-and-blooms-bitset-dev (>= 1.24.4), |
| 27 |
golang-golang-x-crypto-dev (>= 0.51.0), |
| 28 |
${misc:Depends} |
| 29 |
Description: Routing library with public keys as addresses (library) |
| 30 |
Ironwood is a routing library with a net.PacketConn-compatible interface |
| 31 |
using ed25519.PublicKeys as addresses. Basically, you use it when you |
| 32 |
want to communicate with some other nodes in a network, but you can't |
| 33 |
guarantee that you can directly connect to every node in that network. |
| 34 |
It was written to test improvements to / replace the routing logic in |
| 35 |
Yggdrasil (https://github.com/yggdrasil-network/yggdrasil-go), but it may |
| 36 |
be useful for other network applications. |
| 37 |
. |
| 38 |
Note: Ironwood is pre-alpha work-in-progress. There's no stable API, |
| 39 |
versioning, or expectation that any two commits will be compatible with |
| 40 |
each other. Also, it hasn't been audited by a security expert. While the |
| 41 |
author is unaware of any security vulnerabilities, it would be wise to |
| 42 |
think of this as an insecure proof-of-concept. Use it at your own risk. |