v1.5.3 Bug Reports and Comments

[sirhc]

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

Well this is where the Access Control List comes in as to whom can even attempt to login/hack the switch.

Now they would have to crack a device that is within the list and spring board off it into the switch.....who did you piss off?

[jakematic]

Seriously though, you should support passwords of at least 24 characters (128 bits). Some people are serious about security.

I concur.

In the corporate world this is becoming very commonplace... hell even my personal passwords are being migrated to 24+ chars, and most require 2FA.

[astounding]

Has anyone encountered this upgrading from v1.5.0 to v1.5.3? (This was a WS-12-250-DC revision F device...)

Unpacking firmware ...
/usr/bin/firmware_upgrade: line 164: i2cget: not found
Running preflash script ...
Error flashing boot configuration
/usr/bin/firmware_upgrade: line 227: mtd: not found

Ideas? I'll likely try again after a reboot tomorrow morning.

[Stephen]

That's a strange one, sometimes upgrading several version's up can cause issue's. It's not typical but it does happen. I think your current plan is a good idea. After the reboot, try again, if that doesn't work, try upgrading via a lower version first (like 1.5.2) 1.5.0 is pretty old now.

[sirhc]

That's a strange one, sometimes upgrading several version's up can cause issue's. It's not typical but it does happen. I think your current plan is a good idea. After the reboot, try again, if that doesn't work, try upgrading via a lower version first (like 1.5.2) 1.5.0 is pretty old now.

Or factory default then upgrade in case the config or flash is corrupted

[mlow]

Unable to use the domains ending in .network (a valid gTLD) for the NTP, SMTP or RADIUS host. Any TLD over 6 characters is rejected based on the pattern attribute of those form <input>'s.

[Stephen]

I'll add that to the list of things to fix.
In the mean time, if you have the ip addresses of where those services map too you should be able to use them that way.

[neteng]

I'm a small WISP and have had two Mikrotiks hacked, scripts inserted. So, I agree the security issue is important.

[neteng]

That's a strange one, sometimes upgrading several version's up can cause issue's. It's not typical but it does happen. I think your current plan is a good idea. After the reboot, try again, if that doesn't work, try upgrading via a lower version first (like 1.5.2) 1.5.0 is pretty old now.

Where can I find 1.5.2? I have several on 1.5.0.

[Stephen]

You can find it here