1 /* 2 * Copyright (c) 1996 3 * Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 4 * 5 * Redistribution and use in source and binary forms, with or without 6 * modification, are permitted provided that the following conditions 7 * are met: 8 * 1. Redistributions of source code must retain the above copyright 9 * notice, this list of conditions and the following disclaimer. 10 * 2. Redistributions in binary form must reproduce the above copyright 11 * notice, this list of conditions and the following disclaimer in the 12 * documentation and/or other materials provided with the distribution. 13 * 3. All advertising materials mentioning features or use of this software 14 * must display the following acknowledgement: 15 * This product includes software developed by Bill Paul. 16 * 4. Neither the name of the author nor the names of any co-contributors 17 * may be used to endorse or promote products derived from this software 18 * without specific prior written permission. 19 * 20 * THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND 21 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23 * ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR CONTRIBUTORS BE LIABLE 24 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30 * SUCH DAMAGE. 31 */ 32 33 /* 34 * This protocol definition exists because of the U.S. government and 35 * its stupid export laws. We can't export DES code from the United 36 * States to other countries (even though the code already exists 37 * outside the U.S. -- go figure that one out) but we need to make 38 * Secure RPC work. The normal way around this is to break the DES 39 * code out into a shared library; we can then provide a dummy lib 40 * in the base OS and provide the real lib in the secure dist, which 41 * the user can install later. But we need Secure RPC for NIS+, and 42 * there are several system programs that use NIS+ which are statically 43 * linked. We would have to provide replacements for these programs 44 * in the secure dist, but there are a lot, and this is a pain. The 45 * shared lib trick won't work for these programs, and we can't change 46 * them once they're compiled. 47 * 48 * One solution for this problem is to do the DES encryption as a system 49 * call; no programs need to be changed and we can even supply the DES 50 * support as an LKM. But this bloats the kernel. Maybe if we have 51 * Secure NFS one day this will be worth it, but for now we should keep 52 * this mess in user space. 53 * 54 * So we have this second solution: we provide a server that does the 55 * DES encryption for us. In this case, the server is keyserv (we need 56 * it to make Secure RPC work anyway) and we use this protocol to ship 57 * the data back and forth between keyserv and the application. 58 */ 59 60 enum des_dir { ENCRYPT_DES, DECRYPT_DES }; 61 enum des_mode { CBC_DES, ECB_DES }; 62 63 struct desargs { 64 u_char des_key[8]; /* key (with low bit parity) */ 65 des_dir des_dir; /* direction */ 66 des_mode des_mode; /* mode */ 67 u_char des_ivec[8]; /* input vector */ 68 opaque desbuf<>; 69 }; 70 71 struct desresp { 72 opaque desbuf<>; 73 u_char des_ivec[8]; 74 int stat; 75 }; 76 77 program CRYPT_PROG { 78 version CRYPT_VERS { 79 desresp 80 DES_CRYPT(desargs) = 1; 81 } = 1; 82 } = 600100029; 83