1.0.7 ldap problems
Hello!
Did not find any problem in the mailing list archive, so I am writing to you.
Tried to compiled it, but got the attached ldap error. I had a look into
ldap.h, which is correct.
Can somebody point out where exactly the problem is why gnupg does not compile?
I also attached ldap.h (just to be sure it's correct).
Sincerly,
Nico Schottelius
p.s.: please cc me, I am not subscribed.
--
Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt mails
to mailing list!). If you don't know what pgp is visit www.gnupg.org.
(public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key)
/*
* Copyright 1998,1999 The OpenLDAP Foundation, Redwood City, California, USA
* All rights reserved.
*
* Redistribution and use in source and binary forms are permitted only
* as authorized by the OpenLDAP Public License. A copy of this
* license is available at http://www.OpenLDAP.org/license.html or
* in file LICENSE in the top-level directory of the distribution.
*/
/* Portions
* Copyright (c) 1990 Regents of the University of Michigan.
* All rights reserved.
*
* Redistribution and use in source and binary forms are permitted
* provided that this notice is preserved and that due credit is given
* to the University of Michigan at Ann Arbor. The name of the University
* may not be used to endorse or promote products derived from this
* software without specific prior written permission. This software
* is provided ``as is'' without express or implied warranty.
*/
#ifndef _LDAP_H
#define _LDAP_H
#include ldap_cdefs.h
LDAP_BEGIN_DECL
#define LDAP_PORT 389
#define LDAP_VERSION1 1
#define LDAP_VERSION2 2
#define LDAP_VERSIONLDAP_VERSION2
#define LDAP_COMPAT20
#define LDAP_COMPAT30
#if defined(LDAP_COMPAT20) || defined(LDAP_COMPAT30)
#define LDAP_COMPAT
#endif
#define LDAP_MAX_ATTR_LEN 100
/* debugging stuff */
extern int ldap_debug; /* always available */
#ifdef LDAP_DEBUG
#ifdef LDAP_SYSLOG
extern int ldap_syslog;
extern int ldap_syslog_level;
#endif /* LDAP_SYSLOG */
#define LDAP_DEBUG_TRACE0x001
#define LDAP_DEBUG_PACKETS 0x002
#define LDAP_DEBUG_ARGS 0x004
#define LDAP_DEBUG_CONNS0x008
#define LDAP_DEBUG_BER 0x010
#define LDAP_DEBUG_FILTER 0x020
#define LDAP_DEBUG_CONFIG 0x040
#define LDAP_DEBUG_ACL 0x080
#define LDAP_DEBUG_STATS0x100
#define LDAP_DEBUG_STATS2 0x200
#define LDAP_DEBUG_SHELL0x400
#define LDAP_DEBUG_PARSE0x800
#define LDAP_DEBUG_ANY 0x
/* this doesn't below as part of ldap.h */
#ifdef LDAP_SYSLOG
#define Debug( level, fmt, arg1, arg2, arg3 ) \
{ \
if ( ldap_debug (level) ) \
fprintf( stderr, (fmt), (arg1), (arg2), (arg3) ); \
if ( ldap_syslog level ) \
syslog( ldap_syslog_level, (fmt), (arg1), (arg2), (arg3) ); \
}
#else /* LDAP_SYSLOG */
#ifndef WINSOCK
#define Debug( level, fmt, arg1, arg2, arg3 ) \
if ( ldap_debug (level) ) \
fprintf( stderr, (fmt), (arg1), (arg2), (arg3) );
#else /* !WINSOCK */
extern void Debug( int level, char* fmt, ... );
#endif /* !WINSOCK */
#endif /* LDAP_SYSLOG */
#else /* LDAP_DEBUG */
#define Debug( level, fmt, arg1, arg2, arg3 )
#endif /* LDAP_DEBUG */
/*
* specific LDAP instantiations of BER types we know about
*/
/* general stuff */
#define LDAP_TAG_MESSAGE0x30L /* tag is 16 + constructed bit */
#define OLD_LDAP_TAG_MESSAGE0x10L /* forgot the constructed bit */
#define LDAP_TAG_MSGID 0x02L
/* possible operations a client can invoke */
#define LDAP_REQ_BIND 0x60L /* application + constructed */
#define LDAP_REQ_UNBIND 0x42L /* application + primitive */
#define LDAP_REQ_SEARCH 0x63L /* application + constructed */
#define LDAP_REQ_MODIFY 0x66L /* application + constructed */
#define LDAP_REQ_ADD0x68L /* application + constructed */
#define LDAP_REQ_DELETE 0x4aL /* application + primitive */
#define LDAP_REQ_MODRDN 0x6cL /* application + constructed */
#define LDAP_REQ_COMPARE0x6eL /* application + constructed */
#define LDAP_REQ_ABANDON0x50L /* application + primitive */
/* version 3.0 compatibility stuff */
#define LDAP_REQ_UNBIND_30 0x62L
#define LDAP_REQ_DELETE_30 0x6aL
#define LDAP_REQ_ABANDON_30 0x70L
/*
* old broken stuff for backwards compatibility - forgot application tag
* and constructed/primitive bit
*/
#define OLD_LDAP_REQ_BIND 0x00L
#define OLD_LDAP_REQ_UNBIND 0x02L
#define OLD_LDAP_REQ_SEARCH 0x03L
#define OLD_LDAP_REQ_MODIFY 0x06L
#define OLD_LDAP_REQ_ADD0x08L
#define OLD_LDAP_REQ_DELETE 0x0aL
#define
Re: how to fcc my gpg/pgp-mails UNencrypted?
Hi Viktor, * Viktor Rosenfeld [EMAIL PROTECTED] [24. Jul. 2002]: David T-G wrote: ...and then Phil Gregory said... % encrypt-to your key ID % % to your ~/.gnupg/options file. This leaves them encrypted on disk but % still allows you to go back and look at them. ... and allows anyone who knows your keyid to know that the message has been encrypted to your key as well, thereby making the message very not-anonymous. Just so you're aware... Hmm, good point. Then again, I almost always sign my messages anyway, so the key id is there in any case. But the idea with a secred, unpublished key is nice. Pgp/gpg first sign then encrypt. So only the repicient can check the sig (after encrypting the message). With gnupg you may even use --throw-keyid Do not put the keyid into encrypted packets. This option hides the receiver of the message and is a countermeasure against traffic analysis. It may slow down the decryption process because all avail- able secret keys are tried. So it is possible to send messages encrypted, signed and anonymously. Ciao, Gregor -- The future is here. It's just not widely distributed yet. -- William Gibson
X-Mailer Header Not Being Picked Up With Resend Command
When I resend a message, using esc e, I find that my X-Mailer header is not picked up from the original message. The manual indicates that weeding is used when resending. My .muttrc contains: ignore unignorefrom: subject to cc mail-followup-to \ date x-mailer x-url weed in not set, so should default to yes, per the manual. What obvious thing am I missing? TIA John
gpg-decryption produces ^Ms
Hello Mutt-users, a friend of mine uses Outlook :-( in order to write me encrypted GnuPG E-Mails... -BEGIN PGP MESSAGE- Version: GnuPG v1.0.6 (MingW32) - GPGOE 0.4.1 [...] Everytime (after pressing ESC-P) i get the decrypted mail with ^Ms at the end of each line (carriage return?). When i decode the E-Mail manually via bash the output is as right as a trivet. What can I do against that behaviour? I'm using Mutt 1.4i with the following decrypt-setting: set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f -- Cheers, Heiko Heil
Re: 1.0.7 ldap problems
Kirill Miazine [Wed, Jul 24, 2002 at 02:16:11PM +0200]: You sent this to the wrong list, no? 1.0.7 looks like a GnuPG version. sorry guys! I was so tired...Definitly choosed the wrong list! Still have a nice day! Nico -- Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt mails to mailing list!). If you don't know what pgp is visit www.gnupg.org. (public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key) msg29843/pgp0.pgp Description: PGP signature
how does simple commenting work
Now I spent a whole day in searching all my .vim files, reading all through the :help stuff and used my mailarchive to get a clue - either I am missing simply a part of the whole puzzle or I am just too insert whatever to understand. Supposed I have a text which may begin with [ \t]+ blahblah blahblah and I need to define a special comment marker like note1 blahblah note1 no blahblah note1 use blub instead blahblah and further I want this comment marker to be auto-inserted whenever I do enter, what parts would I need for this? The whole stuff works with mail just on its own, but I cannot find out what it is that makes it work. I have not auto- insert and gq also does not work like it should. Any help appreciated. -- Erika Pacholleck [EMAIL PROTECTED] mutters: insert vowels of last name
Re: gpg-decryption produces ^Ms
On Wed, Jul 24, 2002 at 05:08:09PM +0200, Heiko Heil wrote: Hello Mutt-users, a friend of mine uses Outlook :-( in order to write me encrypted GnuPG E-Mails... a common problem. i have it as well and have, as yet, been unable to solve it. :-) Everytime (after pressing ESC-P) i get the decrypted mail with ^Ms at the end of each line (carriage return?). When i decode the E-Mail manually via bash the output is as right as a trivet. i think that you are probably getting the ^M's in both cases but mutt's pager decides to show them to you but the bash method doesn't. try decrypting it from a shell and save it to a file, then use vim to look at it and see if there are ^M's or not. What can I do against that behaviour? out of curiosity, why do you care? you could send it through sed or use dos2unix or some such. set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f for example (untested): set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f | sed 's/^M//' -- Peter Abplanalp Email: [EMAIL PROTECTED] PGP: pgp.mit.edu msg29845/pgp0.pgp Description: PGP signature
Re: how does simple commenting work
Under :help comments there is this:
'comments' 'com'string (default s1:/*,mb:*,ex:*/,://,b:#,:%,:XCOMM,n:,fb:-)
local to buffer
{not in Vi}
{not available when compiled without the
|+comments|
feature}
A comma separated list of strings that can start a comment line.
See |format-comments|. See |option-backslash| about using
backslashes to insert a space.
If you have access to Steve Oualline's Book in Vim, he goes through
examples of using the comments option to define what is a comment. He
gives an example:
s1:/*,mb:*,ex:*/
and says of it:
The s1 command indicates that this is the start of a three-part comment
(s) and the other lines in the command need to be indented an extra
space (1). The comment starts with the string /*.
The middle of the comment is defined by the mb:* part. The m indicates
a middle piece, and the b says that a blank must follow anything that is
inserted. The text that begins the comment is *.
The ending is specified by ex:*/. The e indicates the end, and the x
indicates that you have only to type the last character of the ending to
finish the comment. The end delimiter is */. (Oualline, page 271).
I have not worked with this feature, but hope this reference is helpful.
John
On 07/24/02 16:23 +0200, Erika Pacholleck wrote:
Now I spent a whole day in searching all my .vim files,
reading all through the :help stuff and used my mailarchive
to get a clue - either I am missing simply a part of the
whole puzzle or I am just too insert whatever to understand.
Supposed I have a text which may begin with [ \t]+
blahblah
blahblah
and I need to define a special comment marker like note1
blahblah
note1 no blahblah
note1 use blub instead
blahblah
and further I want this comment marker to be auto-inserted
whenever I do enter, what parts would I need for this?
The whole stuff works with mail just on its own, but I cannot
find out what it is that makes it work. I have not auto-
insert and gq also does not work like it should.
Any help appreciated.
--
Erika Pacholleck [EMAIL PROTECTED]
mutters: insert vowels of last name
Re: how to fcc my gpg/pgp-mails UNencrypted?
Hi Viktor and Rocco, Viktor wrote: can't help you with your question, however, I always encrypt messages with the recipient's key and with my own key. Yep, that's how I do it, too. :-) This way, the encrypted messages is stored in my fcc folder, but I'm still able to read it, because it's encrypted with my own key. ...until you switch from gpg to ?? in a few years or revoke your key. That's what I'm fearing a little bit. Besides sometime I like to grep through my mailbox files which doesn't work (easily) when they're encrypted. Rocco wrote: Sounds like you're looking for ``set fcc_clear''. That's it, yes! Thanks a lot. Although I wouldn't mind if mutt saves with signatures, but I suppose that's how close I can get without patching mutt myself. Thanks for your help, Andy. -- http://peru.spiegl.de Our project http://radiomaranon.org.pe Radio Marañón, Jaén, Perú o _ _ _ --- __o __o /\_ _ \\o (_)\__/o (_) -o) - _`\,__`\,__(_) (_)/_\_| \ _|/' \/ /\\ (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o__\_v If cats and dogs didn't have fur would we still pet them? msg29847/pgp0.pgp Description: PGP signature
Re: gpg-decryption produces ^Ms
Hi, * Peter T. Abplanalp [02-07-24 19:55:29 +0200] wrote: for example (untested): set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f | sed 's/^M//' (sed 's/ $//' is much better) Hmm, what happens with signed and encrypted mail? If GnuPG does decryption and verification at once it may be sucessfull, if not then not. IMHO the more better solution is (untested): set display_filter=sed s/ $// This will only manipulate what you see and not the body. If your example was used I guess you'll run into trouble when formarding mail (or do something else with it). bye, Rocco
Re: gpg-decryption produces ^Ms
On Wed, Jul 24, 2002 at 08:05:01PM +0200, Rocco Rutte wrote: Hi, * Peter T. Abplanalp [02-07-24 19:55:29 +0200] wrote: for example (untested): set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f | sed 's/^M//' (sed 's/ $//' is much better) you are, of course, correct. Hmm, what happens with signed and encrypted mail? If GnuPG does decryption and verification at once it may be sucessfull, if not then not. IMHO the more better solution is (untested): set display_filter=sed s/ $// This will only manipulate what you see and not the body. If your example was used I guess you'll run into trouble when formarding mail (or do something else with it). heck, i don't know. it all depends on why he wants to remove the ^M's. -- Peter Abplanalp Email: [EMAIL PROTECTED] PGP: pgp.mit.edu msg29849/pgp0.pgp Description: PGP signature
View OpenOffice Documents inline
Does anyone know a tool to view the text parts of StarOffice/OpenOffice documents? I finally convinced my windows buddies to switch from MickySoft, but now my mutt-setup is incomplete. :-) Thanks, Andy. -- http://peru.spiegl.de Our project http://radiomaranon.org.pe Radio Marañón, Jaén, Perú o _ _ _ --- __o __o /\_ _ \\o (_)\__/o (_) -o) - _`\,__`\,__(_) (_)/_\_| \ _|/' \/ /\\ (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o__\_v Love, not time, heals all wounds.
Re: gpg-decryption produces ^Ms
On Wed, Jul 24, 2002 at 11:01:44AM -0600, Peter T. Abplanalp wrote: [...] for example (untested): set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f | sed 's/^M//' Nice idea! I've tried this before, but my attempts were without success... The principal fault was that i have changed the pgp_decrypt_command and not the pgp_decode_command. Now it works. tested: set pgp_decode_command=gpg %?p?--passphrase-fd 0? --no-verbose \ --batch --output - %f | sed 's/\r//' -- Cheers, Heiko Heil msg29851/pgp0.pgp Description: PGP signature
Re: how does simple commenting work
* Erika Pacholleck [EMAIL PROTECTED] [2002-07-24 15:33]: Suppose I have a text which may begin with [ \t]+ blahblah blahblah and I need to define a special comment marker like note1 blahblah note1 no blahblah note1 use blub instead blahblah and further I want this comment marker to be auto-inserted whenever I do enter, what parts would I need for this? set comments+=note1 set formatoptions+=r - :help fo-table The whole stuff works with mail just on its own, but I cannot find out what it is that makes it work. I have not autoinsert and gq also does not work like it should. for whatever definition of should... Any help appreciated. -- Erika Pacholleck [EMAIL PROTECTED] mutters: insert vowels of last name no fsking way! welcome to my killfile. *plonk* Sven [no remorse for anti-spam losers!]
Re: X-Mailer Header Not Being Picked Up With Resend Command
* John P Verel [EMAIL PROTECTED] [2002-07-24 14:54]: When I resend a message, using esc e, I find that my X-Mailer header is not picked up from the original message. The manual indicates that weeding is used when resending. .. What obvious thing am I missing? resending takes the message as is. no hooks or whatever get applied. feature. period. Sven
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 21:12 +0200, Sven Guckes wrote: resending takes the message as is. no hooks or whatever get applied. feature. period. Not to be difficult, but to quote the on-line manual: 'With resend-message, mutt takes the current message as a template for a new message. This function is best described as recall from arbitrary folders. It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. John
Re: X-Mailer Header Not Being Picked Up With Resend Command
John P Verel ([EMAIL PROTECTED]) muttered: 'With resend-message, mutt takes the current message as a template for a new message. This function is best described as recall from arbitrary folders. It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. I seem to recall a previous discussion on this topic. Please grep the archives for further details. To summarize: Mutt will delete any X-Mailer header. HTH, Michael -- PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: X-Mailer Header Not Being Picked Up With Resend Command
* John P Verel [EMAIL PROTECTED] [2002-07-24 20:03]: On 07/24/02 21:12 +0200, Sven Guckes wrote: resending takes the message as is. no hooks or whatever get applied. feature. period. Not to be difficult, but to quote the on-line manual: 'With resend-message.. Note that the amount of headers included here depends on the value of the ``$weed'' variable.' What does the last sentence mean? a valid question! thanks for pointing it out - i did not see this. As the original message had an X-Mailer header included, I took the manual to mean that it would be picked up in the new message. I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) Sven === mutt.testmail From mutt-testers Wed Jul 24 23:22:21 2002 From: Sven Guckes [EMAIL PROTECTED] To: Mutt Users' List [EMAIL PROTECTED] Subject: Re: X-Mailer Header Not Being Picked Up With Resend Command Message-ID: [EMAIL PROTECTED] In-Reply-To: 20020724200253.GB1775@Verdi X-Test: does resend-message weed headers or not?
Re: X-Mailer Header Not Being Picked Up With Resend Command
I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) That does not work with x-mailer sven. Why didn't you test the header in question? Michael -- Whip me. Beat me. Make me maintain AIX. (By Stephan Zielinski) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: how does simple commenting work
Hi, * Sven Guckes [02-07-24 21:28:34 +0200] wrote: * Erika Pacholleck [EMAIL PROTECTED] [2002-07-24 15:33]: Any help appreciated. -- Erika Pacholleck [EMAIL PROTECTED] mutters: insert vowels of last name no fsking way! welcome to my killfile. *plonk* Wow, this mail has to go to my special archive. A plonk on a mailing list... bye, Rocco [who never saw it before...]
Re: gpg-decryption produces ^Ms
Hi, * Peter T. Abplanalp [02-07-24 21:28:27 +0200] wrote: heck, i don't know. it all depends on why he wants to remove the ^M's. I guess most likely because it looks ugly... Another solution could be trying to color it out (with the internal pager). bye, Rocco
Re: X-Mailer Header Not Being Picked Up With Resend Command
* Michael Tatge [EMAIL PROTECTED] [2002-07-24 20:45]: I assume that if you do no specifically unignore X-* lines then they will be weeded out. let's test this: $ mutt -f mutt.testmail :unignore x- resend-message bingo - X-Test: line *included*! :-) That does not work with x-mailer sven. Why didn't you test the header in question? because it should be self-evident that mutt will not send with an identification other than the one it adds itself. that's why. you can complain to the developers for not documenting their code enough on this point, of course. Sven [off to see a sneak preview]
Re: X-Mailer Header Not Being Picked Up With Resend Command
On 07/24/02 22:11 +0200, Michael Tatge wrote: To summarize: Mutt will delete any X-Mailer header. Confirmed. Thanks.
