Releases: bitbeans/SimpleDnsCrypt
Releases · bitbeans/SimpleDnsCrypt
0.5.8
New: start in system tray support
New: support to disable tray mode
New: domain block list clear button
New Languages:
- Filipino
Special thanks to @Mongogamer!
0.5.7
0.5.6
0.5.5
- Fix: Cannot Change Fallback Resolver #289
- Fix: Create log directory, if not available
- Fix: Prevent multiple instances of SimpleDnsCrypt
- New: Option to set
listen_addresses
#301 - Updated: dependencies
- Updated: to dnscrypt-proxy 2.0.14
New Languages:
- Romanian
- Korean
- Japanese
- Malay
- Czech
- Finish
- Thai
Thanks again to all translators! (26 languages, thats pretty awesome!)
Note: New Code Signing Certificate
CN: Christian Hermann
Valid until: 02.06.2019
Fingerprint (256): 47:54:2F:0F:5C:25:CA:63:C5:05:3A:62:5A:7D:A7:0E:92:30:29:B9:72:2F:43:EA:7D:3E:6F:EB:21:22:7E:CB
0.5.4
0.5.3
- Fix: Domain Block Log issue (#246)
- Fix: Domain Blacklist issue (#245)
- New languages: Turkish and Traditional Chinese
- Updated some translations
- Added dynamic width and height to some tabs.
Updated to dnscrypt-proxy 2.0.6
- Fixes a crash occasionally happening when using DoH servers, with stamps not containing any IP addresses, a DNSSEC-signed name, a non-working system DNS configuration, and a fallback server supporting DNSSEC (2.0.5).
- Automatic log files rotation was finally implemented (2.0.6).
- A bug with source names including CNAME records was fixed (2.0.6).
0.5.2
- Fix: Keep user settings after an update (#234)
- New: Act as global resolver (#240)
- Updated some translations
Updated to dnscrypt-proxy 2.0.4
- Fixes a regression with truncated packets (2.0.4)
- Load balancing: resolvers that respond promptly, but with bogus responses are now gradually removed from the preferred pool (2.0.3)
0.5.1
0.5.0
- dnscrypt-proxy has been updated to version 2.0.1
- Updated some language files
- it is now possible to add hosts directly from the block log to the whitelist
- it is now possible to add hosts directly from the query log to the blacklist
- simplednscrypt automatically restarts the service when the blacklist is regenerated (if the service has already been started)
- an error which could cause the application to crash in case of missing blacklist or whitelist file has been fixed