Rugged Operating System (ROS Ã‚Â® ) Software User ... - RuggedCom

More documents

Recommendations

Info

Chapter 1 Introduction RUGGEDCOM ROS User Guide the configuration file) and replace the current certificates and keys with temporary certificates and keys that can be destroyed upon the device's return. Section 1.1.2 Key Files This section describes in detail the security keys used by ROS for the establishment of secure remote login (SSH) and web access (SSL). It is strongly recommended to create and provision your own SSL certificates and SSH keys. The default certificate and keys are only ever used when upgrading to ROS v3.12.0 or later. New ROS-based units from Siemens' will already have unique certificate and keys preconfigured in ssl.crt and ssh.keys flash files. The default and auto-generated SSL certificate are self-signed. It is recommended to use SSL certificates that are either signed by a trusted third party Certificate Authority (CA) or by an organization's own CA. This technique is described in the Siemens' application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows, available from www.siemens.com/ruggedcom. The sequence of events related to Key Management during an upgrade to ROS v3.12.0 or later is as follows: NOTE The auto-generation of SSH keys is not available for Non-Controlled (NC) versions of ROS. • Upgrade Boot Software to v2.20.0 or newer (see Section 1.1.3, “Bootloader Considerations”). • On first boot, ROS >= v3.12.0 will start the SSH and SSL (secure web) services using the default keys. • Immediately after boot, ROS will start to generate a unique SSL certificate and SSH key pair, and save each one to its corresponding flash file. This process will take approximately one hour on a lightly loaded unit. As each one is created, the corresponding service is immediately restarted with the new keys. • At any time during the key generation process, one may upload custom keys, which will take precedence over both the default and auto-generated keys and will take effect immediately. • On subsequent boot, if there is a valid ssl.crt file, the default certificate will not be used for SSL. If there is a valid ssh.keys file, the default SSH key will not be used. • At any time, new keys may be uploaded or generated by ROS using the "sslkeygen" or "sshkeygen" CLI commands. Section 1.1.2.1 SSL Certificates ROS supports SSL certificates that conform to the following specifications: • X.509 v3 digital certificate format • PEM format • RSA key pair, 512 to 2048 bits in length The RSA key pair used in the default certificate and in those generated by ROS uses a public key of 1024 bits in length. 2 Key Files
RUGGEDCOM ROS User Guide Chapter 1 Introduction NOTE RSA keys smaller than 1024 bits in length are not recommended. Support is only included here for compatibility with legacy equipment. NOTE The default certificate and keys are common to every instance of a given ROS firmware version. That is why it is important to either allow the key autogeneration to complete or to provision custom keys. In this way, one has at least unique, and at best, traceable and verifiable keys installed when establishing secure communication with the unit. NOTE RSA key generation times increase dramatically with key length. 1024-bit RSA keys take O(10 minutes) on a lightly loaded unit, whereas 2048-bit keys take O(2 hours). A typical modern PC system, however, can generate these keys in seconds. The following (bash) shell script fragment uses the openssl command line utility to generate a self-signed X.509 v3 SSL certificate with a 1024-bit RSA key suitable for use in ROS. Note that two standard PEM files are required: the SSL certificate and the RSA private key file. These are concatenated into the resulting ssl.crt file, which may then be uploaded to ROS: # RSA key size: BITS=1024 # 20 years validity: DAYS=7305 # Values that will be stored in the Distinguished Name fields: COUNTRY_NAME=CA # Two-letter country code STATE_OR_PROVINCE_NAME=Ontario # State or Province LOCALITY_NAME=Concord # City ORGANIZATION=Ruggedcom.com # Your organization's name ORGANIZATION_CA=${ORGANIZATION}_CA # Your Certificate Authority COMMON_NAME=RC # The DNS or IP address of the ROS unit ORGANIZATIONAL_UNIT=ROS # Organizational unit name # Variables used in the construction of the certificate REQ_SUBJ="/C=${COUNTRY_NAME}/ST=${STATE_OR_PROVINCE_NAME}/L=${LOCALITY_NAME}/O=${ORGANIZATION}/OU= ${ORGANIZATIONAL_UNIT}/CN=${COMMON_NAME}/" REQ_SUBJ_CA="/C=${COUNTRY_NAME}/ST=${STATE_OR_PROVINCE_NAME}/L=${LOCALITY_NAME}/O=${ORGANIZATION_CA}/ OU=${ORGANIZATIONAL_UNIT}/" ######################################################################## # Make the self-signed SSL certificate and RSA key pair: openssl req -x509 -newkey rsa:${BITS} -nodes \ -days ${DAYS} -subj ${REQ_SUBJ} \ -keyout ros_ssl.key \ -out ros_ssl.crt # Concatenate Cert and Key into a single file suitable for upload to ROS: # Note that cert must precede the RSA key: cat ros_ssl.crt ros_ssl.key > ssl.crt For information on creating SSL certificates for use with ROS in a Microsoft Windows environment, refer to the following Siemens' application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows. The following listing is the disassembly of a self-signed SSL certificate generated by ROS: Certificate: Data: SSL Certificates 3
Page 1 and 2: Preface Introduction 1 RUGGEDCOM RO
Page 3 and 4: RUGGEDCOM ROS User Guide Table of C
Page 11 and 12: RUGGEDCOM ROS User Guide Preface Pr
Page 13 and 14: RUGGEDCOM ROS User Guide Preface Ac
Page 15: RUGGEDCOM ROS User Guide Chapter 1
Page 19 and 20: RUGGEDCOM ROS User Guide Chapter 1
Page 67 and 68:
RUGGEDCOM ROS User Guide Chapter 2
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
show all

Rugged Operating System &#40;ROS Ã‚Â® &#41; Software User ... - RuggedCom

Create successful ePaper yourself

Delete template?

Save as template?

Rugged Operating System (ROS Ã‚Â® ) Software User ... - RuggedCom