Upgrade Problem

Nef Kho

Upgrade Problem

« on: December 06, 2000, 08:04:31 AM »

I install a new e-smith and update it with the new release version when i restore my back-up from the previous
version I get an error when I access imp, the error is:

Forbidden: You don't have permission to access /horde/imp on this server.

any one know what the proble is? imp is not under i-bays so i cant apply the how to stated on the upgrade procedure. Thanks

Logged

hanscees

RE: Upgrade Problem

« Reply #1 on: December 06, 2000, 05:49:37 PM »

perhaps this has to do with the bug in ftp after the upgrade?? ftp won't let you put any files in your home directory after the upgrade to 4.01? See newbie forum

Logged

Gordon Rowell

FTP restricted to ~/home (was RE: Upgrade Problem)

« Reply #2 on: December 06, 2000, 06:44:10 PM »

hanscees wrote:

> perhaps this has to do with the bug in ftp after the upgrade??

It is not a bug. This is an intentional design decision for 4.0.1

> ftp won't let you put any files in your home directory after
> the upgrade to 4.01? See newbie forum

FTP should not have been allowed to write to you home directory -
it should have been restricted to ~/home to make it consistent
with Samba and (now) netatalk.

Gordon

Logged

Charlie Brady

RE: FTP restricted to ~/home (was RE: Upgrade Prob

« Reply #3 on: December 06, 2000, 07:09:10 PM »

Gordon Rowell wrote:

> hanscees wrote:
>
> > perhaps this has to do with the bug in ftp after the
> upgrade??
>
> It is not a bug. This is an intentional design decision for
> 4.0.1

There is also a bug in the upgraded ftp (which is the latest release from the proftpd people).

> > ftp won't let you put any files in your home directory
> after > the upgrade to 4.01? See newbie forum
>
> FTP should not have been allowed to write to you home directory
> - it should have been restricted to ~/home to make it
> consistent with Samba and (now) netatalk.

The proftpd daemon in our 4.0.1 update does not accept uploads in PASV mode, even if there is write permission - this is a known proftpd bug. Unfortunately, they have not yet fixed it in their released version.

There is a workaround (don't use PASV mode), and I have a proftpd RPM with a patch applied in my contrib directory on ftp.e-smith.org. Please note - I have not yet tested this new version, I just applied the patch which I extracted from the CVS version of proftpd and built a new RPM.

I will make sure that our bug page is updated with this information today.

Regards

Charlie

> Gordon

Logged