Hi Mads and others;
Chris Murtagh has pointed out to me that this is sort of a non-issue
because the plan for 1.2 is to replace the users/members file with an
authentication database. Therefore this is likely to require a
certain amount of post install configuration before even the admin
interfac
>> So the .htaccess should be included in the rpm? In that case an upgrade
>> would introduce it again...
>>
>
> No. I was thinking of generating it the same way you generate the
> members file. I am assuming that what you put in that part of the
> script won't get regenerated on each upgrad
On 10/18/06, Mads Kiilerich <[EMAIL PROTECTED]> wrote:
> Chris Travers wrote, On 10/19/2006 12:52 AM:
> > (I
> > have renamed the spec file btw).
> >
>
> To ledgersmb.spec. The spec name usually matches the rpm name which
> matches the source-tar name - which often matches the domain/sf name.
> Whi
Chris Travers wrote, On 10/19/2006 01:24 AM:
> I think I fixed your error. Not 100% sure because I can't validate at
> the moment.
>
Nope, same problem in same line (which has moved):
[Thu Oct 19 02:08:38 2006] [error] [client 127.0.0.1] Can't connect to
data source , no database driver speci
On 10/18/06, Mads Kiilerich <[EMAIL PROTECTED]> wrote:
> Chris Travers wrote, On 10/19/2006 01:18 AM:
> > Would it be easier just to include by default a .htaccess file that
> > would deny access to the admin.pl with instructions on how to remove
> > it? Once you go to the admin.pl screen, if it h
Chris Travers wrote, On 10/19/2006 01:18 AM:
> Would it be easier just to include by default a .htaccess file that
> would deny access to the admin.pl with instructions on how to remove
> it? Once you go to the admin.pl screen, if it has a blank password,
> you will get prompted to enter another o
Chris Travers wrote, On 10/19/2006 12:52 AM:
> (I
> have renamed the spec file btw).
>
To ledgersmb.spec. The spec name usually matches the rpm name which
matches the source-tar name - which often matches the domain/sf name.
Which of these are wrong? ;=)
> Currently, to create a dataset, you
Any objection to having it write a .htaccess which denies access to
the admin.pl with a custom message explaining that one needs to remove
that file?
On 10/18/06, Mads Kiilerich <[EMAIL PROTECTED]> wrote:
> John Hasler wrote, On 10/19/2006 01:08 AM:
> > Create a password on the fly during installa
John Hasler wrote, On 10/19/2006 01:08 AM:
> Create a password on the fly during installation and mail it to root.
RPMs are often installed before mail is configured. And mails get lost.
And...
I would rather write such a password to a readable-by-root-only file...
But I doubt that we can do be
I think I fixed your error. Not 100% sure because I can't validate at
the moment.
On 10/18/06, Mads Kiilerich <[EMAIL PROTECTED]> wrote:
> Chris Travers wrote, On 10/18/2006 11:21 PM:
> > Hi all;
> >
> > I am adding the spec file to the source directory under dists/rpm.
> >
>
> Testing in trunk u
Would it be easier just to include by default a .htaccess file that
would deny access to the admin.pl with instructions on how to remove
it? Once you go to the admin.pl screen, if it has a blank password,
you will get prompted to enter another one.
With the .htaccess solution, we can provide a ni
Mads writes:
> Also, in case the rpm is installed by a clueless root it should not leave
> a door open to attackers. The rpm must be ensure that root and only root
> knows the master password. That's why I let the rpm contain a bogus
> password and provide instructions on how to reset it.
Create a
Ok. I think I know what the problem is. I can't validate where I am
at the moment, but I will try to correct it.
The admin.pl must not like the new db connection architecture (so I
will probably have to manually create the $form->{dbh} when saving a
user. No biggie. I will have it fixed tonigh
Chris Travers wrote, On 10/18/2006 11:21 PM:
> Hi all;
>
> I am adding the spec file to the source directory under dists/rpm.
>
Testing in trunk user creation dies with
[Wed Oct 18 23:32:15 2006] [error] [client 127.0.0.1] Can't connect to
data source , no database driver specified and DBI_DSN
I think you misunderstood me. I have decided that the instructions
are good enough at the moment but may need to be fine tuned later. (I
have renamed the spec file btw).
Currently, to create a dataset, you can supply the db superuser
information in addition ot the regular user. In this case, the
Chris Travers wrote, On 10/18/2006 11:21 PM:
Hi all;
I am adding the spec file to the source directory under dists/rpm.
Please name it ledger-smb.spec instead of just spec. ledger-smb.spec is
just the way it should be...
A few notes though that may cause issues:
1) If you follow the i
Hi all;
I am adding the spec file to the source directory under dists/rpm.
A few notes though that may cause issues:
1) If you follow the instructions, you will be unable to create new
datasets because you may need to log in as postgres to create the
database and add plpgsql.
2) There are a f
Thanks;
I will look at this if nobody gets to it first.
As for the list being a quite place, this is just a quite time. It
will pick up again :-)
Best Wishes,
Chris Travers
On 10/17/06, Mads Kiilerich <[EMAIL PROTECTED]> wrote:
> Hi,
>
> this list seems to be very quiet place... ;-)
>
> I have
Hi,
this list seems to be very quiet place... ;-)
I have tried to create a draft of an rpm spec. Please test and review!
Quick howto: Having /usr/src/redhat/SOURCES/ledger-smb-1.1.1d.tar.gz run
"rpmbuild -ba ledger-smb.spec" and "rpm -ihv
/usr/src/redhat/RPMS/noarch/ledger-smb-1.1.1d-1.noarch
19 matches
Mail list logo
