Sorry, I forgot that I also in an earlier stage had removed several more files in the pam.d dir...
1. remove _all_ files in the pam.d directory ( I think that the README-file in pam.d states that the "ohter"-file is used when the application-specific one is not found, thats why you probably still get prompted even with removed sshd files).
2. try to ssh with a working username
3. restart sshd
4. try to ssh with a working username
I can still login both in (2) and (4) without password.
I understand that it's really stupid to remove all files in the pam.d folder, but I'm still surprised that the default action is to allow rather than to deny.
I successfully tested this on fresh installed 8.1 & 9.1-rc3.
I have no better "proof" than my putty screenshots:
To the left, login with all pam files present, fist try, faulty password, no go.
Second try, correct pw, ok.
To the right, pam files removed, sshd restarted, it allows me in with no promt at all.
http://i.imgur.com/FNL9V.png
Again, maybe I'm just too much "what if", and this is how it's supposed to work, I just find it scary that a couple of lost files allows ssh access without a password.
Again, on my Ubuntu-machine, removed PAM-files will not allow me to login. (Even without a sshd restart).
If I'm already logged in, and try to use SUDO, it complains about a missing PAM file.
Disclaimer: I'm not an experienced freebsd-user at all, both my installs I tested this on was just freshly installed using the guided install with no changes to the default settings what so ever.