full-disclosure - Autosys Information and risks

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]

Date: Wed Dec 14 15:00:17 2005
From: jessevalentin at yahoo.com (spclfx)
Subject: Autosys Information and risks

Hello,

  I am looking for some information on Autosys and some of the risks associated with allowing this to run in an environment.

  Is it necessary to allow this traffic to run bi-directionally even with a stateful firewall? I am unsure if monitored machines ever need to initiate separate connections back to the master autosys server.

  Does anyone know if Cisco PIX firewalls can maintain state information for these connections? I know PIX fw's dont maintain state for certain types of protocols, was wondering if Autosys traffic was included.

  Does anyone know of a location where I can get some technical whitepapers on this service and how it functions from a lower layer perspective? 

  Thanks,

  JV

-------------------------------------------------------------
This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing disclosing or using any information contained herein.  Please inform the sender of the erroneous delivery by return e-mail. Thank you for your cooperation.
-------------------------------------------------------------

---------------------------------
Yahoo! Shopping
 Find Great Deals on Holiday Gifts at Yahoo! Shopping 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20051214/80925dea/attachment.html