Anything more specific regarding what the potential issues are? Besides "adding an interface adds an attack surface"?
Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. Original Message From: Michael MacFaden Sent: Monday, June 22, 2015 15:09 To: Kathleen Moriarty; The IESG; Randy Presuhn Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [OPSAWG] Kathleen Moriarty's No Objection on draft-ietf-opsawg-vmm-mib-03: (with COMMENT) Agree there should be some warning here. But if this text is intended for those who implement it (like me) then I'd prefer to make it clear as mud what the issue is: Any implementation of this MIB module in an agent where the Virtual Machines being monitored have access to this very agent or this MIB module creates an attack vector on the system or on any other VM hosted by this system. Mike MacFaden _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
