v0.1.5

autonat

v0.1.4

Full Changelog: v0.1.3...v0.1.4

Introduction

scs has been a TCP based sharing program, but for efficiency and faster sending times, the QUIC transport protocol was added. This release introduces QUIC to scs as the default protocol and then falls back to TCP if QUIC is not available.

v0.1.3

What's Changed

• Fix: IP Address Validation by @Lilit0x in #4
• Peer ID personalization by @Lilit0x in #5
• Saving Recipients Info by @Lilit0x in #6

Full Changelog: v0.1.2...v0.1.3

Introduction

This release adds a personalization feature to scs.

Features

1. Enables a deterministic PeerId by setting a seed key in the config file.
2. Saving peer information.

v0.1.2

Full Changelog: v0.1.1...v0.1.2

Introduction:

This release focuses on fixing bugs with npm installation and IP address validation.

Bugs

• IP address validation. For more information, please check out this PR #4 .
• The NPM bin field was changed to reflect the new name scs

v0.1.1

Full Changelog: v0.1.0...v0.1.1

Introduction:

This release renames this package heretofore known as share to scs, makes scs available on crates.io as well as some security updates.

Changes

• share is now scs all through. Although you still have to yarn install @onboarbase/secure-share, when actually using it, you run scs --help.
• Henceforth, scs will be used as the name of the package, binary and colloquial name.

Installation

• scs is now available on crates.io with cargo install scs. Make sure to read the installation instructions for additional information.

Security Updates

• scs now uses TLS 1.3 to encrypt data end to end. A step above that is using signed certificates from Let's Encrypt to validate the sender. A receiver can configure scs to only accept connections from certificates issues by the Authority just by adding connection: trusted to the configuration file

v0.0.17

Full Changelog: v0.0.16...v0.0.17

Introduction:

This release introduces new security features and implementations to make share the security standard.

Security Features:

• Upgraded protocol from TCP to TLS for secure and encrypted communication over the network.
• Added whitelists and blacklists to prevent/allow traffic from specified IPs.

Improvements:

• Refactored codebase into the network stack, the handlers which contain security implementations and the config stack.

Other Changes:

• Bumped up version.

How to enable security features.

To use whitelists or blacklists, you need to add the list of IPs to the config file, an example can be found here.

Notes

• If no whitelist IPs are specified, all connections are allowed
• If whitelist IPs are specified traffic is only allowed from that IP address
• Generic IPs like 127.0.0.1 or 192.0.0.0 won't work as they represent localhost, and the firewall access points respectively

v0.0.16

fixes

v0.0.15

new release

v0.0.14

scure-share

v0.0.13

secure-share