full-disclosure - Interesting idea for a covert channel or I justdidn't research enough?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1724892033.20051008152751@Sniff-em.com>
Date: Sat Oct  8 14:27:59 2005
From: Thierry at sniff-em.com (Thierry Zoller)
Subject: Interesting idea for a covert channel or I
	justdidn't research enough?

Dear Aditya Deshmukh,

AD> Aren't these all different versions of portknocking ? All of 
AD> them work untill someone outside can figure out the pattern of 
AD> events - at most I would call this security by obscurity -
Leveraged to real portknocking, i.e "encrypted payloads" (time based)
in different SYN, FYN, etc packets to different ports, you can't
easily get the pattern. Thus it leverages the "protection" over a
level that can be seen as security though obscurity. That said
you competely ignore that the Port 22 if open is not a security hole
itself. By hiding it you protect yourself from "possible" threads.

AD> Trivial to detect but good enough for some low security
AD> requirements
Proof it.

-- 
Thierry Zoller
mailto:Thierry@...ff-em.com