Http Security

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jounin
    Member
    • Jun 2003
    • 31

    #16
    I think you are cornfused about port 80 and the browser. I do believe the browser uses a port somewhere between 1123 up to the mid/high 1100's (whatever is available) and for sure the server is using 80 to listen on. Please check me if I'm wrong (like I had to ask). E.g. browser=1143 --> server=80
    http://www.google.com/search?hl=en&lr=&ie=UTF-8&q=replace_with_any_question

    Comment

    • encrypt31945
      Banned
      • Apr 2003
      • 266

      #17
      The easiest way is get sygate and just tell it to block the port.

      Comment

      • yankee
        Transmutation
        • May 2003
        • 113

        #18
        Originally posted by jounin
        I think you are cornfused about port 80 and the browser. I do believe the browser uses a port somewhere between 1123 up to the mid/high 1100's (whatever is available) and for sure the server is using 80 to listen on. Please check me if I'm wrong (like I had to ask). E.g. browser=1143 --> server=80
        I'm pretty sure anything above 1023 up to 65535 is fair game for a source TCP port. See the well-known and registered ports at: http://www.iana.org/assignments/port-numbers

        Comment

        • Chris
          Great Satan of the East
          • Oct 2001
          • 2866

          #19
          Ok, I think we have beaten this horse long enough.

          Summary--
          Stay away from Steve Gibson
          Clients don't open server ports.
          P2P apps don't open http server port.
          Clients use high ports.

          Nuff said...thread closed.
          perl -e 'print pack(c5, (41*2), sqrt(7056), (unpack(c,H)-2), oct(115), 10)'

          Comment

          Working...