Interop infrastructure
CI runners, macOS minutes, and the libcoap and libedhoc containers that every pull request runs against.
Sponsors
kcoap has no sponsors yet, and there is no way to sponsor it yet. Sponsorship will go through GitHub Sponsors or Open Collective; this page will link the account once one exists.
Why
kcoap is security code that people should read before they trust it, maintained by one person.
Its claims rest on things that cost money to keep running: interop against independent implementations on every pull request, CI on Linux and macOS, real devices to test on, and a review of the cryptographic code by someone other than its author.
Sponsorship gives no say over technical decisions, the roadmap, reviews or disclosure, and no early access to vulnerability information. Sponsors may say that they sponsor kcoap; calling themselves an official partner, or using the logo, needs written permission.
Sponsors will be listed in SPONSORS.md, in the README and on this page; details such as logos come with the accounts.
What it will fund
The same list as in SPONSORS.md and the governance document.
CI runners, macOS minutes, and the libcoap and libedhoc containers that every pull request runs against.
Phones, gateways and boards, so kcoap runs on real Android devices, iPhones and ARM gateways, not only in simulators.
An independent review of the OSCORE and EDHOC code and the crypto backends.
Time for the open items of the checklist, reviews, releases and answers.
kcoap.dev and the pages on it.
How the money is reported will be stated when the account is set up. With Open Collective, every income and expense is public.
Today
Money is one way to help. These help as much, and work today.
Ran kcoap against a device, a gateway or another CoAP, OSCORE or EDHOC implementation? Open an issue with what you ran, what you saw, and a capture if you have one. Results from real devices are what the project lacks most.
A behaviour that differs from an RFC is a bug. Cite the section, and say what kcoap did. SUPPORT.md says where each kind of report goes.
Open an issue before a large change. Tests come first, RFC vectors where they exist; every commit carries a DCO sign-off, and there is no CLA.
A guide that confused you is worth an issue or a pull request. The docs hub lists every page.
There is no official sponsorship, support, training or certification program yet; such programs exist only when this site lists them. If your organization wants to sponsor kcoap now, write to adrian.soltys@seelso.net.
Found a vulnerability? Do not open an issue: SECURITY.md says how to report it privately.