Dude 6.40 changelog ?

RouterOS The Dude
1

Any changelog for Dude 6.40 ?

2

carnivean,

It seems that currently Dude v6 development is postponed.

The_Dude_v6/dude_v6.xx_changelog show us that last changes were made in v6.39 - 2017-Apr-27 10:06.

ROS changelog shown only one Dude related changes after 6.39.
Release 6.40 - What’s new in v6.40 (2017-Jul-21 08:45):

*) dude - fixed server crash;

Thank you!

3

All the major issues are fixed, the minor issues will be fixed in order of priority.
Do you have any major problems that need to be addressed?

4

I discovered bad security defect in Dude - it is possible to read passwords of devices monitored by Dude by users which do not have the “sensitive” policy enabled. This way such read-only dude user can for example login to router with winbox, if such tool using password entered in device settings is defined in Dude.

How to reproduce:

  1. enter password for some device in device settings in Dude
  2. define new dude Tool, name it for example “Pwd” and enter this command: http:///[Device.Password]
  3. create new user “dude” and add it to group with only dude policy enabled (sensitive and password policies not checked)
  4. login to Dude client with user dude
  5. run “Pwd” tool on the device - it opens browser with device password in URL

Please fix this ASAP, as this bug blocks our usage of Dude for tech support staff with read-only privileges.

5

Yes Normis, I’ve reported problem in VirtualBox and SNTP client on CHR. There is a bug with CHR and VirtualBox when you reboot CHR. The clock is not saved and clock changes after next boot. Then Dude starts and malforms its base. You guys have this reported and ticketed already. Still waiting for a fix thou :frowning:

6

Raf - This is CHR issue not Dude problem. Debugging of this problem is in our to-do list!

7

Yeah… sorry about that. Since Dude is on CHR I sometimes take them as one thing :slight_smile: My bad.

8

CHR time bug is a separate thing.
BUT, that doesn’t mean that Dude isn’t at fault too, if the clock happens to go backwards - which it will certainly do at least once a year at DST end.
Dude should cope with this sort of thing, rather than making a mess of its database on such happenings.
Don’t just ignore things like this. There IS something to fix.

9

Yeap, i have a problem with some itens not displaying interface traffic. Note that SNMP readings on the label shows correctly. Everything used to work fine at Dude 3.6

At the image you can see that some links display the information correctly others just show a " ? " sign. It doesn´t happen to a specifc device or brand, it´s random thing.

Interface display the information “unknown”

10

I’m having the same problem as the friend above.

In DUDE 3.6 this does not happen, but in update 6.40 it is frequent. Why is this happening?

11

Are we still going to get new features, there’s a number of things it would be nice to have?

12

normis,

Recently, an issue was addressed to the support and we got a reply.

I don’t know which Criticity level on it - Ticket#2017052222001251. Sometime it may be like a closed eyes. And currently we didn’t get a practical issue with it.
Dude v6 - Dependencies - How does it work?

If you heave a time and possibility, please look on it.


Thank you!

13

normis,

But we periodically get only up notifications for some devices, which may confuse us: Ticket#2017052022000551.

Dude v6 - Dependencies - How does it work?

If you heave a time and possibility, please look on it.


Thank you!