...Karel Galuska wrote:
As a casual reader of this thread, I'm wondering if someone could
enlighten me as to why you'd want a custom application to take the
"standard" destination port an app (web browser) has requested and remap
it to some random high port which the destination server has no hope of
understanding, therefore requiring said port to be re-translated back to
its original by a proxy or firewall anyhow? It seems a completely
pointless and futile exercise. I hope it's not some kind of attempt at
security through obscurity, but for the life of me I couldn't think of
some other reason why you'd want to do this.
Thanks for any clarity someone might send my way,
Mark
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| David Newall | Re: Slow DOWN, please!!! |
| Andrew Morton | Re: Linux 2.6.21-rc4 |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Dale Farnsworth | Re: [PATCH 01/39] mv643xx_eth: reverse topological sort of functions |
