+-Thomas 'Balu' Walter-([EMAIL PROTECTED])-[25.06.01 17:10]:
> Additionally I would restrict the access to localhost e.g.
>
> GRANT ALL PRIVILEGES ON ${ASPSEEK_SQLDB}.localhost TO
> ${ASPSEEK_SQLUSER}@localhost IDENTIFIED BY '$DB_PASSWD';
My fault - just ignore that one :)
>
> And perhaps
>
> REVOKE GRANT OPTION ON ${ASPSEEK_SQLDB}.localhost TO
> ${ASPSEEK_SQLUSER}@localhost IDENTIFIED BY '$DB_PASSWD';
>
> to disallow granting (dunno if grant is included in ALL PRIVILEGES in
> the actual mysql-version)
Looks like it does not give grant by default.
BUT
I tried to do it manually:
mysql -u root -p mysqlV
CREATE DATABASE aspseek;
GRANT ALL PRIVILEGES ON aspseek.* TO aspseek@localhost IDENTIFIED BY
'censored';
flush privileges;
When adding the aspseek/etc/sql/mysql/tables.sql using
mysql -u aspseek -p aspseek < /usr/local/aspseek/etc/sql/mysql/tables.sql
I get
ERROR 1073 at line 36: BLOB column 'word' can't be used in key
specification with the used table type
Okay - forget it, I was still running mysql-3.22, after upgrading to
3.23 it seems to work. (just for the archive if someone looks for this
error ;)
And now my server is running on debian "testing"-distrib, because
aspseek seems to use many new packages. I am not sure if I am glad about
that... 8)
Balu
