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.

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

garbage is appended to /etc/resolv.conf #103

Closed
gilligan opened this issue Feb 26, 2017 · 7 comments
Closed

garbage is appended to /etc/resolv.conf #103

gilligan opened this issue Feb 26, 2017 · 7 comments

Comments

@gilligan
Copy link

I just wanted to update the openfortivpn package for NixOS to the latest version. Everything seemed to be working fine and I can in fact connect to our vpn. The problem is that after disconnecting VPN some garbage is being appended to /etc/resolv.conf:

^S^]AddTrust Exte<91>

As you can see in my package update PR for openfortivpn the best guess from some other contributor is that it might be some pointer corruption.

How can I provide useful information to figure out what is going on ?

@gilligan
Copy link
Author

I ran this through valgrind - here is the output: https://gist.github.com/gilligan/f973eac77bbb87206afbc32e3eed174c

==15669== LEAK SUMMARY:
==15669==    definitely lost: 824 bytes in 1 blocks
==15669==    indirectly lost: 71,519 bytes in 653 blocks
==15669==      possibly lost: 47 bytes in 2 blocks
==15669==    still reachable: 88,011 bytes in 2,876 blocks
==15669==         suppressed: 0 bytes in 0 blocks
==15669== Reachable blocks (those to which a pointer was found) are not shown.
==15669== To see them, rerun with: --leak-check=full --show-leak-kinds=all

@gilligan
Copy link
Author

As noted in the linked PR I notcied that there is a read happening somewhere towards the end that reads some data containing AddTrust so I'm guessing there is some memory corruption going on when the nameserver entries are removed from /etc/resolv.conf in src/ipv4.c - Can't really point at anything in specific though

@gilligan
Copy link
Author

gilligan commented Mar 1, 2017

@adrienverge ping ;-)

@DimitriPapadopoulos
Copy link
Collaborator

It's a long shot, but perhaps #117 could help...

@adrienverge
Copy link
Owner

Sorry about the delay. I hope #117 will fix the problem!

@DimitriPapadopoulos
Copy link
Collaborator

@gilligan Does it work any better with openfortivpn 1.3.1 (which includes patch #117)?

@DimitriPapadopoulos
Copy link
Collaborator

I'll close this issue as #117 should have fixed the problem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants