Authentication works with Aalto password as a fallback these days, so you’re most likely using that to log in. You can’t, however, change your Niksula password without knowing your Niksula password. New users (starting from September 2012) do not have a Niksula password at all; use https://password.aalto.fi/ to change your Aalto password.
There are too many possible issues to list. If you are using a program remotely on a Niksula machine via SSH, results will depend on at least the following things:
To understand, you should read about internationalization variables.
The way these environment variables propagate, and how the system is supposed to work is as follows:
LANG (possibly other
LC_* to the server. In OpenSSH, this is done with the
SendEnv option in
ssh_config, and is the default on many operating systems that ship OpenSSH (notably not some versions of Mac OS X). PuTTY on Windows does not send these environment variables, but may be configured to do so.
AcceptEnv to accept these environment variables from the client, and it sets them for the user shell it launches. If it does not receive environment variables from the client, then the user shell inherits the ssh server’s environment (in Niksula, all processes have a default value for
LANG inherited from
Complexity to this is added by the fact that some programs implement their own workarounds for issues (eg.
-U option), and that programs running under
tmux might be attached to from different environments, and those programs’ process environments will reflect the one they were started in.
In Niksula, processes have
LANG=en_US.UTF-8 by default, because if the ssh client does not specify its environment, we have to guess, and even PuTTY today defaults to UTF-8 (since beta 0.63).