*) console - resolved problem that appeared in version 5.4. it caused
‘sup-output’ command to crash console on systems with many ethernet
interfaces or very long interface names.
*) serial console - do not automatically send login prompt to attached
usb modem if no other serial port exists;
*) winbox - fixed scrolling in terminal window;
*) webfig - encrypt whole session even in non https mode;
*) do not show contents of skin files to users without
‘sensitive’ permission;
Already have such low space on routerboard 750 with 5.4 installed. Don’t know how I’m going to fit this update on for install =/ and have minimal packages installed =(
Nothing about any wireless improvements (NV2 disconnects etc.)!
And nothing about port flapping I guess? (It still exists on 5 different rb’s I have, all with 5.4 and updated firmware and MT radio cards)
To me this looks a ´minor´ upgrade I might as well consider not to use…
And why do I only get the notification e-mail on Sunday 26th? While the package is already out since 22nd?
and considering release - you should definitely use 5.5 if you are using webfig - encryption of session even over http, and login page changed solving a lot of login problems.
This is a matter that has bugged me since 5.5 was announced a week ago: how does encryption over http work? https in an obvious choice when encrypting traffic but http… the only way it may work is encrypting/decrypting traffic on both ends of a communication link, and I do not see how a browser can do it without using https. Does the browser run some sort of script that encrypts traffic? How is the encryption key adquired/shared? Is it public key? private key? OTP?
that is not private/public key as with ssl/tls encryption that we are used to use. But if you check packet sniff of webfig traffic you will see that it is not plain-text.
