Forem: Zheng "Bruce" Li

P2P on steroids - Meet Surge

Zheng "Bruce" Li — Tue, 08 Dec 2020 17:29:06 +0000

Surge is a new alternative to Bit Torrent, claiming to be 100% secure, 100% decentralized, and 100% anonymous. And the client and network are both 100% open sourced and owned by the community: so full transparency and no adware or malware. It has a modern and sleek user interface, and very fast in downloading large files across the globe. Please give it a try! :-)

https://surge.rule110.io/

nMobile: the extra secure, sever-less and trusted chat app

Zheng "Bruce" Li — Tue, 04 Aug 2020 17:20:13 +0000

“The decisions we make about communication security today will determine the kind of society we live in tomorrow.” by Whitfield Diffie. Launching nMobile 1.0, the extra secure, trusted and server-less chat app powered by blockchain tech.
https://blog.nkn.org/nmobile-the-trusted-chat/

Encrypted Stream for net.Conn or io.ReadWriter

Zheng "Bruce" Li — Wed, 03 Jun 2020 20:41:10 +0000

It's surprising to find that no Golang library can easily transform a net.Conn to an encrypted and/or authenticated net.Conn. So I wrote one that works in one line, welcome to give it a try!

https://github.com/nknorg/encrypted-stream

Overview

Encrypted-stream is a Golang library that transforms any net.Conn or io.ReadWriter stream to an encrypted and/or authenticated stream.

The encrypted stream implements net.Conn and io.ReadWriter and can be used as drop-in replacement.

Works with any encryption, authentication, or authenticated encryption algorithm or even arbitrary transformation. Only a cipher that implements encrypt/decrypt needs to be provided. XSalsa20-Poly1305 and AES-GCM are provided as reference cipher.

The encrypted stream only adds a small constant memory overhead compared to the original stream.

Usage

Assume you have a net.Conn and you want to transform it into an encrypted net.Conn:

conn, err := net.Dial("tcp", "host:port")

You first need to have a shared key at both side of the connection, (e.g. derived from key exchange algorithm, or pre-determined). Then all you need to do is to choose or implements a cipher:

encryptedConn, err := stream.NewEncryptedStream(conn, &stream.Config{ Cipher: stream.NewXSalsa20Poly1305Cipher(&key), })

Now you can use encryptedConn just like conn, but everything is encrypted and authenticated.

See stream_test.go for complete example and benchmark with TCP connection.

Benchmark

$ go test -v -bench=. -run=^$
goos: darwin
goarch: amd64
pkg: github.com/nknorg/encrypted-stream
BenchmarkPipeXSalsa20Poly1305-12            4712        254008 ns/op     516.01 MB/s           1 B/op          0 allocs/op
BenchmarkPipeAESGCM128-12                  18675         65688 ns/op    1995.38 MB/s           0 B/op          0 allocs/op
BenchmarkPipeAESGCM256-12                  16060         74029 ns/op    1770.55 MB/s           0 B/op          0 allocs/op
BenchmarkTCPXSalsa20Poly1305-12             6760        263446 ns/op     497.53 MB/s           0 B/op          0 allocs/op
BenchmarkTCPAESGCM128-12                   14780         82979 ns/op    1579.57 MB/s           0 B/op          0 allocs/op
BenchmarkTCPAESGCM256-12                   13321         92393 ns/op    1418.64 MB/s           0 B/op          0 allocs/op
PASS
ok      github.com/nknorg/encrypted-stream  9.471s

NKN SDK: powering client side communication without servers

Zheng "Bruce" Li — Wed, 25 Mar 2020 17:31:01 +0000

What can developers do with NKN’s latest SDK, a decentralized communication stack that enables true peer to peer messaging, streaming, and file transfer? We would like to sort them into two main categories:

Things you can do ONLY with NKN SDK.
1. Send and receive data for free between any NKN powered apps regardless of their network condition without setting up a server or relying on any third party services.
2. Network agnostic: Neither sender nor receiver needs to have public IP address or port forwarding. NKN powered apps only establish outbound (websocket) connections, so Internet access is all they need. This is ideal for client side peer to peer communication.
Things you can do BETTER with NKN SDK
1. Top level security: All data are end to end authenticated and encrypted. No one else in the world except sender and receiver can see or modify the content of the data. The same public key is used for both routing and encryption, eliminating the possibility of man in the middle attack.
2. Decent performance: By aggregating multiple overlay paths concurrently, NKN powered apps can get ~100ms end to end latency and 10+mbps end to end session throughput between most international locations. This might sound modest, but it is actually faster than most file transfer services (e.g. instant messenger, gmail/google-drive, wetransfer.com, or dropbox)
3. Everything is free, open source and decentralized.

NKN recently combined three Javascript SDKs (client, multi-client and wallet) into a single one, and added several important new features that developers will love.

NKN Client: Send and receive data for free between any NKN clients regardless their network condition without setting up a server or relying on any third party services. Data are end to end encrypted by default. Typically you might want to use multiclient instead of using client directly.
NKN MultiClient: Send and receive data using multiple NKN clients concurrently to improve reliability and latency. In addition, it supports session mode, a reliable streaming protocol similar to TCP based on ncp.
NKN Wallet: Wallet SDK for NKN blockchain. It can be used to create wallet, transfer token to NKN wallet address, register name, subscribe to topic, etc.

Several example applications that are built on NKN SDK are:

nMobile: a secure mobile wallet and chat application.
- More information
- Google Play Store download
D-Chat: a decentralized chat as Chrome/Firefox browser extension.
- More information
- Gitlab
nFTP: a high throughput and direct file transfer between any clients

So if your application needs these unique communication capabilities of NKN, would like to simplify and get rid of the servers, or simply to reduce server costs, you can head to NKN’s Developer Portal as well as our github repository to get started:

https://www.nkn.org/developer/

https://github.com/nknorg/nkn-sdk-js