I've been very careful to keep corporate stuff separate from the Open Source FreeRADIUS side. That being said, most FreeRADIUS development is now done under the banner of "Network RADIUS", which is a company I started in 2008. For the past few years, myself, Arran, Matthew, and a few others who contribute heavily to FreeRADIUS are largely paid out of consulting and support around FreeRADIUS. This process has greatly increased the amount of time we can spend on FreeRADIUS. It has also enabled us to develop new features, including the (alleged) v4 release. It has given us a number of significant improvements in 3.0.22 (to be released soon), thanks to Terry and Nick. This work has also funded me to participate in the IETF, where I help to set many of the new RADIUS and EAP standards. I don't get paid for writing standards, but it does mean that FreeRADIUS and myself get to be known as the leaders in the space. It also means that we get to work directly with large companies such as Microsoft, Cisco, and Apple. It means that we get to be seen as a "major player" in the space, just like Microsoft, Cisco, and Apple. As an example, we've been working closely with the Microsoft engineering team in order to standardize and fix issues with EAP-TLS, for TLS 1.3. This is a big change from 10 years ago, when Microsoft would just ship code, and be surprised when it broke every RADIUS server out there. As of today, FreeRADIUS and Microsoft implement the new standard. No commercial RADIUS server can say that. So in the 20+ years of FreeRADIUS, we have gone from a small Open Source project to the leader in the space. Multiple companies rely on FreeRADIUS, and a number have dropped their "in house" RADIUS server, and replaced them with FreeRADIUS. That being said, there's always more to do, and new goals to reach. To that end, I've started writing background articles which are hosted on the companies web site. These articles are not directly "how to" configure FreeRADIUS. Instead, they explain at a high level how RADIUS fits into a larger ecosystem. The articles talk about ISP environments (large and small), universities, Active Directory, etc. They explain *why* things happen, and *how* they happen. So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email? I don't normally allow off-topic discussions on the list, but I think the content could potentially be interesting and/or helpful enough to be relevant here. Please discuss. Alan DeKok.
On 20 Apr 2021, at 13:51, Alan DeKok wrote:
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I’m absolutely OK with that. Thanks for all your work! -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
That would be great. Thanks On Tue, 20 Apr 2021, 14:01 Sebastian Hagedorn, <Hagedorn@uni-koeln.de> wrote:
On 20 Apr 2021, at 13:51, Alan DeKok wrote:
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I’m absolutely OK with that. Thanks for all your work! -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Same here! Sent from my iPhone
On Apr 20, 2021, at 8:01 AM, Sebastian Hagedorn <Hagedorn@uni-koeln.de> wrote:
On 20 Apr 2021, at 13:51, Alan DeKok wrote:
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I’m absolutely OK with that. Thanks for all your work! -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Alan, Congrats for great work! Go ahead and post those articles, like you said, they will be beneficial to us. It is OK. Regards, Raj On Tue, Apr 20, 2021, 14:55 Alan DeKok <aland@deployingradius.com> wrote:
I've been very careful to keep corporate stuff separate from the Open Source FreeRADIUS side. That being said, most FreeRADIUS development is now done under the banner of "Network RADIUS", which is a company I started in 2008.
For the past few years, myself, Arran, Matthew, and a few others who contribute heavily to FreeRADIUS are largely paid out of consulting and support around FreeRADIUS. This process has greatly increased the amount of time we can spend on FreeRADIUS. It has also enabled us to develop new features, including the (alleged) v4 release. It has given us a number of significant improvements in 3.0.22 (to be released soon), thanks to Terry and Nick.
This work has also funded me to participate in the IETF, where I help to set many of the new RADIUS and EAP standards. I don't get paid for writing standards, but it does mean that FreeRADIUS and myself get to be known as the leaders in the space. It also means that we get to work directly with large companies such as Microsoft, Cisco, and Apple. It means that we get to be seen as a "major player" in the space, just like Microsoft, Cisco, and Apple.
As an example, we've been working closely with the Microsoft engineering team in order to standardize and fix issues with EAP-TLS, for TLS 1.3. This is a big change from 10 years ago, when Microsoft would just ship code, and be surprised when it broke every RADIUS server out there.
As of today, FreeRADIUS and Microsoft implement the new standard. No commercial RADIUS server can say that. So in the 20+ years of FreeRADIUS, we have gone from a small Open Source project to the leader in the space. Multiple companies rely on FreeRADIUS, and a number have dropped their "in house" RADIUS server, and replaced them with FreeRADIUS.
That being said, there's always more to do, and new goals to reach.
To that end, I've started writing background articles which are hosted on the companies web site. These articles are not directly "how to" configure FreeRADIUS. Instead, they explain at a high level how RADIUS fits into a larger ecosystem. The articles talk about ISP environments (large and small), universities, Active Directory, etc. They explain *why* things happen, and *how* they happen.
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I don't normally allow off-topic discussions on the list, but I think the content could potentially be interesting and/or helpful enough to be relevant here.
Please discuss.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 20/04/2021, at 11:51 PM, Alan DeKok <aland@deployingradius.com> wrote:
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I’d be very supportive of this, either as full text of the articles, or links. If you choose to do links, perhaps an abstract would be useful. I think education about exactly this - how RADIUS fits in - would be great for newcomers to this list, and give something to point to when there are questions where the problem is not with FreeRADIUS the software, but more a misunderstanding of RADIUS as a protocol. I get it how users get to that point - when I first looked at RADIUS in I guess 2000 or so, I thought it was something I could use to do website filtering. I semi-regularly have off list discussions with folks who have those sorts of misunderstandings, when I have time to engage, and try give them “ecosystem” advise to steer them straight. More easily accessible high quality background information would be a very welcome resource, in my view. Two suggestions: 1) I don’t know if the articles have comments/questions/whatever. If they do, perhaps it’s good to mention that in the posts, to keep that non-FreeRADIUS-software discussion off the list. 2) Note that the articles are posted by Network RADIUS who develop FreeRADIUS, and that the list isn’t somewhere for any old person to advertise their poorly researched blog post.. :-) -- Nathan Ward
On Apr 20, 2021, at 8:14 AM, Nathan Ward <lists+freeradius@daork.net> wrote:
I’d be very supportive of this, either as full text of the articles, or links. If you choose to do links, perhaps an abstract would be useful.
My $0.02 right now is a one-paragraph abstract, followed by a link. That's enough for people to get the idea, without getting pages of text.
I think education about exactly this - how RADIUS fits in - would be great for newcomers to this list, and give something to point to when there are questions where the problem is not with FreeRADIUS the software, but more a misunderstanding of RADIUS as a protocol. I get it how users get to that point - when I first looked at RADIUS in I guess 2000 or so, I thought it was something I could use to do website filtering. I semi-regularly have off list discussions with folks who have those sorts of misunderstandings, when I have time to engage, and try give them “ecosystem” advise to steer them straight.
There's also the FreeRADIUS technical guide, which is a good introduction: https://networkradius.com/doc/FreeRADIUS-Technical-Guide.pdf Maybe it would be better to split that work out into multiple articles.
More easily accessible high quality background information would be a very welcome resource, in my view.
We're also working on that for v4. And trying to update the docs so that they're clearer and better organized.
1) I don’t know if the articles have comments/questions/whatever. If they do, perhaps it’s good to mention that in the posts, to keep that non-FreeRADIUS-software discussion off the list.
The articles don't have comments or questions. I really don't want to turn each article into an endless series of "Hi, nice article! How do I configured <unrelated topic>". I'm sort of OK with discussing some of the contents here. But realistically, this list isn't the place to discuss "how RADIUS works". It's not really the place to learn more about RADIUS. The success of this list has been in part due to extreme focus on technical content. We regularly get generic questions about RADIUS. "Hi, I'm writing a new RADIUS thing, can you explain how...". And the answer is "no". Such topics are not relevant for this list. Beside the morality issue of "Im getting paid to do this work, but because I don't know anything, I'm asking you to help me for free, on topics unrelated to FreeRADIUS".
2) Note that the articles are posted by Network RADIUS who develop FreeRADIUS, and that the list isn’t somewhere for any old person to advertise their poorly researched blog post.. :-)
Yes, we'll do that. Alan DeKok.
"More easily accessible high quality background information would be a very welcome resource, in my view." And low level. The current documentation includes very little "who, what, when, why, and how" information. Learning freeradius from scratch is not ap pleasant experience.
On Apr 20, 2021, at 6:51 AM, Alan DeKok <aland@deployingradius.com> wrote:
I've been very careful to keep corporate stuff separate from the Open Source FreeRADIUS side. That being said, most FreeRADIUS development is now done under the banner of "Network RADIUS", which is a company I started in 2008.
Just to be clear, there's still a large amount of work that is _NOT_ under the Network RADIUS corporate banner. Alan is the only stakeholder in NetworkRADIUS who's involved in the project, the rest of us are contractors who are paid out of support and professional services revenue (as Alan says). Who owns the copyright on the code is important as neither NetworkRADIUS nor Alan can change the license on FreeRADIUS without the agreement of the other copyright holders. i.e. NetworkRADIUS cannot change the license to suit corporate priorities as has happened with Redis/Redis Labs and others... With that said, Network RADIUS has sponsored a lot of the documentation for the upcoming release of v4, and paid for 50% of the new website and documentation site (I put up the other 50%). Features that just wouldn't make it into the project otherwise like sigtran and the EAP-AKA* methods were sponsored through/by Network RADIUS. Network RADIUS also sponsored the majority of the documentation for the v4.0.x release, so the involvement of a corporate sponsor is a definite net benefit. I for one have no issues with Alan posting Network RADIUS articles to the mailing list and will likely be involved in creating content for some of them :) -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Hi, It's not only that I'd be ok with it. I'm looking forward to it. Also, as many others have said, many thanks for the hard work over these years. Cheers, Alex El 20/4/21 a las 13:51, Alan DeKok escribió:
I've been very careful to keep corporate stuff separate from the Open Source FreeRADIUS side. That being said, most FreeRADIUS development is now done under the banner of "Network RADIUS", which is a company I started in 2008.
For the past few years, myself, Arran, Matthew, and a few others who contribute heavily to FreeRADIUS are largely paid out of consulting and support around FreeRADIUS. This process has greatly increased the amount of time we can spend on FreeRADIUS. It has also enabled us to develop new features, including the (alleged) v4 release. It has given us a number of significant improvements in 3.0.22 (to be released soon), thanks to Terry and Nick.
This work has also funded me to participate in the IETF, where I help to set many of the new RADIUS and EAP standards. I don't get paid for writing standards, but it does mean that FreeRADIUS and myself get to be known as the leaders in the space. It also means that we get to work directly with large companies such as Microsoft, Cisco, and Apple. It means that we get to be seen as a "major player" in the space, just like Microsoft, Cisco, and Apple.
As an example, we've been working closely with the Microsoft engineering team in order to standardize and fix issues with EAP-TLS, for TLS 1.3. This is a big change from 10 years ago, when Microsoft would just ship code, and be surprised when it broke every RADIUS server out there.
As of today, FreeRADIUS and Microsoft implement the new standard. No commercial RADIUS server can say that. So in the 20+ years of FreeRADIUS, we have gone from a small Open Source project to the leader in the space. Multiple companies rely on FreeRADIUS, and a number have dropped their "in house" RADIUS server, and replaced them with FreeRADIUS.
That being said, there's always more to do, and new goals to reach.
To that end, I've started writing background articles which are hosted on the companies web site. These articles are not directly "how to" configure FreeRADIUS. Instead, they explain at a high level how RADIUS fits into a larger ecosystem. The articles talk about ISP environments (large and small), universities, Active Directory, etc. They explain *why* things happen, and *how* they happen.
So the question is, would the list be OK with me posting occasional articles here? It would be no more than once a week. Or, would the list subscribers be OK with being sent links to the articles as a separate email?
I don't normally allow off-topic discussions on the list, but I think the content could potentially be interesting and/or helpful enough to be relevant here.
Please discuss.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Alejandro Perez-Mendez Technical Specialist (AAA), Trust & Identity Skype alejandro_perez_mendez jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under company number. 05747339, VAT number GB 197 0632 86. Jisc’s registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 02881024, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. Jisc Commercial Limited is a wholly owned Jisc subsidiary and a company limited by shares which is registered in England under company number 09316933, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800. For more details on how Jisc handles your data see our privacy notice here: https://www.jisc.ac.uk/website/privacy-notice
Hi I'm okay with this, nice small pointers to articles or info that might be useful. Many might not see eg similar tweets alan
participants (10)
-
Alan Buxey -
Alan DeKok -
Alejandro Perez-Mendez -
Anthony Stuckey -
Arran Cudbard-Bell -
Dan Swartzendruber -
Nathan Ward -
Pizu -
rajabu kitindi -
Sebastian Hagedorn