v1.5.3 Bug Reports and Comments

[Stephen]

FIXED/CHANGED
- fixed issue with watchdog poe bounce that was not completely shutting off power depending on the delay time and offset's used
- This version had to be pushed as a new production run has a new temp sensor as old was discontinued
- fixed memory leak in NET-SNMP

ENHANCEMENTS
- Modified Port Bounce option to read 'Port Bounce POE' and added 'Port Bounce Link' manual option for status and ports tab
- Option in discovery configuration now exists to disable the switch from broadcasting on discovery protocols while the discovery tab is enabled
- link bounce option exists for the watchdog as well as the POE bounce option.

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help

Released 7/27/2019

[Ludvik]

SNMP bug solved too? Like in 1.5.3rc2-201907151558?

[Stephen]

Thank you for the reminder Ludvick, yes that fix is in there. The temp sensor issue was an emergency and so we had to immediately wrap up everything and get this version out. However, the fix for what we found with snmp is in there (and I have updated the notes to reflect that).

[mducharme]

Hello,

We are having problems with special characters in passwords (we just upgraded to v1.5.2 last week). The upgrade to 1.5.2 from a much older version has fixed the issues with the # character in passwords, but we have a user with the characters " } ! | [ in their password and they cannot log in via RADIUS to a netonix. Our other users are fine, so the problem seems to be with one of those characters.

[Stephen]

The latest firmware is now at 1.5.3 but if this is an issue in our code I don't think the fix is there yet.
I will add this to the list and try to get it ready for the rc release.

[Ludvik]

Length of password is only 16 characters for RADIUS. I think that is bug.
We use Mikrotik's implementation (userman) and there is no length limit (or is very longer).

[sirhc]

Length of password is only 16 characters for RADIUS. I think that is bug.
We use Mikrotik's implementation (userman) and there is no length limit (or is very longer).

Not a bug, this was intentional.

More than 16 characters, really?

[Ludvik]

In secure environment ... bigger password is necessary. If you use phrase, you don't have problem with. If you use password manager, you don't have problem ...

16 is small. Very small limit. I could understand 40, but 16 couldn't.

If you have a hash, you don't care much about the length of the hashed text.

[jpaine619]

More than 16 characters, really?

Well, mathematically 16 bits of random text is roughly equal to an 80-bit encryption key. I.e if you want to crack a 128 bit cipher, you don't attack the cipher itself if the password is less than about 24 characters..(assuming all ASCII without mixed case or special characters).

Seriously though, you should support passwords of at least 24 characters (128 bits). Some people are serious about security. Why deploy a 128 bit WPA2 cipher if your password for it is gonna be less than 128 bits (effective)? That's like putting a shitty lock on a strong chain..

https://www.kryptel.com/articles/encryption_passwords.php

[sirhc]

Even with a 16 character limit on the password that is over 332,329,305,696,010,000,000,000,000,000 possible passwords.

Who is hacking you, the NSA?

I understand your thinking of using a phrase but come on.