that, or
isn't the plain-text secret such an issue after all?
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Plain-text-shared-secrets-problematic-tp5603361p5612293.html
Sent from the FreeRadius - User mailing list archive at Nabble.com.
-
List info/subscribe/unsubscribe? See http
Heilz wrote:
Thanks for the quick answer.
Yes, the RADIUS secret was what I meant.
Since we want to use a freeRADIUS proxy in our DMZ and because a secure
connection from our customers to our application is important, that seems to
be a problem. Are there maybe some best practices for a
Hello,
(c) use IPSec for connectivity
or if you don't like the complexity that comes with ipsec, use OpenVPN
or any other VPN software.
Cheers,
Thomas
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
and fould several articles
about RADIUS' vulnerabilities, but noone seems to be concerned about this
subject.
I hope you might be able to clear things up for me.
Regards
Mathias
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Plain-text-shared-secrets-problematic
On 29/03/12 11:46, Heilz wrote:
Hi,
I'm fairly new to the topic but I got the assignment to find out if the fact
that the shared secrets for user logins are in plain-text could be a problem
security-wise.
Do you really mean shared secrets? This is a term normally applied to
the RADIUS secret
5 matches
Mail list logo