'\" -*- coding: us-ascii -*- .if \n(.g .ds T< \\FC .if \n(.g .ds T> \\F[\n[.fam]] .de URL \\$2 \(la\\$1\(ra\\$3 .. .if \n(.g .mso www.tmac .TH msencrypt 1 "08 May 2021" "" "" .SH NAME msencrypt \- create an encryption key or encrypt portions of connection strings for use in mapfiles .SH SYNOPSIS 'nh .fi .ad l \fBmsencrypt\fR \kx .if (\nx>(\n(.l/2)) .nr x (\n(.l/5) 'in \n(.iu+\nxu [\fB-keygen\fR \fIfile\fR | \fB-key\fR \fIfile\fR \fIstring\fR] 'in \n(.iu-\nxu .ad b 'hy .SH DESCRIPTION \fBmsencrypt\fR can create an encryption key or encrypt portions of connection strings for use in mapfiles. Typically you might want to encrypt portions of the CONNECTION parameter for a database connection. The following CONNECTIONTYPEs are supported for using this encryption method: .TP 0.2i \(bu OGR .TP 0.2i \(bu Oracle Spatial .TP 0.2i \(bu PostGIS .TP 0.2i \(bu SDE .SH OPTIONS .TP \*(T<\fB\-keygen\fR\*(T> \fIfile\fR Creates a new encryption key in \fIfile\fR. .TP \*(T<\fB\-key\fR\*(T> \fIfile\fR \fIstring\fR Use the key in \fIfile\fR to encrypt \fIstring\fR. .SH NOTES \fBUse in Mapfile\fR. .PP The location of the encryption key can be specified by two mechanisms, either by setting the environment variable MS_ENCRYPTION_KEY or using a CONFIG directive in the MAP object of your mapfile. For example: .PP .nf \*(T< CONFIG MS_ENCRYPTION_KEY "/path/to/mykey.txt" \*(T> .fi .PP Use the { and } characters as delimiters for encrypted strings inside database CONNECTIONs in your mapfile. For example: .PP .nf \*(T< CONNECTIONTYPE ORACLESPATIAL CONNECTION "user/{MIIBugIBAAKBgQCP0Yj+Seh8==}@service" \*(T> .fi .SH EXAMPLE .nf \*(T< LAYER NAME "provinces" TYPE POLYGON CONNECTIONTYPE POSTGIS CONNECTION "host=127.0.0.1 dbname=gmap user=postgres password=iluvyou18 port=5432" DATA "the_geom FROM province using SRID=42304" STATUS DEFAULT CLASS NAME "Countries" COLOR 255 0 0 END END \*(T> .fi .PP Here are the steps to encrypt the password in the above connection: .TP 0.4i 1. Generate an encryption key (note that this key should not be stored anywhere within your web server's accessible directories): .PP .nf \*(T< msencrypt \-keygen "/home/user/mykey.txt" \*(T> .fi .PP And this generated key file might contain something like: .PP .nf \*(T< 2137FEFDB5611448738D9FBB1DC59055 \*(T> .fi .TP 0.4i 2. Encrypt the connection's password using that generated key: .PP .nf \*(T< msencrypt \-key "/home/user/mykey.txt" "iluvyou18" \*(T> .fi .PP Which returns the password encrypted, at the commandline (you'll use it in a second): .PP .nf \*(T< 3656026A23DBAFC04C402EDFAB7CE714 \*(T> .fi .TP 0.4i 3. Edit the mapfile to make sure the 'mykey.txt' can be found, using the "MS_ENCRYPTION_KEY" environment variable. The CONFIG parameter inside the MAP object can be used to set an environment variable inside a mapfile: .PP .nf \*(T< MAP ... CONFIG "MS_ENCRYPTION_KEY" "/home/user/mykey.txt" ... END #mapfile \*(T> .fi .TP 0.4i 4. Modify the layer's CONNECTION to use the generated password key, making sure to use the "{}" brackets around the key: .PP .nf \*(T< CONNECTION "host=127.0.0.1 dbname=gmap user=postgres password={3656026A23DBAFC04C402EDFAB7CE714} port=5432" \*(T> .fi .TP 0.4i 5. Done! Give your new encrypted mapfile a try with the \fBshp2img\fR(1) utility!