https://bugs.kde.org/show_bug.cgi?id=496581
--- Comment #2 from Ian Abbott <i...@abbott.org> --- After a bit more digging in the Ampache sources on GitHub, the "<compatible>" element was introduced in 3.5.2 and its value 350001 has remained consistent ever since. The value of the "<version>" element was a single, monotonically increasing integer until version 5.0.0 when it changed to the dotted triplet format. (The monotonically increasing integer vaguely mapped onto the dotted triplet, but not in a consistent way.) So if the code used the value of the "<compatible>" element in preference to the value of the "<version>" element, it will get an old number 350001 if the "<compatible>" element exists, but that will be sufficiently large to determine that the SHA256 hash method should be used. @Tuomas I can set up a test account for you on my home Ampache server if you like. It's a couple of major versions behind the latest 7.x.x so only supports Ampache API versions 3, 4 and 5, but it should be good enough for testing authentication methods. -- You are receiving this mail because: You are watching all bug changes.
