full-disclosure - RE: RES: Instant Messenger

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-next>] [day] [month] [year] [list]

Message-ID: <496A14A88484E8418B0882BDA23E0B6C0FFE2038@hqcomexcp01>
From: MurtlandJ at Grangeinsurance.com (Murtland, Jerry)
Subject: RE: RES: Instant Messenger

Snake,

That's a very good step-by-step illustration of how to proxy through secure
remote to external systems.  I'm sure it would make other security staff
feel as uncomfortable as it does me, but I was aware of this.  However,
there might be something else that we can discuss that would be of good use
to me as well as others looking to work on ways to detect and block this
sort of activity.  Obviously, you can't sniff or detect secure protocol, and
I've heard of some that say they can, but they that's via SSL and the
certificates are pointed to from the IDS for filtering signatures.  Not
effective.

I'm looking for a way to be able to block this all together.  What
immediately comes to mind is to only allow specific IP's to SSh outbound
through your firewall and deny all else.  I guess my question is, "Are there
other methods to circumvent this block after creating this rule set?"

Thanks for the document, I put it to good use!  ;)

Jerry Murtland

-----Original Message-----
From: RSnake [mailto:rsnake@...cking.com]
Sent: Sunday, September 05, 2004 3:50 PM
To: Alexandre Cezar
Cc: Ido Rosen; Murtland, Jerry; pen-test@...urityfocus.com;
webappsec@...urityfocus.com; full-disclosure@...ts.netsys.com
Subject: Re: RES: Instant Messenger

	On the flip side I wrote a short paper on bypassing content filters
by
sending Trillian Pro messages over SSH.  It's a tad off topic, but still
relevant: http://www.shocking.com/~rsnake/trillianremote.html

On Fri, 3 Sep 2004, Alexandre Cezar wrote:

| Date: Fri, 3 Sep 2004 11:42:31 -0300
| From: Alexandre Cezar <acezar@...ncs.com.br>
| To: Ido Rosen <ido@...uchicago.edu>,
|      "Murtland, Jerry" <MurtlandJ@...ngeinsurance.com>
| Cc: pen-test@...urityfocus.com, webappsec@...urityfocus.com,
|      full-disclosure@...ts.netsys.com
| Subject: RES: Instant Messenger
|
| Take a look at http://www.akonix.com for securing IM communication and
| I recommend this paper
| www.giac.org/practical/GSEC/Frank_Reiss_GSEC.pdf
|
|
| Regards
| -----Mensagem original-----
| De: Ido Rosen [mailto:ido@...uchicago.edu]
| Enviada em: quinta-feira, 2 de setembro de 2004 23:17
| Para: Murtland, Jerry
| Cc: pen-test@...urityfocus.com; webappsec@...urityfocus.com;
| full-disclosure@...ts.netsys.com
| Assunto: Re: Instant Messenger
|
| Jabber.
|
| On Thu, 2 Sep 2004 10:00:18 -0400
| "Murtland, Jerry" <MurtlandJ@...ngeinsurance.com> wrote:
|
| > I am looking for white papers on enterprise Instant Messenger security
| > concerns.  It doesn't have to be, but anything on MSN IM would be
| > helpful too.  Does anyone have any good resources to share?
| >
| > Jerry J. Murtland
| >
| >
| >
|
|
| --
| +-------------------------------------------------+
| |  Email : ido@...e.org / ido@...uchicago.edu     |
| | Jabber : phaedo@...ber.org                      |
| |    PGP : http://www.dork.com/ido                |
| +-------------------------------------------------+
|

-R

The information in this email is confidential and may be legally
privileged.  It is intended solely for the addressee.  Access to
this email by anyone else is unauthorized.  If you are not the
intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it is
expressly prohibited and may be unlawful.