*) allow to filter by IPv6 addresses and prefixes;
*) build 64-bit Winbox as well (https://mt.lv/FeuQe);
*) do not leave files locked on computer when uploading files to router;
*) fixed problem where some fields were not shown for read only users;
*) fixed Winbox crash when copying multiple files between routers;
*) make Ctrl+A work in script fields and other multiline fields;
*) make DLL hijacking attack not work: Winbox will not look at the directory it resides in, when looking for system DLLs;
*) on update, Winbox will check that code is signed by MikroTik and not somebody else;
*) removed Drag and Drop support on 64-bit Winbox in Wine;
*) show system note at login;
If you experience version related issues, then please report them to support@mikrotik.com.
If you try to upgrade directly from Winbox loader and version is not available, then you might need to wait for a while until cache in path between your device and our servers is refreshed.
I remember your report ages ago and I always wondered how long till they fix that. I find this unbelievable that update process is vulnerable like that. Well, good to know that it is not yet fixed.
Thanks for report.
Changing the updater to use https instead of current plaintext http would be good and simple first step. It’s nice bonus if it also checks new exe’s signature, but in first place, it should not allow anyone on the way to intercept requests so easily.
Make sure you don’t have anything in “/system note”, because that’s what the window is. From screenshot it doesn’t look like you have anything there, but even single space would be enough.
On macos catalina using wine64 and automation start winbox64.
Seems all normal. hex poe (v6.45.6). cpu is around 1~5%.
But if i go to IP-FIREWALL-Address lists tab, CPU goes up to 54% immediately, then hopping between 25%-57% constantly. Only when i click other tabs, CPU returns normal.
Anyone observes the same?
Are you planing to release a real macos app?.. or is this what we have to live with?.. the old winbottler was ok.. maybe I have done somthing wrong.. but its disturbing with the terminal in the background.
Making the window full screen in wine64 with winbox64 on macos Catalina breaks winbox - Just drag the edges to full screen if you want this to work.
Also attempting to export/import addresses crashes wine64 with noexec filesystem error and hangs winbox.
Other than the above it seems to be working to an extend - we can live with it until full support is released!
Drag and drop doesnt work for my.. when I try to upload firmware.. upload button in files doesnt do anything more then hang winbox.
How far aways are we from a real winbox app for macOS? Parallels isnt an option.. to slow to start.. and resourses.
Is their anyway to get rid of terminal when winbox is started from terminal?
When start new winbox (either 32bit or 64bit) I get message: “ERROR: Colud not save conffiguration”.
If I start with administrative privileges - no such error.
Also without administrative privileges I can’t connect to router. And with administrative privileges - without problem
could you please consider changing application bar/other WinBOX window component colour while in SafeMode? Regardless of information when exiting the app it would help to identify the current mode.
