Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Invalid rule: [[fe80:53:*]] - wildcards can only be used as a suffix #1261

Closed
kimw opened this issue Apr 1, 2020 · 2 comments · Fixed by kimw/dnscrypt-proxy#1 or #1264
Closed

Invalid rule: [[fe80:53:*]] - wildcards can only be used as a suffix #1261

kimw opened this issue Apr 1, 2020 · 2 comments · Fixed by kimw/dnscrypt-proxy#1 or #1264

Comments

@kimw
Copy link
Contributor

kimw commented Apr 1, 2020

Who is the bug affecting?

dnscrypt-proxy 2.0.42

What is affected by this bug?

Error message shows up at the time dnscrypt-proxy start up,

[ERROR] Invalid rule: [[fe80:53:*]] - wildcards can only be used as a suffix at line 12

With ip-blacklist.txt config file has configured as follow, (copied from example-ip-blacklist.txt)

163.5.1.4
94.46.118.*
[fe80:53:*]        # IPv6 prefix example

When does this occur?

The dnscrypt-proxy start up.

How do we replicate the issue?

  1. Enable ip-blacklist feature
  2. Start up dnscrypt-proxy
@jedisct1
Copy link
Member

jedisct1 commented Apr 1, 2020

Can you try without the brackets ([ ])?

@kimw
Copy link
Contributor Author

kimw commented Apr 2, 2020

@jedisct1 Yes, it works :) I'll change the example-ip-blacklist.txt & PR later. Thank you.

kimw added a commit to kimw/dnscrypt-proxy that referenced this issue Apr 2, 2020
@kimw
Update example-ip-blacklist.txt
301a209 
fix DNSCrypt#1261. remove `[` & `]`.
@kimw kimw mentioned this issue Apr 2, 2020
Merged
@kimw kimw mentioned this issue Apr 2, 2020
Merged
jedisct1 pushed a commit that referenced this issue Apr 2, 2020
@kimw
Update example-ip-blacklist.txt (#1264)
4ce2847 
fix #1261. remove `[` & `]`.
@DNSCrypt DNSCrypt locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@jedisct1 @kimw