Hello all.  The hard part of the copy patch is done.  I haven't gone down
and worked on the link into new/, but the delivery to tmp/ is completely
rewritten to make use of posix syscalls and stack based buffers instead
of new/delete'd ones.  The size is determined at runtime by querying
the OS.

The patch is 200 lines long so it's here:

http://www.technocage.com/~caskey/bincimap/copyA-1.0.24.patch

When I go over the second half of the copy command, that'll go up as copyB.

The other two patches I have for the io bug which is not strictly necessary
if Andreas has already rewritten the code and my change to enable the
setuid and setgid to be toggled off are here:

http://www.technocage.com/~caskey/bincimap/configs-1.0.24.patch
http://www.technocage.com/~caskey/bincimap/io-1.0.24.patch

As a side note for those doing testing, try this:

Edit the default config and turn off chroot, setgid, setuid and set
the logger to 'stderr'.  Then create a test homedir/maildir like so:

[EMAIL PROTECTED] ~/ $ mkdir -p binctest/home/Maildir/{cur,new,tmp}

Then run the server using your new config and a faked checkpassword:

[EMAIL PROTECTED] ~/ $ tcpserver localhost 14300 --conf=./bincimap.conf 
/usr/bin/printf '%s\n%s\n' user.user /home/user/binctest/home

That will enable any client to connect locally and make testing binc code
easier without having to actually install it on a system as root.  The
bogus checkpassword using printf will simply authenticate any username/password
into the test maildir.

Copy a few sample messages from an existing maildir into the Maildir/new and
you're good to go.

C=)

-- 
--------------------------------------------------------------------------
     Better the hard truth than the comforting fantasy. -- Carl Sagan
--------------------------------------------------------------------------
Caskey <caskey*technocage.com>       ///                   TechnoCage Inc.
--------------------------------------------------------------------------
 A presumption on your part does not constitute an obligation on my part.

Reply via email to