Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Adding SuperUser Password through CMD

Help
Mark
2012-04-14
2013-05-31
  • Mark
    Mark
    2012-04-14

    Hey guys, I've been having trouble (like many people) with adding the
    superuser password through CMD.

    I've tried the traditional way of gaining superuser rights following the Mumur
    guide, but I constantly ended up the same message of having to enter in a
    password becasue mine was wrong. I understand how the certificate process
    works and everything, and I even tried uninstalling the Mumble/Murmur files
    and re-installing to try and get a "fresh" start again, but the same
    information carried over.

    I never specifically set a SUPW, I know some will say that it was the first
    user account, but I just never entered anything in that said SUPW.

    So, to CMD. -> I enter in "cd %programfiles(x86)%\Mumble" to get into the file, then I try to put in "murmur.exe -supw Password_of_your_choice" Obviously changing the "password of your choice"

    The error message I receive says today's date and the time, then says "Unknown
    argument "[-ini". I know only a small amount when it comes to running commands
    in the CMD-prompt, so I don't know if this is an error of what I'm typing or
    what's happening.

    And just to be sure, once this SUPW is set through cmd, I can then log into my
    hosted server with ANY certificate, and just put SuperUser as the username,
    and the password as what I set it through here. Correct?

    Thanks in advance!

     
  • Natenom
    Natenom
    2012-04-14

    1. In this case the square brackets stand for an optional argument, you must not use them in your command.
      So the correct commandline for you should be:
      murmur.exe -ini "c:\program files(x86)\Mumble\murmur.ini" -supw
      "Password_of_your_choice"

    2. Yes.

     
  • Mark
    Mark
    2012-04-14

    Thanks a lot Natenom!

    That got me through to the next error message now, and I hate to be even more
    of a burden, now it will tell me that "c:\program files(x86)\Mumble\murmur.ini
    cannot be opened". Do you think that is a UAC issue since I'm on windows 7?
    Obviously I am logged in an admin.

     
  • Natenom
    Natenom
    2012-04-14

    That was a copy & paste issue.
    murmur.exe -ini "c:\programfiles(x86)\Mumble\murmur.ini" -supw
    "Password_of_your_choice"

    AFAIK you could even remove the complete "-ini file" argument because murmur
    looks for this file in the current working directory.

     
  • Mark
    Mark
    2012-04-14

    I see that, but the problem now is that the command to access that file is
    getting stopped. When I run the command, it opens up an instance of Murmur,
    then gets the error message and closes it out.

    It seems as if something is blocking the .ini file from being accessed and
    changed. I looked into permissions and UAC, but didn't help. Thank you for
    your help thus far Natenom, been a great user.

     
  • Mark
    Mark
    2012-04-14

    Thought this might work and I think it did! I copied the .ini file to my
    desktop, ran the command with the new path, it said SuperUser password changed
    to 1. Now I will copy the .ini from my desktop back to the install folder and
    overwrite the old one. Let's see what happens

     
  • I know this post is from 6 months ago, but just wanted to throw this in here
    just in case. The problem you're (hopefully were actually) running into is
    that you command prompt doesn't have the elevated privileges it needs to edit
    the .ini file. You can get around this two ways. The first is the way you
    solved this. You can also run "cmd" as an Administrator by going to Start ->
    All Programs -> Accessories, then right-click Command Prompt and choosing Run
    as Admin (this is assuming you're using Windows 7).

     
  • M^3
    M^3
    2012-10-18

    Running an internet server daemon with higher privileges than needed can be
    risky if an exploit of that daemon is discovered down the road. You can do it
    just know there are potential risks, though the developers do seem to keep
    security in mind.

     

  • Richard
    2013-05-31

    Weighing in late in this conversation I have a similar problem with an "unknown argument" but the argument that is being rejected is ANYTHING that I put in for my password. Current string is:

    murmur.exe -ini -supw password

    That's it and the only part it doesn't like is the password. Ideas?

     
    • Not sure if this is it, but sometime you have to actually "type" your
      password in and not copy and paste.

      Signature


      Wayne McMichael . www.waynemcmichael.com


      From: Richard [mailto:None]
      Sent: 31 May, 2013 12:46 AM
      To: [mumble:discussion]
      Subject: [mumble:discussion] Adding SuperUser Password through CMD

      Weighing in late in this conversation I have a similar problem with an
      "unknown argument" but the argument that is being rejected is ANYTHING that
      I put in for my password. Current string is:

      murmur.exe -ini -supw password

      That's it and the only part it doesn't like is the password. Ideas?


      Adding
      https://sourceforge.net/p/mumble/discussion/492607/thread/b1bff7b7/?limit=2 5#3911 SuperUser Password through CMD


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/mumble/discussion/492607/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/