Categories

• Announcements

  Get the latest news on what's happening.
  166
  Topics
  688
  Posts

  

  @jburleson Yes both firefox and chrome uses the windows cert store as Tom posted. I know because we had to do this with our vCenter servers. You need to take the public root certificate of the self signed certificate and import it into the machine’s trusted root certificate store. Once you do that then there is no warnings in any of the three browsers. While these instructions are specific to vCenter the process would be the same for any self signed root certificate. https://tinkertry.com/how-to-get-rid-of-vsphere-browser-certificate-warnings-in-windows
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1883
  Topics
  15247
  Posts

  P

  I didn’t update kernel. it still working for me. Thanks,
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  8896
  Topics
  87404
  Posts

  S

  @Landy_Dan The FOG CA was introduced to secure the connection between fog-client software and the FOG server. We use certificate based state of the art encryption for that. But you need to know that it is a self signed CA and not derived from an official authority. Not sure if it’s wise (and even possible) to use that for your RADIUS project. Give it a try and see how far you get. Start by taking a look at all the certificate stuff in /opt/fog/snapins/ssl/ on your FOG server.
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  1999
  Topics
  19009
  Posts

  

  @cmurray139 i’m not sure. I don’t have much experience with devices that don’t have Ethernet built in. if you search the forums, you might find someone who’s already solved the problem though.