Finally! After nearly 2 decades of development, I can proudly announce a worthy two oh release! In addition I’m releasing 1.9 community edition as well. Last but not least, I’m providing NeDian20, which is a small Debian 10 appliance running NeDi 1.9C.
Security researcher Veno Eivazian found some vulnerabilities in Nodes-Traffic and Monitoring-History (only exploitable by authenticated users). I thank him for contacting me thus helping to improve NeDi! He mentioned System-Files as well, but as this module can perform actual software updates and is only accessible by admins, any “mitigation” would defeat its purpose. Please update…
Yes as in Genesis 3:22 (2023 backwards). We’ll see what this year holds for mankind! However I’m still working on making the (networking) world a better place. NeDi 2.3 is out and the 2.2 community edition is available as well. Both are PHP8.x compatible to keep it safe and up-to-date. Please contact us, if you…
A new milestone has been achieved! This version provides improvements in the the discovery algorithm, the device backup (adding comparison to saved configs) and many frontend enhancements! The layer 3 map automatically adds a subnet-cloud, if more than 2 interfaces belong to the same network. New icons let you draw simplified maps for documentation purposes….
After 18 years of NeDi development, it’s time to move on to a 2.0 major release cycle. Looking back, it’s been a great journey so far. NeDi 1.9 is doing fine in our customer networks and 1.8C has been released to the public a few weeks ago. Version 2.0 is under heavy development and will…
…seems to change on a monthly basis. I feel it will get even weirder than the past 2 years have been! NeDi’s development focusses more on core functions and stability these days, which allows me to work on this website some more. You’ll see changes soon as the relentless probes for vulnerabilities are annoying! But…
As Cyber attacks seem to move more into the focus of the WEF, I wanted to let you know that you can lock down NeDi some more by simply deleting devwrite.pl from nedi’s inc/ folder. It might be a good idea to do that anyway, if you don’t intend to use Devces-Write from the GUI….