Installing OpenFire 4.0.1 on CentOS 7
-
As promised, below is the output of the database security script....
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.Enter current password for root (enter for none):
OK, successfully used password, moving on...Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.Set root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.Remove anonymous users? [Y/n] Y
... Success!Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.Disallow root login remotely? [Y/n] Y
... Success!By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.Remove test database and access to it? [Y/n] Y
- Dropping test database...
... Success! - Removing privileges on test database...
... Success!
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.Reload privilege tables now? [Y/n] Y
... Success!Cleaning up...
All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.Thanks for using MariaDB
- Dropping test database...
-
So I just looked at this like 10 minutes ago and it was fine. I opened it now and the formatting is screwed up. It looks the same as it did on that Ansible write-up I did where the formatting was changing.
-
I'll try to get a rocket.chat server set up so I can do a write up for it. It looks interesting, and it's built on meteor/electron.
-
@johnhooks said:
So I just looked at this like 10 minutes ago and it was fine. I opened it now and the formatting is screwed up. It looks the same as it did on that Ansible write-up I did where the formatting was changing.
Looking okay here, for the moment, at least.
-
@johnhooks said:
I'll try to get a rocket.chat server set up so I can do a write up for it. It looks interesting, and it's built on meteor/electron.
Their site is down.
-
@scottalanmiller said:
@johnhooks said:
I'll try to get a rocket.chat server set up so I can do a write up for it. It looks interesting, and it's built on meteor/electron.
Their site is down.
I tried following their documentation last night and it didn't work out. I'll have to try to find some other people that have set it up.
-
@rocketchat looks amazing!
-
@anonymous said:
@rocketchat looks amazing!
Do you mean you have it up and running and it looks amazing... or the potential for it looks amazing?
-
Ha well, I just created an account for speak.io yesterday and I just went on the site to link it here and they're shutting down. I was going to say it's an interesting replacement for Skype and others, but never mind.
-
@johnhooks said:
Ha well, I just created an account for speak.io yesterday and I just went on the site to link it here and they're shutting down. I was going to say it's an interesting replacement for Skype and others, but never mind.
You know, I had looked at their site just this morning and thought "neat technology, but I could not see us using it." I feel like lots of people felt the same way.
-
@scottalanmiller said:
@johnhooks said:
Ha well, I just created an account for speak.io yesterday and I just went on the site to link it here and they're shutting down. I was going to say it's an interesting replacement for Skype and others, but never mind.
You know, I had looked at their site just this morning and thought "neat technology, but I could not see us using it." I feel like lots of people felt the same way.
I saw it linked in the Electron page, so I figured I'd just play around with it. It doesn't look like the cost was worth it, but it seemed to work well.
-
@johnhooks said:
@scottalanmiller said:
@johnhooks said:
Ha well, I just created an account for speak.io yesterday and I just went on the site to link it here and they're shutting down. I was going to say it's an interesting replacement for Skype and others, but never mind.
You know, I had looked at their site just this morning and thought "neat technology, but I could not see us using it." I feel like lots of people felt the same way.
I saw it linked in the Electron page, so I figured I'd just play around with it. It doesn't look like the cost was worth it, but it seemed to work well.
That's how I felt at a quick look. It looked like it would be an amazing open source project but it was very expensive and only duplicated functionality that we already have several different ways. Had it been free and open source, well worth looking into. As a paid service, it was of no interest.
-
So I decided to try hooking up a new install of openfire to my domain controller (Zentyal). Turns out you need a more recent version of prototype.js to make it work correctly.
cd /opt/openfire/plugins/admin/webapp/js; mv prototype.js prototype.js.old; wget https://ajax.googleapis.com/ajax/libs/prototype/1.7.1.0/prototype.js systemctl restart openfireAt that point clear your browser cache if you had started the setup configuration via web browser already, and you should be able to complete the setup using your Active Directory information.
I know, I know, way beyond the article scope, but I figured it would save some of us a little headache.
