Menu

#6 Trace logs incorrectly resolve source and destination IP addresses

open
nobody
None
5
2016-05-05
2016-05-05
No

It was recently identified that the trace logs contain incorrect reverse DNS for the IP addresses involved in a proxied connection.

1 Attachments

Discussion

  • lord

    lord - 2016-05-05

    I have partially applied this patch.
    The first occurence of 'gethosbyaddr' was eliminated by earier patch:
    https://sourceforge.net/p/simpleproxy/patches/4/
    I am wondering if the remaining gethostbuaddr application also poses a performance issue as reported in #4?

     
  • Andrew Pollock

    Andrew Pollock - 2016-05-05

    IMO it's worthwhile being consistent, so use getnameinfo everywhere

     
  • lord

    lord - 2016-05-05

    I am not familiar with getnameinfo and I am not sure how to test if switching to it also address the problem in this ticket. I will appreciate if somebody would try it and send me a patch :)

     
  • lord

    lord - 2016-05-05

    Project moved to https://github.com/vzaliva/simpleproxy
    Please submit new issues and patches there. This page is no longer updated.

     

Log in to post a comment.