![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Yes, of course, I had USM on the brain. For TSM, the notification receiver doesn't really have a whole lot to do with the securityName, does it? Thanks much. Ray -----Original Message----- From: Pasi.Eronen at nokia.com [mailto:Pasi.Eronen at nokia.com] Sent: Friday, May 09, 2008 7:11 AM To: Purvis, Ray; wjhns1 at hardakers.net Cc: isms at ietf.org Subject: RE: [Isms] ISMS/SSH and notifications Ray Purvis wrote: > [Ray Purvis] Isn't the securityName, in the current RFCs, and thus > for the use of USM, used with the snmpEngineID to locate the > authentication and privacy key to authenticate/decrypt the > notification? Yes; with SSHTM, at the point when the securityName actually could be visible, the packet has already been authenticated and decrypted. Best regards, Pasi
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Isms mailing list Isms at ietf.org https://www.ietf.org/mailman/listinfo/isms