<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div></div><div><div>Currently SSH is used. </div><div><br></div><div>Two forms of access are required to create a template:</div><div>1) SSH to the CT to install/ configure/ etc. When I say SSH, this could also be the Java console.</div><div>2) SSH to the HW node to tar the CT. This is where the issue is as this requires a level of access which essentially means that you have access to literally everything on the HW node.</div><div><br></div><div>To me, the 'sensitive' stuff is a feature and not a problem. I have a 'development' key on all my templates so that I can connect with a single key as soon as the CT is created. From there, I can then replace the key as required. I realise this might be quite a unique use case and therefore I'm not so precious about it but I was trying to give an example where you might want to keep the stuff which you guys want to get rid of. I think this should be down to the template creator - leave in what should go into the template and remove what shouldn't... rather than having the templating process messing with it. </div><div><br></div><div><br></div><div>James Coyle<br></div><div><br></div><div>E: <a href="mailto:james.coyle@jamescoyle.net" data-mce-href="mailto:james.coyle@jamescoyle.net">james.coyle@jamescoyle.net</a> <br>Skype: jac2703<br>Gtalk: <a href="mailto:jac2703@gmail.com" data-mce-href="mailto:jac2703@gmail.com">jac2703@gmail.com</a> </div><div>www: <a data-mce-href="http://www.jamescoyle.net" href="http://www.jamescoyle.net">www.jamescoyle.net</a></div><span name="x"></span><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Daniel Hunsaker" <danhunsaker@gmail.com><br><b>To: </b>"James A. Coyle" <james.coyle@jamescoyle.net><br><b>Cc: </b>pve-devel@pve.proxmox.com, "Dietmar Maurer" <dietmar@proxmox.com><br><b>Sent: </b>Thursday, 6 March, 2014 10:48:34 AM<br><b>Subject: </b>Re: [pve-devel] Create template from CT<br><div><br></div><p dir="ltr">The backup/restore method isn't intended for distribution-worthy templates, so this tends to be a non-issue. If you have access to do backup/restore, you have access to get at sensitive files within the CTs and backups already anyway.</p><p dir="ltr">Ultimately, since the vast majority of template creation is necessarily manual, the tar step being manual as well is a minimal amount of overhead which preserves the principle of least surprise as a side effect. Unless we *can* make a magic method for removing all the sensitive stuff, we should avoid allowing screwing the whole process up through ignorance by not putting the option in the web interface.</p><p dir="ltr">Out of curiosity, how exactly are you setting up the CTs for conversion if you're not using SSH?</p></div><div><br></div></div></body></html>