full-disclosure - Interesting idea for a covert channel or I just didn'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>] [day] [month] [year] [list]

Message-ID: <20051007074619.AC74B8257@codi.codixx>
Date: Fri Oct  7 08:46:26 2005
From: Polarizer at Codixx.Com (Polarizer)
Subject: Interesting idea for a covert channel or I
	just	didn't research enough?

> The scenario is the following. The victim is a host with a host-level 
> firewall which is blocking *all* incoming traffic. Somehow the attacker 
> still needs to communicate with a backdoor planted in this host. 

Sounds to me like another variation of port knocking[1].

[1] http://www.linuxjournal.com/article/6811

the polarizer
http://www.codixx.de/polarizer.html