Bareos and PostgreSQL 10

[Dakota Pilot]

Has anyone used Bareos 17.2 current version with Postgres 10? The specs simply say Postgres needs to be above a certain version so I assume it will work but before I spend time on it I want to check and see if anyone has tried it. I assume that I'd need to run the scripts to update bareps tables and grant privileges.

Also, do you set a password for bareos user for the Postgres database? My Bareos install on Centos 7 never gave me the opportunity to set it.

[Andreas Haase]

Good morning,

Am 06.09.2018 um 00:42 schrieb Dakota Pilot:
> Has anyone used Bareos 17.2 current version with Postgres 10? The specs simply say Postgres needs to be above a certain version so I assume it will work but before I spend time on it I want to check and see if anyone has tried it. I assume that I'd need to run the scripts to update bareps tables and grant privileges.

According to changelog support for PostgreSQL 10 was added in 17.2.6.

> Also, do you set a password for bareos user for the Postgres database? My Bareos install on Centos 7 never gave me the opportunity to set it.
>

In Debian "su postgres -c psql" works without any password. You could
try that, too. If this doesn't work, you'll find you catalog
configuration in /etc/bareos/bareos-dir.d/catalog/*.conf, which also
includes username and password for connectiing the database.

Regards,
Andreas

[Dakota Pilot]

Thank you. I never found the changelog so that's good news. I'll have to upgrade to 17.2.6 as I'm at 17.2.4.

The su postgres -c psql works fine in Centos, too but I was wondering what the normal practice was for Bareos. Do people just leave it as is with a blank password or change it and if they change it what can break. I hope it's as simple as setting the password in the conf file and then running a database script or setting the password in Postgres but I didn't want to try it and break something.

[Andreas Haase]

Hello,

Am 06.09.2018 um 10:26 schrieb Dakota Pilot:
> Thank you. I never found the changelog so that's good news. I'll have to upgrade to 17.2.6 as I'm at 17.2.4.

http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-650000L
;-)

Reference manual is a quite good point to start at if you are looking
for some special point. While documentation could be improved for some
special features, the common things for setup and release notes and so
on are documented very well.

> The su postgres -c psql works fine in Centos, too but I was wondering what the normal practice was for Bareos. Do people just leave it as is with a blank password or change it and if they change it what can break. I hope it's as simple as setting the password in the conf file and then running a database script or setting the password in Postgres but I didn't want to try it and break something.
>

So you do not have any password in your catalog configuration? If there
is a password, bareos uses the user bareos with the configured auth
secret. So changing the password for user postgres shouldn't break anything.

Regards,
Andreas

[Dakota Pilot]

On the whole I find Bareos documentation pretty good. I checked the website and some other sources for system requirements and never found links to the release notes.

As far as the password goes it really doesn't matter one way or the other. I come from where everything has passwords and I'm trying to find out what others do - what is general practice. The docs say nothing about it and I assume Bareos has set things up to be pretty secure. My installation has no password in the catalog configuration nor was I asked for one when I ran the install via yum.

I'm not sure what auth secret you are referring to. The bareos user in postgres has no password. I'm wary of changing passwords after the fact for apps like Bareos because things can break badly.

I guess what I'm asking is what does Bareos recommend. Should I apply a password to the database user and if so I assume I change it in the catalog and in postgres also. Do I need to do anything other than restart the bareos services?

Thank you.

[Dakota Pilot]

On Thursday, September 6, 2018 at 2:16:22 AM UTC-4, Andreas Haase wrote:
> Good morning,
>
>
> Am 06.09.2018 um 00:42 schrieb Dakota Pilot:
> > Has anyone used Bareos 17.2 current version with Postgres 10? The specs simply say Postgres needs to be above a certain version so I assume it will work but before I spend time on it I want to check and see if anyone has tried it. I assume that I'd need to run the scripts to update bareps tables and grant privileges.
>
> According to changelog support for PostgreSQL 10 was added in 17.2.6.
> > Also, do you set a password for bareos user for the Postgres database? My Bareos install on Centos 7 never gave me the opportunity to set it.
> >

Okay. Well, it's not available for general download so I'll have to wait till it catches up.

[Jörg Steffens]

By default, Bareos uses ident identification with Postgresql. This is a
default method of Postgres. A unix user can access a local database
which is named identical to the user. Therefore the Unix user bareos can
access the local Postgres database bareos, as Postgres can check if a
query is really issues by the local user. I consider this as secure enough.
Postgres has also a method to extend the behavior for network based
database access. This is something I would avoid and would use a
password based authentication instead.

--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

[Dakota Pilot]

Thanks for the input. I'm happy with the ident for bareos. I only use password and not clear text! for all other connections from other systems.