| … | |
… | |
| 100 | |
100 | |
| 101 | For other problems that also affect the Debian package, you can and |
101 | For other problems that also affect the Debian package, you can and |
| 102 | probably should use the Debian BTS, too, because, after all, it's |
102 | probably should use the Debian BTS, too, because, after all, it's |
| 103 | also a bug in the Debian version and it serves as a reminder for |
103 | also a bug in the Debian version and it serves as a reminder for |
| 104 | other users that might encounter the same issue. |
104 | other users that might encounter the same issue. |
|
|
105 | |
|
|
106 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
|
|
107 | recommendation? |
|
|
108 | You should build one binary with the default options. configure now |
|
|
109 | enables most useful options, and the trend goes to making them |
|
|
110 | runtime-switchable, too, so there is usually no drawback to enbaling |
|
|
111 | them, except higher disk and possibly memory usage. The perl |
|
|
112 | interpreter should be enabled, as important functionality (menus, |
|
|
113 | selection, likely more in the future) depends on it. |
|
|
114 | |
|
|
115 | You should not overwrite the "perl-ext-common" snd "perl-ext" |
|
|
116 | resources system-wide (except maybe with "defaults"). This will |
|
|
117 | result in useful behaviour. If your distribution aims at low memory, |
|
|
118 | add an empty "perl-ext-common" resource to the app-defaults file. |
|
|
119 | This will keep the perl interpreter disabled until the user enables |
|
|
120 | it. |
|
|
121 | |
|
|
122 | If you can/want build more binaries, I recommend building a minimal |
|
|
123 | one with "--disable-everything" (very useful) and a maximal one with |
|
|
124 | "--enable-everything" (less useful, it will be very big due to a lot |
|
|
125 | of encodings built-in that increase download times and are rarely |
|
|
126 | used). |
|
|
127 | |
|
|
128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
|
|
129 | safe? |
|
|
130 | Likely not. While I honestly try to make it secure, and am probably |
|
|
131 | not bad at it, I think it is simply unreasonable to expect all of |
|
|
132 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
|
|
133 | all be secure. Also, rxvt-unicode disables some options when it |
|
|
134 | detects that it runs setuid or setgid, which is not nice. |
|
|
135 | |
|
|
136 | Elevated privileges are only required for utmp and pty operations on |
|
|
137 | some systems (for example, GNU/Linux doesn't need any extra |
|
|
138 | privileges for ptys, but some need it for utmp support). If |
|
|
139 | rxvt-unicode doesn't support the library/setuid helper that your OS |
|
|
140 | needs I'll be happy to assist you in implementing support for it. |
|
|
141 | |
|
|
142 | So, while setuid/setgid operation is supported and not a problem on |
|
|
143 | your typical single-user-no-other-logins unix desktop, always |
|
|
144 | remember that its an awful lot of code, most of which isn't checked |
|
|
145 | for security issues regularly. |
| 105 | |
146 | |
| 106 | When I log-in to another system it tells me about missing terminfo data? |
147 | When I log-in to another system it tells me about missing terminfo data? |
| 107 | The terminal description used by rxvt-unicode is not as widely |
148 | The terminal description used by rxvt-unicode is not as widely |
| 108 | available as that for xterm, or even rxvt (for which the same |
149 | available as that for xterm, or even rxvt (for which the same |
| 109 | problem often arises). |
150 | problem often arises). |
