ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.35 by root, Sat Jan 7 04:19:43 2006 UTC vs.
Revision 1.36 by root, Mon Jan 9 01:54:43 2006 UTC

206<dd> 206<dd>
207<p>For other problems that also affect the Debian package, you can and 207<p>For other problems that also affect the Debian package, you can and
208probably should use the Debian BTS, too, because, after all, it's also a 208probably should use the Debian BTS, too, because, after all, it's also a
209bug in the Debian version and it serves as a reminder for other users that 209bug in the Debian version and it serves as a reminder for other users that
210might encounter the same issue.</p> 210might encounter the same issue.</p>
211</dd>
212<p></p>
213<dt><strong><a name="item_i_am_maintaining_rxvt_2dunicode_for_distribution_2">I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?</a></strong><br />
214</dt>
215<dd>
216You should build one binary with the default options. <em>configure</em>
217now enables most useful options, and the trend goes to making them
218runtime-switchable, too, so there is usually no drawback to enbaling them,
219except higher disk and possibly memory usage. The perl interpreter should
220be enabled, as important functionality (menus, selection, likely more in
221the future) depends on it.
222</dd>
223<dd>
224<p>You should not overwrite the <code>perl-ext-common</code> snd <code>perl-ext</code> resources
225system-wide (except maybe with <code>defaults</code>). This will result in useful
226behaviour. If your distribution aims at low memory, add an empty
227<code>perl-ext-common</code> resource to the app-defaults file. This will keep the
228perl interpreter disabled until the user enables it.</p>
229</dd>
230<dd>
231<p>If you can/want build more binaries, I recommend building a minimal
232one with <code>--disable-everything</code> (very useful) and a maximal one with
233<a href="#item__2d_2denable_2deverything"><code>--enable-everything</code></a> (less useful, it will be very big due to a lot of
234encodings built-in that increase download times and are rarely used).</p>
235</dd>
236<p></p>
237<dt><strong><a name="item_i_need_to_make_it_setuid_2fsetgid_to_support_utmp_">I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?</a></strong><br />
238</dt>
239<dd>
240Likely not. While I honestly try to make it secure, and am probably
241not bad at it, I think it is simply unreasonable to expect all of
242freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to all be
243secure. Also, rxvt-unicode disables some options when it detects that it
244runs setuid or setgid, which is not nice.
245</dd>
246<dd>
247<p>Elevated privileges are only required for utmp and pty operations on some
248systems (for example, GNU/Linux doesn't need any extra privileges for
249ptys, but some need it for utmp support). If rxvt-unicode doesn't support
250the library/setuid helper that your OS needs I'll be happy to assist you
251in implementing support for it.</p>
252</dd>
253<dd>
254<p>So, while setuid/setgid operation is supported and not a problem on your
255typical single-user-no-other-logins unix desktop, always remember that
256its an awful lot of code, most of which isn't checked for security issues
257regularly.</p>
211</dd> 258</dd>
212<p></p> 259<p></p>
213<dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br /> 260<dt><strong><a name="item_when_i_log_2din_to_another_system_it_tells_me_abou">When I log-in to another system it tells me about missing terminfo data?</a></strong><br />
214</dt> 261</dt>
215<dd> 262<dd>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines