How can i use empty password in MAMP?
I tried the command:
/Applications/MAMP/Library/bin/mysqladmin -u root -p password
and edited the config php file but empty password seems not working..(every other password works fine).
What can i do to use empty password?
There is a third party app that runs Apache & MySQL from MAMP without asking for a password each time. It’s quite secure because it uses a stored password locked in the Keychain. It also quits Apache & MySQL when you quit the app itself.
Here is how to use it:
Open the Keychain Access app and click ‘+’ to add a new item. Call the item ‘MAMP’ and enter the account name and password that you use to log in to your Mac.
Download and launch the MAMP No Password app
App is here.
Related
Recently our web hoster (Domainfactory) changed the method to externally access our online mysql database. From simple ssh "port forwarding" to a "unix socks tunnel".
The ssh call looks like this (and it works!):
ssh -N -L 5001:/var/lib/mysql5/mysql5.sock ssh-user#ourdomain.tld
The problem: you have to enter the password every single time.
In the past I used BitVise SSH client to create a profile (which also stores the encrypted password). By simply double-clicking on the profile you'll be automatically logged in.
Unfortunately, neither the "BitVise SSH client" nor "Putty" (plink.exe) supports the "Unix socks tunnel" feature/extension, so I can't use these tools any more.
Does anyone have an idea how to realize an automated login (script, tool, whatever)?.
The employees who access the database must not know the SSH password in any case!
I got a solution. The trick is to generate a SSH Key pair (private and public) on client side (Windows machine) calling 'ssh-keygen'. Important: don't secure the ssh keys with a password (simply press [enter] if you're asked for a password, otherwise you'll be asked for the SSH-Key password every time you try to SSH). Two files will be generated inside 'c:\Users\your_user\.shh\': 'id_rsa' (private key) and 'id_rsa.pub ' (public key).
On server side create a '.shh' directory within your user's home directory. Inside the '.ssh' directory create a simple text file called 'authorized_keys'. Copy the contents of 'id_rsa.pub' into this file (unfortunately 'ssh-copy-id' isn't available yet for Windows. So you have to do the copy and paste stuff on your own.) Set permissions of 'authorized_keys' file to '600'.
Now you should be able to simply SSH into your server by calling 'ssh-user#ourdomain.tld' without entering a password. Create a batch file with your individual ssh-call and you're done.
Thanks to Scott Hanselman for his tutorial: https://www.hanselman.com/blog/how-to-use-windows-10s-builtin-openssh-to-automatically-ssh-into-a-remote-linux-machine
I am following the documentation here http://designers.hubspot.com/docs/tools/local-hubl-server but when running the local-hubl-server Batch file (after unzipping the package), the browser opens a username/password window. What are the credentials? I tried root/root, admin/admin and blank username and password. I also checked the config.yaml file but I couldn't see any parameter to set the username and password. I am running on Windows 7 and JDK 1.8.0_144
Issue was another service was running in the same port as the HubL server was supposed to run. Edited the port in the config.yaml file and no username/password prompt appeared anymore.
I am a new Plone user. I have installed Plone from docker image eeacms/plone:4.3.7. But I can't create a web site because I have no username/password.
Thanks,
I have not used this Docker image. But the standard that I expect is: username admin and password admin.
When I look at the config in https://hub.docker.com/r/eeacms/plone/ this seems to be correct. See the 'user' option in the 'plone.recipe.zope2instance' recipe on that page.
Note that this username and password in the config file is only used once when there is no initial user yet. When you have started the site at least once, changing the user option will have no effect anymore. You can change the password later in the UI.
Follow the next instructions
cd data1/parts/zope2/utilities/
data1/parts/zope2/utilities/ is a path to utilities folder, that contains zpasswd.py script Note: data1 is not the default name of folder in a plone/zope installtion, find zpasswd.py
./zpasswd.py -u <user> -p <password> access
where <user> is an emergency user login name you are creating, <password> - password for this user to log in.
You will get a file access created in the utilities folder.
Move this access file into your instance (data1/parts/instance) folder with the following command
mv access ../../instance/
Now change your location form data1/parts/zope2/utilities to data1/bin, and restart your instance
cd ../../../bin
./instance restart
Login to ZMI with newly created emergency user login
Create usual Zope admin user and login with it to do all the necessary stuff in ZMI.
for more information see tutorial
I have tortoiseSVN set up on my local windows 7 computer. I access the repository with a password. For example, if I right-click on a file from within Windows Explorer, and then select 'repo-browser', the password dialogue box pops up.
I now would like to modify my setup to use key authentication, rather than passwords. I followed the instructions here: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ssh-create-keys.html
Everything worked fine until I got to this step:
Testing SSH with TortoiseSVN: ... Right click on any folder in Windows
Explorer and select TortoiseSVN →
Repo-Browser. You will be prompted to
enter a URL, so enter one in this
form:
svn+ssh://svnuser#SvnConnection/repos
When I select Repo-Browser, the password dialogue pops up immediately. I am not prompted to enter a URL. If I try canceling the password dialogue, the password dialogue just pops up again.
How do I get the password dialogue to stop popping up? How do I "tell" TortoiseSVN that I want to use key authentication rather than passwords?
The password dialog probably pops up because TorToiseSVN fails to find any ssh key.
On Windows, this is usually due to the environment variable HOME being not defined by default. (HOMEDIR is, HOME is not).
You can set HOME to any directory of your choice, it needs to contain a .ssh directory with your public/private key in it.
Then, make sure that basic SSH communication works first, before fiddling with the TortoiseSVN client itself.
I develop using MAMP pro on my Mac. When I start MAMP it prompts me for a password if I use port 80. If I use a higher port it doesn't prompt me, but I have to append the port number in the URL ( eg dev.local:8888 ).
Does anyone know how to make it not prompt for password when using standard ports?
Thank you.
I've put together an app that allows you to start/stop MAMP's Apache and MySQL without the password request, even on port 80. It stores the password in Keychain, so you only need to enter it once. It has a nice icon too!
Download: http://www.46palermo.com/blog/run-mamp-without-password-easy-way/
According to a living-e rep they are considering adding an option to store the password in the keychain:
http://forum.webedition.de/phpBB/viewtopic.php?f=4&t=5517&p=12019
Update: I pestered Living-e support and got them to add it as a feature request to their bug tracker. The link is here: http://qa.living-e.de/tracker/view.php?id=3648 (requires registration) if you want to follow it.
Another update: Still following this issue. Looks like living-e moved their bug tracker, the new link to this issue is:
http://bugs.mamp.info/view.php?id=3652
It's in German but the Google translation is:
When will start and stop the server in
each case the admin password is
required if port is used as low-1024th
If we could get the password from the
OS X Keychain / keyring, allowed
themselves to avoid annoying popup
ads.
Or a German speaker's translation is:
When the Server starts/stops it will ask for the admin password each time.
If it could get the password from OS X Keychain / Keyring, the annoying popup could be avoided.
As found on Macworld and already mentioned by Tom in the other answer there is a way with applescript! Downside is you have to save your user credentials in plain text.
Open AppleScript Editor
Enter the following code replacing YOURPASSWORD and YOURUSERNAME with your user credentials
Save it as application. You might tick run-only to prevent other users from reading the plain text as a small security measure
do shell script "/Applications/MAMP/bin/startApache.sh &" password "YOURPASSWORD" user name "YOURUSERNAME" with administrator privileges
do shell script "/Applications/MAMP/bin/startMysql.sh > /dev/null 2>&1"
There might be an issue with the correct file path as MAMP apparently changed startmySQL.sh to startMysql.sh in some version, so double check if it's not working!
You can put the new application in the Login Items (System Preferences -> Users & Groups -> Login Items), so the Apache server and MySQL start automatically without even showing up the MAMP-App at startup (silent start).
In response to the commands that were posted:
1) Run MAMP on port > 1024
Running all of the servers on MAMP (nginx, apache, mysql) with port ranges above 1024 allows the Mac OS X account you logged in with to launch the services, so you will not be asked for a password in this instance. Any server that runs below port 1024 requires root privileges when being executed.
2) chmod -R a+w /tmp
This command would recursively go through all files and sub folders in /tmp and make them writable for the current user. When MAMP launches, servers create temporary files in this directory.
Also if you decide you want to run the servers below port 1024 and want a solution with applescript that does not store the password in plain text then see this link applescript password with keychain
I'm now using these two applescripts to start/stop MAMP, you can save startup script is a login item so it's always up when I boot. It does mean storing your password in plain text, as Im the only one using this machine I can live with it, better than typing in my password at least three times a day.
I bind apache to port 8080 and then use port forwarding from 80 to 8080
sudo ipfw add 100 fwd 127.0.0.1,8080 tcp from any to any 80 in
Works for me, but I'm working on making the above script permanent. So far, nothing I've tried sticks, so I just run the command above in terminal after restarting. But you can then freely start and stop MAMP without a password and use a URL without :8080 or :8888.
Its a security issue, and MacOS with its UNIX heritage like security (=Good Thing). That's why MacOS asks for passwords all the time. Not much you can do about it as far as I know.
1) Run MAMP on port > 1024
2) chmod -R a+w /tmp