| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| nessus packet analysis of MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| kerberos_daemon |
 Posted: Mon Apr 19, 2004 7:12 am Post subject: nessus packet analysis of MQ |
 |
|
Newbie
Joined: 19 Apr 2004
Posts: 4
|
Im a Security Officer for the compnay I work for, our developers sometimes have to write code for an application that we sell that intercepts specific protocols/communications.
I need a nessus dmp file of several differant Websphere communications between a client and a MQ server, nothing fancy very light traffic and only a few hundered or less packets captured would be just fine.
I cant seem to fine any good white papers or docs on the actuall packet contruction and truely to be honets dont have the time to spend how to learn how to setup the whole thing on my test network just to dump a few packets.....
come on someobody hook me up =)
need it ASAP, date is 4/19/04
aim - kerveros_daemon
_________________
linux |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 19, 2004 7:15 am Post subject: Re: nessus packet analysis of MQ |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kerberos_daemon wrote: |
| I cant seem to fine any good white papers or docs on the actuall packet contruction |
That's probably because it's proprietary IBM information that is not publicly available.
Or at least, I'm pretty sure it's proprietary and not publicly available.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kerberos_daemon |
| Posted: Mon Apr 19, 2004 7:23 am Post subject: proprietary |
|
|
Newbie
Joined: 19 Apr 2004
Posts: 4
|
I know it is, but sometimes you get lucky
_________________
linux |
|
| Back to top |
|
|
| mqonnet |
| Posted: Mon Apr 19, 2004 7:35 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I may be posting something out of context here(or may be just appropriate). But isnt SSL achieving what nessus is trying to test by hacking/breaking into a network. Or to put it in other words, isnt SSL doing the needed authentication of packets sent by a sender at the receiving end. Then whats the need to reinvent the wheel using nessus when this feature is already there in the product.
As i mentioned earlier, i may be posting something out of context, as i dont know much about nessus(just skimmed through their website once just now .. :) ... )
Cheers
Kumar |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
