noise
wireguard-vyatta-ubnt
noise | wireguard-vyatta-ubnt | |
---|---|---|
7 | 273 | |
502 | 1,434 | |
0.4% | 0.0% | |
3.9 | 0.0 | |
3 months ago | over 1 year ago | |
Go | Shell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
noise
-
A simple, (as-of-yet unidentified) asymmetric Authenticated Key Exchange
This is Noise IK (possibly with minor differences in the hashing):
https://noiseprotocol.org/
Wireguard uses NoiseIK, plus a static public key for the initiator which is encrypted to the agreed-upon-session-key without adding additional round trips. Your protocol simply omits the parts related to the initiator's static public key, because it has none.
-
Show HN: Willow – Open-Source Privacy-Focused Voice Assistant Hardware
With regard to this:
> - On the wire/protocol stuff. We're doing pretty rudimentary "open new connection, stream voice, POST somewhere". This adds extra latency and CPU usage because of repeated TLS handshakes, etc. We have plans to use Websockets and what-not to cut down on this.
I've recently used the Noise protocol[1] to do some encrypted communication between two services I control but separated by the internet.
It was surprisingly easy!
[1]: https://noiseprotocol.org/
-
How much secure is my UDP based network protocol?
Rolling your own initial handshake is hard. Right now I strongly encourage you take a look at the Noise protocol framework. Specifically the XK and IK patterns for identified clients, and the NK pattern for anonymous clients. The best security will be achieved by the XK pattern, but if you need to reduce the number of messages to a minimum IK might be a bit more attractive. (Also, if I recall correctly IK is used by Wireguard, so there's an example to follow).
- Noise Protocol Framework
-
Rosenpass – formally verified post-quantum WireGuard
Rosenpass author here;
There is a confusion about terminology here I think. Mathematical proofs including cryptography proofs use models simplifying reality; i.e. the real practical system might still be susceptible to attacks despite a proof of security.
For crypto primitives (classic mc eliece, curve25519, ed25519, RSA, etc etc) the standard for proofs is currently showing that they are as hard as some well studied mathematical problem. This is done by showing that an attack on the primitive leads to an attack on the underlying mathematical primitive. The proof for Diffie-Hellman shows that attacking DH leads to an efficient solution for the discrete log problem. I.e. the proof is a reduction to the underlying primitive.
No primitive is perfectly secure (at least a brute force – i.e. guessing each possibility is possible); there is some probability that the adversary can guess the right key. We call this probability the adversary's advantage. One task in cryptoanalysis is to find better attacks against primitives with a higher advantage; if an attack with a polynomial time average runtime is found, the primitive is broken. Finding a higher non-polynomial attack is still an interesting result.
The standard for protocols is proving that the protocol is secure assuming the primitives are secure; since multiple primitives are used you basically get a formula deriving an advantage for breaking the entire protocol. The proof is a reduction to a set of primitives.
We did not build a proof in that gold standard, although we are working on it. We built a proof in the symbolic model – known as a symbolic analysis. This uses the perfect cryptography assumption; i.e. we assumed that the advantages for each primitive are zero. Google "Dolev-Yao-Model".
This makes the proof much easier; a proof assistant such as ProVerif can basically find a proof automatically using logic programming methods (horn clauses).
The definitions of security are fairly well understood; unfortunately there is a lot to go into so I can't expand on that here. Looking up "IND-CPA" and "IND-CCA" might be a good start; these are the security games/models of security for asymmetric encryption; you could move on to the models for key exchange algorithms there. Reading the [noise protocol spec](https://noiseprotocol.org/) is also a good start.
-
Whisper: Wraps any Go io.ReadWriter in a secure tunnel using Ed25519/X25519
There is no description of the protocol or of its security goals, so I am making some guesses based on a cursory look at the source and what I imagine this might be for.
A single symmetric key is derived for both directions, and there is no checking of nonces, so as far as I can tell any message can be dropped, reordered, or replayed in both directions. (Including replaying message from A to B as if they were from B to A.)
This is a bit like using ECB and likely to lead to fun application-specific attacks like [0].
This is very much rolling your own crypto, in a dangerous way. I am on the record as being "against" the "don't roll your own crypto" refrain [1], but mostly because it doesn't work: it should discourage people from publishing hand-rolled protocols such as this, but instead people think it means "don't roll your own primitives" and accept the use of "Ed25519/X25519" as probably secure.
Please read about the Noise framework [2] to get an idea of how much nuance there is to this, and consider using a Go implementation of it [3] instead.
P.S. This kind of issue is also why I maintain that NaCl is not a high-level scheme [4]: this could have used NaCl and have the exact same issues. libsodium has a couple slightly higher-level APIs that could have helped, secretstream [5] and kx [6], but again please use Noise.
[0] https://cryptopals.com/sets/2/challenges/13
[1] https://securitycryptographywhatever.buzzsprout.com/1822302/...
[2] https://noiseprotocol.org/noise.html
[3] https://github.com/flynn/noise
[4] https://words.filippo.io/dispatches/nacl-api/
[5] https://libsodium.gitbook.io/doc/secret-key_cryptography/sec...
[6] https://libsodium.gitbook.io/doc/key_exchange
wireguard-vyatta-ubnt
-
AWS Lambda Serverless Security. Mistakes, Oversights, and Potential Vulnerabilities
Joining serverless environments like AWS Lambda to a mesh network has traditionally been difficult because you can't directly access the network interfaces on the hosts that run your functions. The NetBird netstack mode addresses this by providing a simulated TUN device and a SOCKS5 proxy that targets that device. This allows your Lambda function to access other services in your NetBird network via the proxy.
-
Using NetBird for Kubernetes Access
NetBird simplifies Kubernetes access with its zero-configuration approach, leveraging WireGuard's simplicity and strength. It seamlessly integrates with various tools, offering transparency and high reliability as an open source solution.
-
Building a Managed Service Provider Business With Open Source
WireGaurd
-
This is what i came home to after work today
As for remote access, you will need another computer to install tailscale or wireguard vpn to access your local devices https://www.youtube.com/watch?v=AkKz7Vza1rw and the official docs for up to date advice https://www.wireguard.com/ this doesn't require much to run, you can use any old family computer or some old quad core 2nd-4th gen intel desktop for 30 bucks off facebook marketplace. You can also use that same computer to run klipper if you install proxmox and have two separate linux virtual machines.
- A word of caution about Tailscale
-
Como não aparecer no I Know What You Download
Um modo mais avançado de se proteger é utilizando protocolos de VPN mais modernos, como o WireGuard. Muitos provedores de VPN oferecem suporte a este protocolo, que além de muito simples de usar e além do mais é open source.
-
Suggest VPNs for torrents?
here u find out how wireguard works https://www.wireguard.com/
-
Netmaker - WireGuard Made Easy
WireGuard is a VPN protocol developed several years ago which is exremely fast, lightweight, and uses state-of-the art cryptography. Its performance blows legacy VPN's out of the water.
-
IVPN wireguard key rotation
Try vanilla. It solved all my problems bar none.
- Can someone help-me to set a SSTP VPN on macOS ventura?
What are some alternatives?
willow - Open source, local, and self-hosted Amazon Echo/Google Home competitive Voice Assistant alternative
ZeroTier - A Smart Ethernet Switch for Earth
rosenpass - Rosenpass is a post-quantum-secure VPN that uses WireGuard to transport the actual data.
tailscale - The easiest, most secure way to use WireGuard and 2FA.
FastNoise - Fast Portable Noise Library - C# C++ C Java HLSL GLSL JavaScript Rust Go
frp - A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
imagemagick - haskell imagemagick bindings
Netmaker - Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
whisper - Wraps an io.ReadWriter in a secure tunnel using modern elliptic-curve cryptography.
wireguard-ui - Wireguard web interface
matplotlib - Haskell bindings for Python's Matplotlib
authelia - The Single Sign-On Multi-Factor portal for web apps