Palace Plugins
| Alternate Names |
| AltNames 1.0 README ---------------------------------- AltNames is a Palace Server plugin that permits all users to include additional character map characters ("alt codes") in their name that were previously not allowed with the regular Palace Client software. It was developed by Martyn Gilbertson. Questions about this plugin? Write to Martyn at plugins@palacebox.com or Joseph Rock at joe@avatarpalace.net. Copyright (c) 2003 Martyn Gilbertson. All Rights Reserved Worldwide. Installation AltNames is a standard Palace server plugin. It is installed by placing the plugin file, altnames.so, in the Palace binary folder, /usr/local/palace/bin, and adding the following line to the plugin configuration file, /usr/local/palace/<palace-name>/psdata/plugin.conf /bin/altnames.so Notes |
 |
| Author Block |
AuthorBlock Version 0.3 README AuthorBlock was developed by Mike Wentzell (dotslashmike@hotmail.com). Installation plugins/authorblock.so
|
|
| Away |
Away 1.0.0 README Questions about this plugin? Write to the plugin devolper at plugins@all4palace.com Installation /plugins/away.so Commands
|
|
| Bad Boy 101 |
BadBoy 1.0.1 README Questions about this plugin? Write to the plugin devolper at plugins@all4palace.com Installation BadBoy is a standard Palace server plugin. It is installed by
placing the plugin badboy.so, in the Palace binary folder, /bin/badboy/badboy.so psdata/badboy.list roomid The badboy list file is created in /usr/local/palace/<palace-name>/psdata. Note that badboy reads and writes to this file. Therefore, it cannot be edited. The roomid is the roomid for which the user will be sent to. God Commands `badboy help - display this message. ChangeLog
|
|
| Crash Block |
CrashBlock 1.4 README bin/chrashblock.so Changes in Version 1.4 Changes in Version 1.3 Changes in Version 1.1 Changes in Version 1.0
|
|
| GateKeeper Pro |
GateKeeper Pro 1.0.0 README Questions about this plugin? Write to the plugin devolper at plugins@all4palace.comCopyright (c) 2004 Martyn Gilbertson. All Rights Reserved Worldwide. Installation GateKeeper is a standard Palace server plugin. It is installed by placing the plugin gatekeeper.so, in the Palace binary folder /usr/local/palace/bin, and adding the following line to the plugin configuration file: /usr/local/palace/<palace-name>/psdata/plugin.conf /bin/gatekeeper/gatekeeper.so psdata/gatekeeper.list The gatekeeper list file is created in /usr/local/palace/<palace-name>/psdata. God Commands 'gatekeeper bless [password] [wiz/god/owner] <[reghash] [name]>/[whisper] - bless a user. Ranks are
|
|
| Gate Logon |
GateLogon Version 0.1 README Installation Gatelogon is a standard Palace server plugin. It is installed by placing the plugin file, gatelogon.so, in the palace binary folder /usr/local/palace/bin, and adding the following line to the plugin configuration file, /usr/local/palace/<palace-name>/psdata/plugin.conf /bin/gatelogon.so
|
|
| Guardian |
Preface Guardain is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. The Guardian plugin and plugin source is distributed in the hope that it will be useful; but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should be able to get a copy of the GNU General Public License at: Version 2.5.32 Version 2.4.26 Version 2.3.23 Version 2.2.17 Version 2.1.14 Version 2.0.10 Version 1.4.5 Version 1.3.4 Version 1.2.3 Version 1.1.2 Version 1.0.1 -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Unique Aliases (commands that do the equivalent to another command.): Arguments Arguments -------------------------------------------------------------------------------- In Guardian, it's different. Guardian takes security a step higher by verifying people by their Registration Code (or hash), by their PUID (or Z-Code) AND by their IP address. Using all 3 of these methods to validate a user would make it almost impossible to crack wizard access. But wait, there's more! Not only do you bless people with so much criteria, but you also are allowed to give each person you bless their own password to "wiz up" with. The basic syntax of the command (from the servers help command) -------------------------------------------------------------------------------- Usually to execute a command you simply need to type a backtick or apostrophe and then the name of the command, and then the enter key. For instance, to list all users in a Palace you'd type: But a fair amount of commands in this server plugin require or can accept information that alters the way they behave or provides information to be processed: Flags are the options that will alter the behavior of the program. They are usually preceded with a dash. If you wanted to bless someone by both their PUID and Registration Code; you could mix the flags together. Now comes in the arguments, an example of this would be `bless wizard password -i <arguments> If I wanted to bless the person with the IP 24.643.82.3 and PUID / RegHash verification, I could do If this is too much for you; you can just whisper `bless <group> <password> to a user without any "flags" and it'll by default bless them by Registration Code (like the original GateKeeper.) You will need to know how to use flags in order to unbless users and do other things throughout the plugin, however, so I'd suggest you learn now! -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- An example of this usage would be the IP address with a wildcard: This example would match any IP with the last part being anything. Meaning only the first 3 parts would have to match. An IP that would not pass this filter would be -------------------------------------------------------------------------------- An example of this usage would be the IP address with a range, such as: IP's that would be allowed through this filter would only include: An IP that would not pass this filter would be -------------------------------------------------------------------------------- The basic syntax of the `unbless Command is: Remember those dreaded Command Flags that we learned in the previous chapter? They come in handy here too! There is several ways you could use this command to unbless someone. The constant that never changes about the unbless command however, is you have to declare which group the person you wish to unbless is in. We'll underline each one of these below: The first way would be to put the reg code of the user you wish to unbless. Let's say I want to unbless Bob and he's in a group called "scripter" and his reg code is HODDCCBEF. I could unbless him by typing: Or, I could use his PUID and unbless him by that, if his PUID was ZHMBBMHIF I'd do: Finally, I could unbless someone by their IP if their IP in the Guardian Bless List was 24.*.212.65 I hope this is simple enough? Let's move on... -------------------------------------------------------------------------------- However, inevitably people may still forget their password, and since you can't retrieve it for them, the best thing to do would be to change it for them, using a command! That's when the `chpass command was born! The syntax for the command is: This command is very similar to the unbless command described in the section above, because the flags work the exact same way. If I want to change the password for "Jon" and he's in group "Host" and he had a reg code of HOPDOCBOF according to his bless record, I would do: You can also use the -p and -i flags to change the password by their PUID or IP address respectively. An alternative (and probably easier) way to change someone's pass would be to whisper to them without providing any flags. E.G. whispering to "Bob" who is in group "owner" who wants his new pass to be "911" like this: -------------------------------------------------------------------------------- If you're in staff mode, you just simply type `logout Owners/Root can log wizards out by whispering `logout to wizards. NOTE: If you're root you will be unable to log out. This is a security precaution. ALIASES: You can also type `guardian exit -------------------------------------------------------------------------------- `offer - To offer an avatar to anyone (needs to be whispered) As you may see, we also added a new command for staff where a staff member can offer their current avatar to everyone in the current room at once. The command for this is NOTE: You can give the ability of `offerall to everyone if you wish by tweaking your guardian.mod file. -------------------------------------------------------------------------------- NEW!!!You can now only make it show only certain details, apply arguments [<-rpilm>] An example of the output this command would generate would be: ALIASES: You can also type `guardian list -------------------------------------------------------------------------------- An example output is: * The "root" stands for the current group they reside in. ALIASES: You can also type `guardian glist -------------------------------------------------------------------------------- ALIASES: You can also type `guardian group -------------------------------------------------------------------------------- This is useful if you need to change your Palacetools key and don't want to shut the server down in order to do it. The syntax is: The changes take place immediately (The changes WILL be saved to the preferences file on shutdown). -------------------------------------------------------------------------------- An example of this would be clearing my bless list of staff who have neglected to come on in the last 5 days. I would do this by typing: Alternatively you can clear the bless list from staff who haven't signed on by the default of 30 days by typing: NOTE: Users blessed under the "owner" rank will be purged too, so use with care! -------------------------------------------------------------------------------- Modifying the configuration through these commands because you don't feel comfortable doing it manually is NOT why these commands were created. You will -HAVE- to know how the configuration works to modify the way the plugin works through these commands. If you mess up you could easily make it so people cannot sign on your server, and then you'll really have to learn how the plugin works to fix this. Please learn how to modify the configuration file manually before using these commands. -------------------------------------------------------------------------------- This command is used to give a user a specific command. This would be useful if you add a user to a group, but want to give them 1 or 2 extra commands that the group you added them to do not have. Consider if I had a group called punyrank it'd look like this in the guardian.mod file: You have a couple of people in punyrank, all of these people can only do those commands. They can't do anything else. Say you bless someone called 'joeblow' who you want to have puny rank, but additionally to have the ability of a badge or star? Then you'd type: He'd then still be in the group punyrank, but also have the INT_badge privilege tacked on to him. You can also add multiple commands to a user at once, like this: -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This command works exactly as the command described above except that it adds privileges to a group. -------------------------------------------------------------------------------- This command acts exactly like adding a privilege, except it removes a privilege instead. -------------------------------------------------------------------------------- This command works exactly as the command described above except that it adds a group to the configuration file. -------------------------------------------------------------------------------- This command acts exactly like adding a group, except it removes a group instead. -------------------------------------------------------------------------------- *** ; 02:13:06 GMT up 0 days, 04:05, 1 user, load average: 0.00, 0.00, 0.00 -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- If necessary, create a "plugins" directory in the palace/bin directory. If you already have plugins on your server, you don't need to do the following step. NOTE: Make sure that is a single line in the file |
|
| Guest Codes |
Guestcodes Version 0.3 README Installation /bin/guestcodes.so |
|
| Host Keeper |
Hostkeeper version 1.1.2 README Group privileges are defined in a control file called the group file.
Individual users are placed in one or more groups through use of the "`hostkeeper bless ..." command. All users are, by default, members of a It should be noted that the server may forbid commands to certain users
based on the user's rank (guest, member, wizard, or god). The server's "member" rank is distinct from Hostkeeper's "member" group. Hostkeeper Changes in Version 1.1.2 * A bug where three extra *'s where displayed in a warning Changes in Version 1.1.1 * `opcount is now an alias for `operatorcount without having to add * A bug where "***;`help hoskeeper - help on hostkeeper" would show
|
|
| Kill IP |
Killip 1.0.0 README Questions about this plugin? Write to the plugin devolper at plugins@all4palace.com. Installation bin/badboy/killip.so psdata/ip.list The killip list file is placed in /usr/local/palace/<palace-name>/psdata. Note that killip reads and writes to this file. Therefore, it cannot be edited. The killip List File God Commands `killip <whisper>/<ip> - kill a user's ip.
|
|
| No Whisper |
NoWhisper plugin README Installation /bin/nowhisper.so <initial-setting> The <initial-setting> may be one of on, guest, member, wizard, operator, god, owner, off. If it is omitted, the default setting will depend on the setting of NOWHISPER in the pserver.conf file. God commands `nowhisper [guest|member|wizard|god|operator|owner|off|on] - Set the
minimum rank of user that is permitted N.B. "`nowhisper" may be abbreviated to "'now".
|
|
| Offer / Accept 2 |
Offer2 version 1.0 plugin README Installation /bin/offer2.so User commands `offer - Offer a copy of your avatar to another user.
(Should be whispered to the intended receiver.) |
|
| PUID |
Puid 1.0.1 README Installation /plugins/puid.so on The parameter is on|off, this starts the palace with puid on or off. God Commands `puid - display status of authentication. |
|
| Secure Names |
Secure Names version 0.5 README Installation The plugin is installed following the usual plugin installation conventions. The following installation instructions assume that the Palace server has been installed in /usr/local/palace. Securenames is a standard Palace server plugin. It is installed by placing the
executable files, securenames.so and securenamesencode, in the palace binary
folder, /usr/local/palace/bin, and adding the following line to the plugin /bin/securenames.so <key-file> [-m <max-name-len>] [-w <time-window>] The <key-file> is described below. The switches are: -m <max-name-len> - Specifies the maximum length of a valid screen name. Sample Web Scripting Files signon.pl - Designed to go in the cgi-bin directory on the web server. Method of Operation <PARAM name="DefaultName" value="<encoded-name>"> It then sends the Instant Palace web page to the user. Instant Palace gets the encoded name from the DefaultName parameter and
sends it
to the Palace server. The securenames plugin intercepts the name, decodes
it and
checks it for validity. If it is valid, the login is continued using the The Time Window If names are encoded on a different machine from the one running the palace
server, the clocks on the two machines must be synchronized well enough so
recently encoded screen names will be valid. Network Time Protocol is a The Key File Unless long-term encoded screen names are desired, it is reasonable to The Secure Names Encode Program securenamesencode -w -k <key-file> <screen-name> -w indicates that time information is to be included in the encoded name to
enforce a name validity window. Note that if -w is specified, then a
non-zero -w
parameter must be specified for the securenames plugin. If -w is not (N.B. securenamesencode will perform the necessary web escaping for characters in the encoded screen name which need to be escaped.) Valid Screen Name Characters Credits Written by Mike Scott 21st April 1999 Copyright (c) 1999 Mike Scott Permission for free direct or derivative use is granted subject
to compliance with any conditions that the originators of the Securenames uses an implementation of MD5 described as follows ** md5.c ** Geek Details for the Security Analyst The encoding is performed by converting the screen name to a number n. Starting with n=0, for each character c in the screen name, it calculates: n = n*Ncs + index(c in valid_set) It then encrypts the resulting number using the Advanced Encryption Standard
algorithm (AES) with cyphertext stealing for the two blocks. (See Applied
Cryptography by Bruce Schneier for details on cyphertext stealing.) The AES If -w parameter is specified, n is multiplied by the low order bits of the encryption time giving nt. Then nt is converted to a character string using the remainder from repeated division by Ncs as in index in the passable screen name character set. The character string is written to stdout. When the securenames plugin receives a login from an Instant Palace client, it
takes the screen name and converts it to a number. If it is running with a
non-zero -w parameter, it divides out the low order bits of the encryption Securenames decrypts the encrypted name recovering the value of n. Then n is
converted to a character string using the remainder from repeated division
by Ncs
as in index in the valid screen name character set. If any indexes are outside |
|
| Word Filter |
Wordfilter plugin README Installation Wordfilter is a standard Palace server plugin. It is installed by placing the plugin file, wordfilter.so, in the palace binary folder, /usr/local/palace/bin, and adding the following line to the plugin configuration file, /usr/local/palace/<palace-name>/psdata/plugin.conf /bin/wordfilter.so psdata/transtab psdata/words The two control files, transtab, and words (described below) are placed in /usr/local/palace/<palace-name>/psdata. Note that wordfilter only reads these files. Therefore, they can be edited while the server is running and reloaded with a command to wordfilter. Method of Operation 1. Translating it character by character with the translate table built from the transtab file. Note that translation only affects the input to the word test. It does not affect the user input that is passed to the server. 2. Converting all strings of single character words to words. For
example, the input: "I want to k i l l" will be converted to, Then the input is checked against the words listed in the words file. The Transtab File Any character which translates to 0xff is removed from the stream. For example, if the character | is defined to translate to 0xff, then the input "k|i|l|l" will be translated to "kill". Any character which translates to 0x00 is forbidden and wordfilte immediately rejects the input. It is highly recommended that any tables translate upper case letters to
lower case letters. If this is not done, and it is desired to forbid
the word "kill" in all its permutations, there must be 16 entries in the
words file: Sample transtab The Words File Entry Some words which are rejected kill kill *kill kill *kill* kill It is recommended that entries using wildcards be tested against a dictionary with a utility such as grep. In many Unixes, the commands: grep '^kill' /usr/dict/words -- will test kill*, Note that when the data in the words file is read, it is translated with transtab. With a transtab which translates all upper case to lower case, this allows upper case letters in the words list to compare equal to user's input after translation. Wizard and god commands `wordfilter log [on|off] - Controls whether messages are sent to
server log when a forbidden word is Fun with wordfilter |
Terms
of Service