- Linux and Mac EAC support is probably too early to reliably use (something garry probably found out after pushing Mac/Linux EAC out). The Windows client has a minor fuckup in the registry keys being set.
- This timeline shows the history of the Rust game client updates, so you can track updates history at one place. Additional details of each update.
- How To Update Mac Computer
- How To Update Client For Rust Macros
- How To Update Client Cs Go
- How To Update Client For Rust Mac Requirements
- How To Update Client Update For Steam
- Client Update Required Rust
The current idea of RustBuster was to create an Anti-Cheat that is running on client side, with auto-update, obfuscated, and get rid of the server-sided laggy anti cheats. Also, RustBuster client will be a Plugin-Developement Center too, where plugin devs will be able to do client sided GUIs, and stuffs, etc.
A Rust based DNS client, server, and Resolver, built to be safe and secure from theground up.
This repo consists of multiple crates:
|Proto||Raw DNS library, exposes an unstable API and only for use by the other Trust-DNS libraries, not intended for end-user use.|
|Client|| Used for sending |
|Server|| Use to host DNS records, this also has a |
|Resolver||Utilizes the client library to perform DNS resolution. Can be used in place of the standard OS resolution facilities.|
|Rustls||Implementation of DNS over TLS protocol using the rustls and ring libraries.|
|NativeTls||Implementation of DNS over TLS protocol using the Host OS' provided default TLS libraries|
|OpenSsl||Implementation of DNS over TLS protocol using OpenSSL|
- Build a safe and secure DNS server and client with modern features.
- No panics, all code is guarded
- Use only safe Rust, and avoid all panics with proper Error handling
- Use only stable Rust
- Protect against DDOS attacks (to a degree)
- Support options for Global Load Balancing functions
- Make it dead simple to operate
Using the ClientFuture is safe. ClientFuture is a brand new rewrite of the oldClient. It has all the same features as the old Client, but is written with thewonderful futures-rs library. Please send feedback! It currently does not cacheresponses, if this is a feature you'd like earlier rather than later, post arequest. The validation of DNSSec is complete including NSEC. As of now NSEC3is broken, and I may never plan to support it. I have some alternative ideasfor private data in the zone. The old Client has been deprecated, so pleaseuse the ClientFuture. If this is an inconvenience, I may add a conveniencewrapper around ClientFuture that would match the old Client; if this is somethingyou would like to see, please file an issue.
Unique client side implementations
These are standards supported by the DNS protocol. The client implements themas high level interfaces, which is a bit more rare.
|create||atomic create of a record, with authenticated request|
|append||verify existence of a record and append to it|
|compare_and_swap||atomic (depends on server) compare and swap|
|delete_by_rdata||delete a specific record|
|delete_rrset||delete an entire record set|
|delete_all||delete all records sets with a given name|
|notify||notify server that it should reload a zone|
DNS over TLS on the Client
DNS over TLS is supported. This is accomplished through the use of
rust-native-tls. To use DNS over TLS with the
TlsClientConnection should be used. See the
TlsClientConnectionBuilder::add_ca() method. Similarly, to use the tokio
TlsClientStream should be used. ClientAuth, mTLS, is currently not supported, there are some issues still being worked on. TLS is supported for Server validation and connection privacy.
The server code is complete, the daemon supports IPv4 and IPv6, UDP and TCP.There currently is no way to limit TCP and AXFR operations, so it is still notrecommended to put into production as TCP can be used to DOS the service.Master file parsing is complete and supported. There is currently no forkingoption, and the server is not yet threaded (although it is implemented withasync IO, so threading may not be a huge benefit). There is still a lot of workto do before a server can be trusted with this externally. Running it behind afirewall on a private network would be safe.
Zone signing support is complete, to insert a key store a pem encoded rsa filein the same directory as the initial zone file with the
.key suffix. Note:this must be only readable by the current user. If one is not present one willbe created and written to the correct location. This also acts as the initialkey for dynamic update SIG(0) validation. To get the public key, the
DNSKEYrecord for the zone can be queried. This is needed to provide to otherupstream servers to create the
DS key. Dynamic DNS is also complete,if enabled, a journal file will be stored next to the zone file with the
jrnl suffix. Note: if the key is changed or updated, it is currently theoperators responsibility to remove the only public key from the zone, thisallows for the
DNSKEY to exist for some unspecified period of time duringkey rotation. Rotating the key currently is not available online and requiresa restart of the server process.
DNS over TLS on the Server
Support of TLS on the Server is managed through a pkcs12 der file. The documentation is captured in the example test config file, example.toml. A registered certificate to the server can be pinned to the Client with the
add_ca() method. Alternatively, as the client uses the rust-native-tls library, it should work with certificate signed by any standard CA.
Currently the root key is hardcoded into the system. This gives validation ofDNSKEY and DS records back to the root. NSEC is implemented, but not NSEC3.Because caching is not yet enabled, it has been noticed that some DNS serversappear to rate limit the connections, validating RRSIG records back to the rootcan require a significant number of additional queries for those records.
Zones will be automatically resigned on any record updates via dynamic DNS.
- RFC 1035: Base DNS spec (see the Resolver for caching)
- RFC 2308: Negative Caching of DNS Queries (see the Resolver)
- RFC 2782: Service location
- RFC 3596: IPv6
- RFC 6891: Extension Mechanisms for DNS
- RFC 6761: Special-Use Domain Names (resolver)
- RFC 6762: mDNS Multicast DNS (experimental feature:
- RFC 6763: DNS-SD Service Discovery (experimental feature:
- RFC ANAME: Address-specific DNS aliases (
- RFC 2136: Dynamic Update
Secure DNS operations
- RFC 3007: Secure Dynamic Update
- RFC 4034: DNSSEC Resource Records
- RFC 4035: Protocol Modifications for DNSSEC
- RFC 4509: SHA-256 in DNSSEC Delegation Signer
- RFC 5702: SHA-2 Algorithms with RSA in DNSKEY and RRSIG for DNSSEC
- RFC 6844: DNS Certification Authority Authorization (CAA) Resource Record
- RFC 6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
- RFC 6840: Clarifications and Implementation Notes for DNSSEC
- RFC 6844: DNS Certification Authority Authorization Resource Record
- RFC 6944: DNSKEY Algorithm Implementation Status
- RFC 6975: Signaling Cryptographic Algorithm Understanding
- RFC 7858: DNS over TLS (feature:
- RFC DoH: DNS over HTTPS, DoH (feature:
RFCs in progress or not yet implemented
How To Update Mac Computer
- RFC 2317: Classless IN-ADDR.ARPA delegation
- RFC 1995: Incremental Zone Transfer
- RFC 1996: Notify secondaries of update
- Update Leases: Dynamic DNS Update Leases
- Long-Lived Queries: Notify with bells
Secure DNS operations
- RFC 5155: DNSSEC Hashed Authenticated Denial of Existence
- DNSCrypt: Trusted DNS queries
- S/MIME: Domain Names For S/MIME
This assumes that you have Rust stable installed. Thesepresume that the trust-dns repos have already been synced to the local system:
- openssl development libraries (optional in client and resolver, min version 1.0.2)
Mac OS X: using homebrew
Debian-based (includes Ubuntu & Raspbian): using apt-get
How To Update Client For Rust Macros
These are good for running on local systems. They will create sockets forlocal tests, but will not attempt to access remote systems. Tests can alsobe run from the crate directory, i.e.
These will try to use some local system tools for compatibility testing,and also make some remote requests to verify compatibility with other DNSsystems. These can not currently be run on Travis for example.
Waiting on benchmarks to stabilize in mainline Rust.
- Production build, from the
Warning: Trust-DNS is still under development, running in production is notrecommended. The server is currently only single-threaded, it is non-blockingso this should allow it to work with most internal loads.
- Verify the version
- Get help
namedserver with test config
- Query the just launched server with
Using as a dependency and custom features
The Client has a few features which can be disabled for different reasons when embedding in other software.
dnssec-opensslIt is a default feature, so default-features will need to be set to false (this will disable all other default features in trust-dns). Until there are other crypto libraries supported, this will also disable DNSSec validation. The functions will still exist, but will always return errors on validation. The below example line will disable all default features and enable OpenSSL, remove
'openssl'to remove the dependency on OpenSSL.
dnssec-ringRing support can be used for RSA and ED25519 DNSSec validation.
native-tlsfor DNS-over-TLS implementation, only supported in client and resolver, not server.
opensslfor DNS-over-TLS implementation supported in server and client, resolver does not have default CA chains.
rustlsfor DNS-over-TLS implementation, only supported in client and resolver, not server. This is the best option where a pure Rust toolchain is desired.
mdnsEXPERIMENTALEnables the experimental mDNS features as well as DNS-SD.
Using custom features in dependencies:
Using custom features during build:
Why are you building another DNS server?
Because of all the security advisories out there for BIND.Using Rust semantics it should be possible to develop a high performance andsafe DNS Server that is more resilient to attacks.
For live discussions beyond this repository, please see this Discord.
How To Update Client Cs Go
Licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
How To Update Client For Rust Mac Requirements
at your option.
How To Update Client Update For Steam
Client Update Required Rust
Unless you explicitly state otherwise, any contribution intentionallysubmitted for inclusion in the work by you, as defined in the Apache-2.0license, shall be dual licensed as above, without any additional terms orconditions.