-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If the NMAP scan can determine that it's an HP Printer can that be correlated with the actual plugin that's effecting the printer and be marked as dangerous? At least until we can go to HP and request a patch..
Thoughts? Chuck Fullerton CISSP, CSS1, CCNP, CCNA, CCDA, CNA, A+ Network Engineer Ficomp, Inc. 3015 Advance Lane Colmar, PA 18915 Office 215-997-3879 Cell 610-780-7248 Pager 1-800-759-8352 PIN 1030063 TextPaging [EMAIL PROTECTED] E-mail [EMAIL PROTECTED] FICOMP, Inc. - Confidential and Proprietary - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, January 10, 2003 8:03 AM To: Baumgartner Christoph Cc: [EMAIL PROTECTED]; Chuck Fullerton Subject: RE: Nessus vs. HP Laser Printers. Quoting Baumgartner Christoph : > We made the same experience. The only solution is a reset of the HP > laser printers after they hook (it seems that HP ink-jets are not > affected). I would test the HP laser printers during working hours > because the users/super users can reset/restart the printers if > they are informed before. > > I would appreciate if the author of the plugin could fix the > problem. I'd think it would be better if HP could fix the problem. If it's the syn scan & not a plugin, it can't be made a dangerous/DoS test to be disabled via the GUI. - -- http://www.cirt.net/ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use iQA/AwUBPh7Jw7OJO5KNoAL1EQIc/gCgqy40PtJpYdHhv4rartqgemR2KIoAn3Tf e51ReZt8LhTm2VClIcYJCX2Q =myvm -----END PGP SIGNATURE-----
PGPexch.htm.asc
Description: PGPexch.htm.asc
