Radclient - Invalid Pointer error.

[Arran Cudbard-Bell]

> On Jul 22, 2015, at 4:10 PM, Alan DeKok <aland at deployingradius.com> wrote:
> 
> On Jul 22, 2015, at 10:08 PM, Todd Smith <todd at sohovfx.com> wrote:
>> We are just warming up to radius implementation, I am testing on OpenSuSE13.2 with the following packages:
>> 
>> freeradius-server-3.0.3-3.8.1.x86_64
> 
>  Use 3.0.9.  We're not going to debug issues which were tracked down and fixed 6 months ago.

Seriously. Can someone explain the thinking behind users reporting defects on out of date versions?

Do they expect us to go back in time, to before we did that release and fix it, so they don't
experience the issue in the present?

Do they expect us to release patched versions of the 3.0.3 SuSE packages?

What's the deal here? Why do people do this? OP isn't the first...


This was even mentioned explicitly in the CONTRIBUTING doc I posted a couple of weeks ago:

2.BEFORE REPORTING A DEFECT

  Verify it's still present in the Git HEAD.  Checkout the appropriate branch for the version of the
  server you're working with as listed here (http://doc.freeradius.org), build the server, and attempt
  to reproduce your issue.

  The ChangeLog (https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/doc/ChangeLog) for the
  current stable branch may also be used to determine if your issue has already been addressed.
  The ChangeLog is updated as fixes are made to the server code, and usually reflects the state of the
  Git HEAD.

  Do not report non-security defects for EOL branches (as listed on doc.freeradius.org), they will be
  closed and locked.


-Arran
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20150722/336dba12/attachment-0001.sig>