Since SFOS/XG is a GUI to a collection of disparate open source softwares, I suspect that having "admin" as the default for all of these is almost a requirement. Probably that most of these softwares handle uppercase/lowercase differently for the username/password combo, and also the password complexity most certainly has different requirements for each. Communications between these modules must have its own level of complexity to keep it minimalistically secure ... Strongswan, Exim and all are all software that do not care whether they are running or not on the same devices.
Since SFOS/XG is a GUI to a collection of disparate open source softwares, I suspect that having "admin" as the default for all of these is almost a requirement. Probably that most of these softwares handle uppercase/lowercase differently for the username/password combo, and also the password complexity most certainly has different requirements for each. Communications between these modules must have its own level of complexity to keep it minimalistically secure ... Strongswan, Exim and all are all software that do not care whether they are running or not on the same devices.
Well, they are renaming root to admin so why is it so difficult to rename it to something else? I imagine they have the same issue as calling eth0 port 1 and it took till v18 to rename a port in the gui.
I remember a thread in v16 where I was complaining about otp + caa not working anymore. Someone from Sophos replied that to separate admin from otp required them to a complete authentication redesign. They gave other issue to “fight” against with now.
