Making TurnKey more turnkey - the end to default passwords

Good idea regarding github, that will make it a lot easier to pull the code. It should also make your life simpler publishing updates, and tracking revisions (which I hope you're already doing).

I'll push out the feedback as soon as I can.

I'm sure I'll learn a couple of lessons from that feedback. I'v already learned a lot helping this project. BTW, I'm missing your feedback on the tklpatch commands of the tkldevenv. I'll upload the entire patch to github so that when you are finally free of the 11pt1 release, you can easily pull/diff those. As you are the author of the original scripts, your feedback is invaluable to the future of that appliance. 

It was a lot of work but I think it adds a lot to the user-experience and was worth the effort.

We'll be including Magento, PrestaShop and VTiger with the 11.0 release (coming shortly), as they are ready and no point in holding them back. I've also taken notes for feedback (for you and Basil) which I need to summarize - I'll try get that done soon. 

Excellent work guys, looking good, I like also that domains are being added where applicable. I'm anxiously waiting for the beta of the new appliances! 

I know how busy you are and really fully appreciate that you took the time to lay some of this out for me. I'm working through Python in a class, and am gonna enjoy digging in see mechanism. Thanks again,

Rik

Thanks Rik!

The code snippets only show how we take the clear text password and convert it into the desired hash for storage. The code displayed in the post are (mainly) taken from the /usr/lib/inithooks/bin/$APP.py, which is called from the related script in firstboot.d (which may preseed the answers).

Why the separation of code? Unix philosophy - do one thing, and do it well. Take a look (if you haven't already) at the inithook documentation.

To wet your appetite (as you asked so nicely), I've attached the full bin/redmine.py

#!/usr/bin/python
"""Set Redmine admin password and email

Option:
    --pass=     unless provided, will ask interactively
    --email=    unless provided, will ask interactively
"""

import sys
import getopt
import hashlib

from dialog_wrapper import Dialog
from mysqlconf import MySQL

def usage(s=None):
    if s:
        print >> sys.stderr, "Error:", s
    print >> sys.stderr, "Syntax: %s [options]" % sys.argv[0]
    print >> sys.stderr, __doc__
    sys.exit(1)

def main():
    try:
        opts, args = getopt.gnu_getopt(sys.argv[1:], "h",
                                       ['help', 'pass=', 'email='])
    except getopt.GetoptError, e:
        usage(e)

    password = ""
    email = ""
    for opt, val in opts:
        if opt in ('-h', '--help'):
            usage()
        elif opt == '--pass':
            password = val
        elif opt == '--email':
            email = val

    if not password:
        d = Dialog('TurnKey Linux - First boot configuration')
        password = d.get_password(
            "Redmine Password",
            "Enter new password for the Redmine 'admin' account.")

    if not email:
        if 'd' not in locals():
            d = Dialog('TurnKey Linux - First boot configuration')

        email = d.get_email(
            "Redmine Email",
            "Enter email address for the Redmine 'admin' account.",
            "admin@example.com")

    hashpass = hashlib.sha1(password).hexdigest()

    m = MySQL()
    m.execute('UPDATE railsapp_production.users SET mail=\"%s\" WHERE login=\"admin\";' % email)
    m.execute('UPDATE railsapp_production.users SET hashed_password=\"%s\" WHERE login=\"admin\";' % hashpass)

if __name__ == "__main__":
    main()

This is brilliant. And knowing how to do that is magical and genious from my point of view. I'm trying to make sense of the code snippets and not getting very far. I understand when values are being passed to MySQL - but take Redmine for example: is that line a part of a configuration file, or is that the value of the field in the MySQL table? Fascinated.

Very tidy feature!

I've been asked via email, on twitter as well on the forums when the 11.0 release is coming out, and I promised before the end of the year. We partly lived up to my promise. All 11.0 ISO's have been released, TKLBAM profiles updated, and Amazon Images (AMI's) uploaded.

And now, before the new year comes in, I pushed out a large update to the Hub which adds:

• Support for all 11.0 appliances. 2009-10.2 appliances are still available under the legacy option.
• Support for preseeding 11.0 appliances (launch form updates via AJAX). TKLBAM will also be initialized via preseeding so you don't need to copy/paste the Hub API Key.
• Support for Asia Pacific - Singapore region (ap-southeast-1).
• New help/FAQ section.
• Minor bugfixes

We'll be making the official 11.0 announcement once the VM builds are ready and released, and in that announcement include more details on what has changed in the Hub.

Lastly, if you come across any issues with the Hub, please post a comment or send feedback via the Hub.

I am looking around the web for ways to import batches of customers into Magento and move cleartext passwords into hashed format.

I see your method for hashing the Admin password.

Is there a way, for instance in Open Office or MySQL to convert a clear password to the correct Hashed password?

The only other method I know it to tell customers they have been imported to the new system, and please follow the "lost password" link to set a new one.  This is somewhat untidy it seems.

Thanks for all the great work.  Awesome set of work here!

You can access your server vai webshell or webmin

See /core for port numbers and sample screenshots.

I am all out of ideas and have no experience with Jenkins. Perhaps someone on that thread has some further ideas for you?

See the bug report here and in the forums here (with a workaround). However AFAIK this shouldn't affect SSH login, so perhaps the non-US keyboard is also a culpret...

My suggestion would be to either install with a US keyboard (if you have one) and then change the keyboard to whatever you are using. Or just use a very simple password initially (with keys that will work...), configure your non-US keyboard and then reset the password. I don't have instructions handy on how to set up your non-US keyboard but google should get you going, just keep in mind that TKL v12.x is based on Debian Squeeze...

Also FWIW I have run a poll to ask about setting timezone and/or non-US keyboard on first boot. It is also logged on the TKL Dev traker. There is also a bug report about non-US keyboard causing log in issues (although this seems to be mainly from the web browser).