| Re: Issue 152: Need crypto protocol agility | <– Date –> <– Thread –> |
|
From: Nathan J. Williams (nathan.williams |
|
| Date: Wed, 30 Jul 2008 14:17:26 -0700 (PDT) | |
"Pat Calhoun (pacalhou)" <pcalhoun [at] cisco.com> writes:
> 12.1.5. Use of MD5
>
> The Image Information Section 4.6.29) message element makes use of
> MD5 to compute the hash field. It is important to note that in order
> to preserve interoperability with existing CAPWAP implementations, it
> was decided to not provide protocol agility. That said, it is also
> important to note that the use of MD5 in this context is to create a
^^^
not
> cryptographically secure hash, but instead to provide a basic
> checksum value. Therefore, the use of MD5 is not considered a
> security vulnerability.
> </text>
Right?
- Nathan
- Re: Issue 152: Need crypto protocol agility, (continued)
-
Re: Issue 152: Need crypto protocol agility Pat Calhoun (pacalhou), July 29 2008
- Re: Issue 152: Need crypto protocol agility Charles Clancy, July 29 2008
- Re: Issue 152: Need crypto protocol agility Pasi.Eronen, July 30 2008
- Re: Issue 152: Need crypto protocol agility Pat Calhoun (pacalhou), July 30 2008
- Re: Issue 152: Need crypto protocol agility Nathan J. Williams, July 30 2008
- Re: Issue 152: Need crypto protocol agility Pat Calhoun (pacalhou), July 30 2008
- Re: Issue 152: Need crypto protocol agility Pasi.Eronen, July 31 2008
- Re: Issue 152: Need crypto protocol agility Pat Calhoun (pacalhou), July 31 2008
-
Re: Issue 152: Need crypto protocol agility Pat Calhoun (pacalhou), July 29 2008
- Re: Issue 152: Need crypto protocol agility David B. Nelson, July 30 2008
Results generated by Tiger Technologies using MHonArc.