| 1 | FREQUENTLY ASKED QUESTIONS |
1 | FREQUENTLY ASKED QUESTIONS |
|
|
2 | I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
3 | change/disable it? |
|
|
4 | You can disable the perl extension completely by setting the |
|
|
5 | perl-ext-common resource to the empty string, which also keeps |
|
|
6 | rxvt-unicode from initialising perl, saving memory. |
|
|
7 | |
|
|
8 | If you only want to disable specific features, you first have to |
|
|
9 | identify which perl extension is responsible. For this, read the |
|
|
10 | section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For |
|
|
11 | example, to disable the selection-popup and option-popup, specify |
|
|
12 | this perl-ext-common resource: |
|
|
13 | |
|
|
14 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
15 | |
|
|
16 | This will keep the default extensions, but disable the two popup |
|
|
17 | extensions. Some extensions can also be configured, for example, |
|
|
18 | scrollback search mode is triggered by M-s. You can move it to any |
|
|
19 | other combination either by setting the searchable-scrollback |
|
|
20 | resource: |
|
|
21 | |
|
|
22 | URxvt.searchable-scrollback: CM-s |
|
|
23 | |
| 2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
24 | Isn't rxvt supposed to be small? Don't all those features bloat? |
| 3 | I often get asked about this, and I think, no, they didn't cause |
25 | I often get asked about this, and I think, no, they didn't cause |
| 4 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
26 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
| 5 | can see that the urxvt binary is larger (due to some encoding tables |
27 | can see that the urxvt binary is larger (due to some encoding tables |
| 6 | always being compiled in), but it actually uses less memory (RSS) |
28 | always being compiled in), but it actually uses less memory (RSS) |
| … | |
… | |
| 127 | |
149 | |
| 128 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
150 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 129 | safe? |
151 | safe? |
| 130 | Likely not. While I honestly try to make it secure, and am probably |
152 | 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 |
153 | not bad at it, I think it is simply unreasonable to expect all of |
| 132 | freetype + fontconfig + xft + xlib + ... + rxvt-unicode itself to |
154 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
| 133 | all be secure. Also, rxvt-unicode disables some options when it |
155 | itself to all be secure. Also, rxvt-unicode disables some options |
| 134 | detects that it runs setuid or setgid, which is not nice. |
156 | when it detects that it runs setuid or setgid, which is not nice. |
|
|
157 | Besides, with the embedded perl interpreter the possibility for |
|
|
158 | security problems easily multiplies. |
| 135 | |
159 | |
| 136 | Elevated privileges are only required for utmp and pty operations on |
160 | Elevated privileges are only required for utmp and pty operations on |
| 137 | some systems (for example, GNU/Linux doesn't need any extra |
161 | some systems (for example, GNU/Linux doesn't need any extra |
| 138 | privileges for ptys, but some need it for utmp support). If |
162 | privileges for ptys, but some need it for utmp support). It is |
| 139 | rxvt-unicode doesn't support the library/setuid helper that your OS |
163 | planned to mvoe this into a forked handler process, but this is not |
| 140 | needs I'll be happy to assist you in implementing support for it. |
164 | yet done. |
| 141 | |
165 | |
| 142 | So, while setuid/setgid operation is supported and not a problem on |
166 | So, while setuid/setgid operation is supported and not a problem on |
| 143 | your typical single-user-no-other-logins unix desktop, always |
167 | 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 |
168 | remember that its an awful lot of code, most of which isn't checked |
| 145 | for security issues regularly. |
169 | for security issues regularly. |
