10:13 a.m.
Yes You are right.
And it is not to convert but we will be giving options if UDP requests are
coming then it has to be serve UDP and if TCP communication is happening we
need to implement the same over TLS certificate exchange implementation.
Is there anything you can suggest?
Javed Akhtar
Technical Lead
jaakhtar(a)cisco.com
Tel:
Cisco Systems, Inc.
India
cisco.com
Think before you print.
This email may contain confidential and privileged material for the sole use
of the intended recipient. Any review, use, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or
authorized to receive for the recipient), please contact the sender by reply
email and delete all copies of this message.
Please click here for Company Registration Information.
-----Original Message-----
From: Linus Nordberg [mailto:linus@nordu.net]
Sent: 16 December 2016 13:21
To: Javed <jaakhtar(a)cisco.com>
Cc: radsecproxy(a)lists.nordu.net
Subject: Re: [radsecproxy] RADIUS TLS implementation
Javed <jaakhtar(a)cisco.com> wrote
Fri, 16 Dec 2016 10:07:32 +0530:
Hello All,
Hello Javed.
We need the same authentication to happen over a
secure network where
we need to implement RADIUS TCP/TLS .I need to change my client
configuration and required code changes has to be done to adapt with
RADIUS server so wher I can be getting client side code to implement
RADIUS over
TLS.
Do I understand you correctly if I think that you have a RADIUS-over-UDP
client that you would like to turn into a RADIUS-over-TLS (aka RadSec)
client?
What should I start with?
Is RadSecProxy will be helpful for me at any point of view?
For source code to use in your program? It might. But libradsec [0] is
probably even more useful to you.
[0] https://git.nordu.net/?p=libradsec.git;a=summary
How and where should I implement RADIUS/TLS and client
configuration
and codes.
I'm afraid I don't understand the question fully. Can you elaborate a bit?