Impossible, unless the customer sets up DNS. I'd just generate a self signed one, add an upload option and call it a day.
On Oct 18, 2017 6:41 PM, "Mike Hammett" <[email protected]> wrote: > How difficult would it be to get LetsEncrypt to work on there? > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL> > <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> > <https://www.linkedin.com/company/intelligent-computing-solutions> > <https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix> > <https://www.linkedin.com/company/midwest-internet-exchange> > <https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > > > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > ------------------------------ > *From: *"Forrest Christian (List Account)" <[email protected]> > *To: *"af" <[email protected]> > *Sent: *Wednesday, October 18, 2017 6:40:17 PM > *Subject: *[AFMUG] Favorite https: cert implementation for managed gear > > 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 > <https://maps.google.com/?q=3577+Countryside+Road,+Helena,+MT+59602&entry=gmail&source=g> > [email protected] | http://www.packetflux.com > <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> > <http://twitter.com/@packetflux> > > >
