[scponly] Re: [Fwd: Bug#344418: updated patch for scponly chroot bug]

[Sven Hoexter]

On Mon, Feb 06, 2006 at 12:22:48PM +0100, Thomas Wana wrote:

Hi all,

> Martin Schulze wrote:
> > Are you able to provide a clean patch for this problem as well?
> > I guess that we should fix it since the administrator is under
> > the impression that scponly users can only run scponly commands,
> > i.e. scp and rsync, but not other programs.
> 
> I finally made a super-patch that fixes both problems for
> Debian Sarge (scponly-4.0). I backported the changes between
> 4.1 and 4.2 to 4.0 (since 4.2 only contained the bugfixes).
Donno if I missed some feature enhancements in scponly but in general I've
the feeling this ends up very close to the scponly 4.2 codebase or am I
completely wrong?
Guess that's kind of a catch22 problem with regard to the Debian
security policy.

> I'm also CCing this to the scponly list in case someone wants
> to look through it.
Hm that's quite hard to review cause of the regenerated autoconf stuff but
I guess cause of some changes in scponly it's not possible to patch it
without the regeneration?

Sven
-- 
Du kannst mit Träumen nicht diskutieren,
du kannst sie träumen oder verlieren.
   [ But Alive - Weißt nur, was du nicht willst ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ccs.neu.edu/pipermail/scponly/attachments/20060208/d4e85e9e/attachment.bin