So, on my list of things to implement in the rackinjector and followon products is the enabling of https:// for the web interface.
Part of doing this means that I somehow have to manage keys and certificates on the device. At a minimum, I'm going to permit customers to upload certificate files, unless I can figure out a better/easier way. I'm curious what those of you who are using https:// interfaces on managed gear are doing in this regards... i.e. are you generating your own certificates, how are you (or the vendor) managing this, etc? -- *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 [email protected] | http://www.packetflux.com <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> <http://twitter.com/@packetflux>
