I dont think that would have helped, half the issue was mixing environments. The master key was generated on Linux, where the passphrases weren't truncated, but it was being used on Solaris where they were. If it had been generated on Solaris or used in Linux the problem wouldn't be there. To find this in testing, you'd have to predict that "data being generated one place and used on another" could be a vector for bugs, and that's not necessarily obvious
Comments
I dont think that would have helped, half the issue was mixing environments. The master key was generated on Linux, where the passphrases weren't truncated, but it was being used on Solaris where they were. If it had been generated on Solaris or used in Linux the problem wouldn't be there. To find this in testing, you'd have to predict that "data being generated one place and used on another" could be a vector for bugs, and that's not necessarily obvious
"you'd have to predict that "data being generated one place and used on another" could be a vector for bugs, and that's not necessarily obvious"
It seems you never had to deal with file encodings? And windows upper lowercase does not matter, compared to linux where it does matter?
But yes, obvious was none of that to me, I naivly assumed, data should be just data, until I change it. Like they did.