2.0.2 ???
-
Hi…
Updated my 2.0.1 64bit which turned it into a i386.
A lot of my packages need to be reinstalled due to the changed i386 binaries...Give it a try , not really needed a 64-bit anyway....
/Michael
You must have done something wrong because I updated my 2.0.1 amd64 install to 2.0.2 and it stayed 64bit. It installed perfect, no surprises, everything just worked.
Oh one thing I did notice, I added in an 'authorized_keys' into the root's ~/.ssh and it got deleted, had to put it back.. (the id_rsa file and known_hosts files remained however)
-
Oh one thing I did notice, I added in an 'authorized_keys' into the root's ~/.ssh and it got deleted, had to put it back.. (the id_rsa file and known_hosts files remained however)
Don't do that. Add keys in the user manager where they belong.
-
You can do that? Cool, I didnt even know it was a feature. I will switch to doing it that way.
-
Oh one thing I did notice, I added in an 'authorized_keys' into the root's ~/.ssh and it got deleted, had to put it back.. (the id_rsa file and known_hosts files remained however)
Don't do that. Add keys in the user manager where they belong.
Btw in UserManager there is no indication/hint that an account has an authorized_keys key defined. It's only after one clicks the "Click to paste an auth key" that UM webpage expands to show it.
PS: v2.1-BETA
-
I used the Invoke Upgrade option in the WebGUI to upgrade my 2.0.1 32bit-i386 installation and it was the fastest and easiest upgrade I've ever done to one of my machines.
The only thing I noticed was that I had to check the box to enable the pfBlocker package, the only package I'm using. The package didn't need to be reinstalled, just the box to enable it checked, and it kept all the CIDR lists I had set up.
