Re: [OPSAWG] Secdir last call review of draft-ietf-opsawg-tacacs-13

2019-04-22 Thread Randy Bush
>> Agreed to replace the section with a simple statement that >> obfuscation provides no integrity or replay protection. I'm assuming >> this refers just to 10.1 and not the whole of 10. >> > [Joe] I think you could probably replace a large portion of 10.2, 3 and 4 > as well. hyperbole is not

Re: [OPSAWG] Secdir last call review of draft-ietf-opsawg-tacacs-13

2019-04-22 Thread Joseph Salowey
On Mon, Apr 22, 2019 at 11:24 AM Andrej Ota wrote: > Hi Joseph, > > Thank you for taking time to review the document. Answers are in-line. > > > On 22 Apr 2019, at 04:49, Joseph Salowey via Datatracker < > nore...@ietf.org> wrote: > > > > Reviewer: Joseph Salowey > > Review result: Serious

Re: [OPSAWG] Secdir last call review of draft-ietf-opsawg-tacacs-13

2019-04-22 Thread Andrej Ota
Hi Joseph, Thank you for taking time to review the document. Answers are in-line. > On 22 Apr 2019, at 04:49, Joseph Salowey via Datatracker > wrote: > > Reviewer: Joseph Salowey > Review result: Serious Issues > > As the draft mentions the MD5 based stream cipher used by TACACS+ is >