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.

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

latest commit breaks my generated dnsmasq.conf #440

Closed
jac18281828 opened this Issue Nov 18, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@jac18281828

jac18281828 commented Nov 18, 2017

The latest commit:
commit 57451df (HEAD -> master, origin/master, origin/HEAD)
Author: Steven Black steveb@stevenblack.com
Date: Thu Nov 16 20:58:38 2017 -0500

New data from yoyo.org, someonewhocares.org, and Badd-Boyz.

Breaks my generated dnsmasq. All hosts fail to resolve after it is loaded.

The script I'm using to generate is here:

https://gist.github.com/jac18281828/31deef842ec0aa7a6f04bdc249da392f

I'm also attaching a diff between the good file and the bad one, but I can't tell what the problem is in my first pass at looking at it.

adlist.generated.diff.txt

@welcome

This comment has been minimized.

Show comment
Hide comment
@welcome

welcome bot Nov 18, 2017

Hello! Thank you for opening your first issue in this repo. It’s people like you who make these host files better!

welcome bot commented Nov 18, 2017

Hello! Thank you for opening your first issue in this repo. It’s people like you who make these host files better!

@StevenBlack

This comment has been minimized.

Show comment
Hide comment
@StevenBlack

StevenBlack Nov 18, 2017

Owner

Hi @jac18281828 to confirm, are you using Python 3.5? This could be related to the build error we see under Python 3.5, but seems fine in other versions. See https://travis-ci.org/StevenBlack/hosts.

Let me know.

Owner

StevenBlack commented Nov 18, 2017

Hi @jac18281828 to confirm, are you using Python 3.5? This could be related to the build error we see under Python 3.5, but seems fine in other versions. See https://travis-ci.org/StevenBlack/hosts.

Let me know.

@StevenBlack StevenBlack self-assigned this Nov 18, 2017

@StevenBlack StevenBlack added the bug label Nov 18, 2017

@mateoag

This comment has been minimized.

Show comment
Hide comment
@mateoag

mateoag Nov 19, 2017

Hi @StevenBlack,

Thanks for providing us with these hosts files, It has given me peace of mind for quite some time.

I also encountered a problem with my dnsmasq lately upon the release of commit 57451df
for my case I was able to work around it for now by removing these 2 lines from the hosts file.

0.0.0.0 ɢoogle.com
0.0.0.0 secret.ɢoogle.com

I'm using the hosts file with this script

I think the reason my dnsmasq got broken was the failure of either the script or my router to properly read the ɢ character from the latest hosts file.

Could there be another way to block these two domains without using the ɢ character?

Edit:
I was able to search about punycodes and converted the two lines using this converter

0.0.0.0 xn--oogle-wmc.com
0.0.0.0 secret.xn--oogle-wmc.com

Can we maybe use this alternative?

mateoag commented Nov 19, 2017

Hi @StevenBlack,

Thanks for providing us with these hosts files, It has given me peace of mind for quite some time.

I also encountered a problem with my dnsmasq lately upon the release of commit 57451df
for my case I was able to work around it for now by removing these 2 lines from the hosts file.

0.0.0.0 ɢoogle.com
0.0.0.0 secret.ɢoogle.com

I'm using the hosts file with this script

I think the reason my dnsmasq got broken was the failure of either the script or my router to properly read the ɢ character from the latest hosts file.

Could there be another way to block these two domains without using the ɢ character?

Edit:
I was able to search about punycodes and converted the two lines using this converter

0.0.0.0 xn--oogle-wmc.com
0.0.0.0 secret.xn--oogle-wmc.com

Can we maybe use this alternative?

@jac18281828

This comment has been minimized.

Show comment
Hide comment
@jac18281828

jac18281828 Nov 19, 2017

@StevenBlack I am using a shell script not python. I quoted the gist for this script in my post.

The solution suggested by @mateoag works for me as well the "G" in those domains converts to extra ".." (dots) in my dnsmasq.conf which appears to confuse/break dnsmasq.

Removing those lines fixes the problem.

Thanks for the help both of you!

jac18281828 commented Nov 19, 2017

@StevenBlack I am using a shell script not python. I quoted the gist for this script in my post.

The solution suggested by @mateoag works for me as well the "G" in those domains converts to extra ".." (dots) in my dnsmasq.conf which appears to confuse/break dnsmasq.

Removing those lines fixes the problem.

Thanks for the help both of you!

@jac18281828

This comment has been minimized.

Show comment
Hide comment
@jac18281828

jac18281828 Feb 3, 2018

The latest hosts file also contains the following:

0.0.0.0 streamillimité.com

This problem is due to dnsmasq not handling unicode characters properly.

I am able to resolve this by filtering with a simple python script. I'm closing because I have a workaround.

import sys
for buffer in sys.stdin.read():
  for ch in buffer:
    if (ord(ch) < 128):
      sys.stdout.write(ch)

jac18281828 commented Feb 3, 2018

The latest hosts file also contains the following:

0.0.0.0 streamillimité.com

This problem is due to dnsmasq not handling unicode characters properly.

I am able to resolve this by filtering with a simple python script. I'm closing because I have a workaround.

import sys
for buffer in sys.stdin.read():
  for ch in buffer:
    if (ord(ch) < 128):
      sys.stdout.write(ch)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment