aboutsummaryrefslogtreecommitdiff
path: root/net/queso
diff options
context:
space:
mode:
authorJimmy Olgeni <olgeni@FreeBSD.org>2015-09-20 20:54:08 +0000
committerJimmy Olgeni <olgeni@FreeBSD.org>2015-09-20 20:54:08 +0000
commit41a7072cfbf055dc6c89e9ca7fa617b720337e24 (patch)
treeb63994e684ffd6fb805f9017ff2e8c81d549ca91 /net/queso
parent20b96b3ed5bab9778e6a3bfb8c877e145c9b2404 (diff)
downloadports-41a7072cfbf055dc6c89e9ca7fa617b720337e24.tar.gz
ports-41a7072cfbf055dc6c89e9ca7fa617b720337e24.zip
Notes
Diffstat (limited to 'net/queso')
-rw-r--r--net/queso/pkg-descr2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/queso/pkg-descr b/net/queso/pkg-descr
index 79cd4ba9002a..a5df04d31b6a 100644
--- a/net/queso/pkg-descr
+++ b/net/queso/pkg-descr
@@ -1,6 +1,6 @@
former QueSO home page <URL:http://www.apostols.org/projectz/queso/>:
-How we can determine the remote OS using simple tcp packets? Well,
+How we can determine the remote OS using simple TCP packets? Well,
it's easy, they're packets that don't make any sense, so the RFCs
don't clearly state what to answer in these kind of situations.
Facing this ambiguous, each TCP/IP stack takes a different approach