Gentoo Archives: gentoo-dev

From: Mauricio Lima PIlla <pilla@××××××××××.br>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Abuse by gentoo developer
Date: Wed, 20 Jul 2005 01:45:58
Message-Id: 1121823686.10908.8.camel@localhost
In Reply to: [gentoo-dev] Abuse by gentoo developer by Casey Allen Shobe
1 http://www.gentoo.org/proj/en/devrel/policy.xml
2
3 "Developer relations should only be involved in a conflict when other
4 attempts to solve the issue have failed. Developers should attempt
5 polite discussion relating to the matter at hand to resolve conflict
6 between themselves. Developers within a single top level project (TLP)
7 engaged in conflict may wish to consult with the TLP manager. Although
8 TLP managers are not necessarily qualified to resolve personal disputes,
9 technical issues resulting in conflict can often be resolved within the
10 TLP without developer relations involvement. Personal issues should be
11 brought to the ombudsman via ombudsman@g.o. Developer relations
12 may get involved when the above methods have failed. For resolution of
13 technical conflicts spanning more than one TLP, see the section entitled
14 'Presenting information to management.'"
15
16
17 On Qua, 2005-07-20 at 01:32 +0000, Casey Allen Shobe wrote:
18 > Hello all, I'm sorry to bring this here, but I don't know where else
19 > to take it, and feel that I was treated really unfairly.
20 >
21 > As you know, I recently inquired about ebuild development on this
22 > list, and mentioned vpopmail. Jory Pratt answered my mail and
23 > suggested that I submit a patch.
24 >
25 > I then spent some time working on the ebuild, and in doing so,
26 > discovered that the postgres support in vpopmail was not very good
27 > at all, so I wrote back to Jory, and said that I was going to hold
28 > off working on the ebuild since I am currently working with the
29 > vpopmail team to improve vpopmail itself. Jory wrote this rather
30 > rude reply:
31 >
32 > -------------------
33 > Casey Allen Shobe wrote:
34 > > Well I patched the ebuild and got it working, but I'm so terribly
35 > > disappointed with vpopmail's horrible postgresql support that I
36 > > don't think I'll be using it at all until I rewrite it. :P
37 > >
38 > > Ah well, thanks anyways. I'll let you know when/if they let me
39 > > fix vpopmail (already posted about it on the list).
40 >
41 > The will not allow it and I will not allow someone to go fooling in
42 > an ebuild I maintain. Not trying to be an ass here but we have
43 > something called respect for others when it comes to the tree and
44 > what they maintain.
45 > >
46 > > One suggestion for you, some servers (i.e. qmail-smptd) runs as a
47 > > non-root user, so they will fail to authenticate
48 > > unless /var/vpopmail/bin/vchkpw is SUID. I have a script that
49 > > runs once a minute on my machines and makes this file +s if it's
50 > > not because I've dealt with this problem so much (mail server
51 > > breaks every time I rebuild vpopmail).
52 >
53 > Default install is setup as setuid seeing we know this already.
54 > Useless info like this tells me you do not understand the
55 > permissions that are being set in the ebuild.
56 > >
57 > > I would strongly recommend doing chmod +s /var/vpopmail/bin/vchkpw
58 > > in the ebuild, and then if the end user doesn't want it SUID, then
59 > > that's what FEATURES=suidctl is for.
60 >
61 > This is not how we can handle this the user should have already read
62 > up on how to setup vpopmail before ever installing it, which means
63 > they would already know that SUID is required.
64 > -------------------
65 >
66 > So, I wrote the following response, which I feel was courteous
67 > enough given the situation:
68 >
69 > -------------------
70 > On Tuesday 19 July 2005 16:09, you wrote:
71 > > The will not allow it and I will not allow someone to go fooling
72 > > in an ebuild I maintain. Not trying to be an ass here but we have
73 > > something called respect for others when it comes to the tree and
74 > > what they maintain.
75 >
76 > Umm look, you ARE being an ass, and I don't appreciate it as I'm
77 > only trying to help.
78 >
79 > A> I was simply offering you help - adding support for a postgres
80 > use flag to the ebuild that called appropriate configure options
81 > and such. I have no intent of hacking up vpopmail source outside
82 > of the main distribution.
83 >
84 > B> You are not one to say whether the vpopmail team will or will not
85 > accept my patches - I believe they will as my intent is to make
86 > vpopmail a better product, and members of their development team
87 > have already been welcoming and helpful in discussing the best way
88 > to redesign things. It's no secret to the vpopmail team that the
89 > postgresql support is lacking flexibility and has some bugs, and is
90 > simply hacked together quickly by people who wanted it to work, and
91 > didn't care much for ease of use or configurability. Try it
92 > yourself, I'm sure you'll be disappointed. It's simply not as
93 > configurable as the mysql option, and neither mysql or postgresql
94 > allow customizing the backend table format without editing i.e.
95 > vpgsql.h for postgres.
96 >
97 > > Default install is setup as setuid seeing we know this already.
98 > > Useless info like this tells me you do not understand the
99 > > permissions that are being set in the ebuild.
100 >
101 > Umm, no it's not, and it's not useless info. I reported the bug to
102 > the gentoo-dev list some months ago, but should have probably used
103 > bugs.gentoo.org instead. In any case, it's certainly not installed
104 > setuid by default:
105 >
106 > # emerge -va vpopmail && ls -l /var/vpopmail/bin/vchkpw
107 >
108 > These are the packages that I would merge, in order:
109 >
110 > Calculating dependencies ...done!
111 > [ebuild R ] net-mail/vpopmail-5.4.6-r1 +clearpasswd -ipalias
112 > -mysql -postgres 0 kB [1]
113 > [...]
114 > >>> net-mail/vpopmail-5.4.6-r1 merged.
115 > [...]
116 > -rwx--x--x 1 root root 85036 Jul 19 23:53 /var/vpopmail/bin/vchkpw*
117 >
118 > So stop telling me my info is useless, when it's obviously not.
119 >
120 > > This is not how we can handle this the user should have already
121 > > read up on how to setup vpopmail before ever installing it, which
122 > > means they would already know that SUID is required.
123 >
124 > As SUID is required for qmail-smtpd, vchkpw should indeed be
125 > installed SUID by default unless overridden by using suidctl. This
126 > is NOT the case now.
127 > -------------------
128 >
129 > I then received this lovely mail from Jory:
130 >
131 > -------------------
132 > You want to curse me and tell me you think your gonna go playing in
133 > my vpopmail ebuild you can take your bullshit upstream I am black
134 > listing you on my filters so I do not need to read your bullshit
135 > you do not understand the full picture if you did you would know
136 > vpopmail works with more then just qmail you dumb ass. So have a
137 > nice Day chow!!
138 > -------------------
139 >
140 > Umm look I'm just trying to help here, and I really feel like I've
141 > been treated very unfairly by this developer. I'm working hard to
142 > try to make vpopmail AND gentoo better products, I'd really
143 > appreciate not being told on things I know very well that I'm right
144 > about, and getting severe reactions like this when I prove that my
145 > statements were indeed correct and that I'm only trying to help.
146 >
147 > I really feel that this response whas wholly unjustified, and that I
148 > did nothing to warrant it. Please advise.
149 >
150 > Cheers,
151 > --
152 > Casey Allen Shobe | http://casey.shobe.info
153 > cshobe@×××××××××××××.com | cell 425-443-4653
154 > AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
155 > SeattleServer.com, Inc. | http://www.seattleserver.com
156 --
157 Mauricio Lima Pilla pilla@××××××××××.br
158 ESIN/UCPEL
159 http://g3pd.ucpel.tche.br/~pilla
160
161 "I'm just very selective about the reality I choose to accept."
162 -- Calvin
163
164 --
165 gentoo-dev@g.o mailing list