TinyRadius | reliable Java Radius library capable ofsending

by ctran Java Version: 1.1.3 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | TinyRadius Summary

TinyRadius is a Java library. TinyRadius has no vulnerabilities, it has build file available and it has low support. However TinyRadius has 25 bugs and it has a Non-SPDX License. You can download it from GitHub, Maven.

TinyRadius is a simple, small and fast Java Radius library capable of sending and receiving Radius packets of all types. It is released under the terms of the LGPL. For documentation, please have a look at doc/tinyradius.html and doc/apidoc. Every method has got JavaDoc comments, and every package has got a package.html document detailing the package usage. Please do not hesitate to contact me if you have got questions or suggestions. Matthias Wuttke post@matthias-wuttke.de

Support

Quality

Security

License

Reuse

Support

TinyRadius has a low active ecosystem.

It has 114 star(s) with 102 fork(s). There are 18 watchers for this library.

It had no major release in the last 12 months.

TinyRadius has no issues reported. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of TinyRadius is 1.1.3

Quality

TinyRadius has 25 bugs (1 blocker, 0 critical, 20 major, 4 minor) and 192 code smells.

Security

TinyRadius has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

TinyRadius code analysis shows 0 unresolved vulnerabilities.

There are 7 security hotspots that need review.

License

TinyRadius has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

TinyRadius releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

TinyRadius saves you 1298 person hours of effort in developing the same functionality from scratch.

It has 2913 lines of code, 264 functions and 38 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed TinyRadius and discovered the below as its top functions. This is intended to give you an instant insight into TinyRadius implemented functionality, and help decide if they suit your requirements.

Adds the user - password attribute
Encodes a user password into a byte array
Encodes a plain - text password using the given CHAP challenge
Returns a string representation of this packet
Returns the type name of this packet
Returns a string representation of this attribute
Decodes the user - password attributes
Returns a resource attribute of the specified type
Decodes a PAP password
Start the RadiusProxy listener
Reads a Vendor - specific attribute
Sets the attributes for this packet
Set the IP address as a long
Returns the attribute value as a string
Sets the radius attribute
Get the vendor id
Checks the received request authenticator
Returns the IP address attribute value
Writes this attribute as a byte array
Returns a string representation of this radius attribute
Sets the value of the IPv6 address
Returns the IP address value
Adds an AttributeType to the cache
Set the IP address attribute value
Method updateRequestAuthenticator
Handle a proxy packet

Get all kandi verified functions for this library.

TinyRadius Key Features

No Key Features are available at this moment for TinyRadius.

TinyRadius Examples and Code Snippets

No Code Snippets are available at this moment for TinyRadius.

Community Discussions

Trending Discussions on TinyRadius

RADIUS Proxy implementation Message-Authenticator error

Stop jmeter.log logging out third party logs

Radius Protocol - How to correctly set the status in the second request?

QUESTION

RADIUS Proxy implementation Message-Authenticator error

Asked 2019-Oct-05 at 18:34

I am implementing a radius proxy with a help of TinyRadius lib. PAP & CHAP proxying without any problems but EAP messages not. So, i am recalculate Request Authenticator for radius packet after adding a proxy attribute, then i recalculate Message-Authenticator according to RFC3579.

And there is two question:

According to RFC3579: Message-Authenticator = HMAC-MD5 (Type, Identifier, Length, Request Authenticator, Attributes)

1) Length=? Is it a length of radius packet or EAP-message?

2) Request Authenticator - this is authenticator for radius packet, am i right? So, if i add it to the Message-Authenticator attribute into the radius packet - radius packet will be changed and i must to recalculate Request Authenticator but if i recalculate Request Authenticator - Message-Authenticator will be invalid because it depends on Request Authenticator.

Shared secrets for clients and endpoint radius server is the same (checked many times).

All i need - is to teach proxy to proxying EAP messages, but always get:

...

ANSWER

Answered 2019-Oct-05 at 18:34

1) Length is the length of the RADIUS packet which contains one or more EAP-Message attributes if you're performing EAP.

2) No - The request authenticator is a random 16 bit challenge in the RADIUS packet header that's used for duplicate detection and as part of a hashing scheme for attributes like CHAP. It should only change if you're generating a new packet, not when you're retransmitting an existing one.

Message-Authenticator is an attribute in the Access-Request itself. The Message-Authenticator contains a HMAC of the RADIUS packet keyed off the shared secret.

Causes of the Message-Authenticator being incorrect are:

Shared secret mismatch.
Bad implementation of the Message-Authenticator HMAC.
Packet being modified in flight between RADIUS client and server.

And then FreeRADIUS specific issues:

Wrong client entry being used due to incorrect IP scoping.
Shared secret being incorrect due to bad home server configuration.

Note: If you're using FreeRADIUS then you shouldn't generate the Message-Authenticator yourself. You just need to set Message-Authenticator = 0x00 in the upstream request and FreeRADIUS will fill in the value automatically.

If you want to generate you own Message-Authenticator values, that's described by RFC 2869 section #5.14.

For Access-Requests:

Source https://stackoverflow.com/questions/58236637

QUESTION

Stop jmeter.log logging out third party logs

Asked 2019-Apr-02 at 08:07

I have a JSR223 sampler that uses Tiny Radius but when I run the script, jmeter.log fills up with info messages from org.tinyradius.util.RadiusClient and packet information.

Is there something I can add to my jmeter.properties to stop this, or at least drop the logging level to error?

...

ANSWER

Answered 2019-Apr-02 at 08:07

PRE v3.2

in bin/jmeter.properties:

Source https://stackoverflow.com/questions/55195514

QUESTION

Radius Protocol - How to correctly set the status in the second request?

Asked 2018-Mar-20 at 12:52

I'm using TinyRadius to authenticate my Java WebServer (as Radius Client) to a Windows Server (as Radius Server).

I successfully sent the user Access-Request to the server and received the passcode back.

...

ANSWER

Answered 2018-Mar-20 at 12:48

There are a few issues in how I was sending the second request to the radius server.

Doing it this way did not work as STATE.getBytes() returned a differently-encoded String:

Source https://stackoverflow.com/questions/46485082

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install TinyRadius

You can download it from GitHub, Maven.
You can use TinyRadius like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the TinyRadius component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: