ClearFoundation Tracker - ClearOS
View Issue Details
0012061ClearOSapp-suvapublic2016-12-20 13:132016-12-22 09:30
bchambers 
user2 
normalfeatureN/A
closedfixed 
7.3.0 Beta 1 
7.3.0 Beta 17.3.0 Beta 1 
0012061: Uniqueness of hostkey should not require install scripts
Think imaging, cloning etc...
Generate hostkey on something like first boot, registration etc.
No tags attached.
Issue History
2016-12-20 13:13bchambersNew Issue
2016-12-20 14:34bchambersAssigned To => bchambers
2016-12-20 14:34bchambersStatusnew => assigned
2016-12-21 09:22user2Assigned Tobchambers => user2
2016-12-21 09:25user2Statusassigned => resolved
2016-12-21 09:25user2Fixed in Version => 7.3.0 Beta 1
2016-12-21 09:25user2Resolutionopen => fixed
2016-12-21 09:26user2Note Added: 0004441
2016-12-22 08:27bchambersNote Added: 0004451
2016-12-22 08:49user2Note Added: 0004461
2016-12-22 08:57bchambersNote Added: 0004471
2016-12-22 09:18user2Target Version => 7.3.0 Beta 1
2016-12-22 09:30user2Statusresolved => closed

Notes
(0004441)
user2   
2016-12-21 09:26   
Typically, the key generation is done on startup, but suvad is not running on most systems. Instead, the key generation was moved to the generic ClearOS "onboot" event (i.e. /var/clearos/events/onboot/suva).
(0004451)
bchambers   
2016-12-22 08:27   
/usr/bin/mkhost.sh doesn't check to see if there is an existing key.

Does onboot happen **only** on first boot, or after every reboot? If latter, we're going to have a problem of course...the hostkey will change if someone reboot the server.
(0004461)
user2   
2016-12-22 08:49   
Yup, I noticed that issue in my PXE test. Will fix it before Friday.
(0004471)
bchambers   
2016-12-22 08:57   
OK...feel free to hand this to me if you want...I was going to place it in the registration app.

B