Today, I just setup a new VM, from here.
https://www.vmware.com/go/downloadplayer
So, I set it up and everything seems to be working fine. I can definitely login with my password, but I can't copy/paste anything from my laptop to the new VM. I tried to run this code: 'sudo apt-get install open-vm-tools'. That, supposedly will allow me to copy/paste. However, when I enter that, I'm prompted for my password on the VM. I enter it, and get a message that it's not correct. I've done this 3x; the password is definitely correct, or I couldn't even login to the VM. Can someone tell me what's going on? All I want to do is copy/paste. That's it. Thanks.
You have to enable Copy and Paste in VMWare settings, e.g. like that.
Related
I am using node v0.18.4 on a raspberry pi 3 Jessie. I want to secure the node-red editor, for which i followed the security.html page provided by node red and also I watched a video on youtube. I did the exact same steps, which are:-
1) Go to ~/.node-red/settings.js
2) Uncomment adminAuth
3) Install node-red-admin - sudo npm install -g node-red-admin
4) Generate hash password using, node-red-admin hash-pw
5) Paste the hashed password to adminAuth password field.
6) Save and restart node red
However I do not get the login prompt. The editor just loads without asking me for the username and the password.
I looked it up online, and all I found were httpNodeAuth. I am not trying to secure the UI, I am trying to secure the editor. Also I found a post that said sessions.json file would be written by node-red which was empty when I checked. It said that, it was because on when running node red on images, this file is not writable.
So I even followed the steps to placing the settings.json file to a writable location, and then created a shortcut for it in the node-red folder. This also didn't work out for me.
I also found a post where it said that the hashed password must have a correct format. I got a link to a hash password generator site. I copied the hash password from there but even that didn't result in the login prompt.
Please suggest why I might be getting this problem.
Thanks in advance.
I had somewhat similar problem on PC - asked for login at first, then didn't ask again. Shift with reload didn't change it either.
I did log out, then it asked for password, so you might try that. Also switching from Chrome to IE, I got a login as well.
Okay, I know it may sound stupid but I really need your opinions or suggestions about something. A computer has an older WAMP version (5 1.7.0) installed in it (I'm not the one who installed it) and running on Windows XP. Whenever I go to its Phpmyadmin page, it automatically gives me access to anything what are in it. That's a security hole that must be solved. I want it to ask me or prompt a login page first. I still have no success from the following steps that I've tried:
I have set the username as root and the password as
samplepass from the Priveleges section in the Phpmyadmin page - Still no success!
I also modified the config.inc.php file. I put the said password in $cfg['Servers'][$i]['password'] and changed the "cookie" as "config" in $cfg['Servers'][$i]['auth_type'] - Still no success!
Already restarted the connection of all WAMP services after the changes made - Still no success!
I also cleared the histories, caches, cookies, etc. in the browsers just incase - Still no success!
One thing I've noticed is that the file has no $cfg['Servers'][$i]['AllowNoPassword'] nor $cfg['Servers'][$i]['AllowNoPasswordRoot'] in it. I tried including that into the file and providing it the value as "YES" but still, no login page is displaying.
I don't want to reinstall the WAMP or install new one. I'm afraid to destroy what was already there. So what do you think why the login page is still not displaying? Am I forgetting something or missed to do? (Sorry for sometimes I'm forgetful).
Alright, just after trying the things out again with still no success, I came up with this:
I changed back the value of $cfg['Servers'][$i]['auth_type'] from "config" to "cookie"
Then I added a random text value for $cfg['blowfish_secret']
After the (2) changes I made, I restarted the all the services again and poof! Login page is now displaying! But I'm still confused why my first tries didn't work. I'm not a know-it-all person about this particular area and sure there's more things to know about database thing. That's all.
I'm trying to use Packer to build a Vagrant box from an ISO, using a boot2docker ISO. All goes well until I try to run vagrant up, which fails with "Error: Authentication failure. Retrying...". The box is OK - I can get in with vagrant ssh by supplying a password. But ssh authentication doesn't work.
This turns out to be a known problem with a known solution - add a public key to .ssh/authorized_keys on the box. If I do this manually after I've accessed the box with a password, I don't need the password for future access. So I updated my Packer script to do that - and found that changes made to the boot volume are discarded without effect. Packer script changes to other volumes work, but not to the boot volume, which is the one I need to update. It looks like it can only ever be an image of the ISO.
Is my only option to create my own ISO with the public key preinstalled? Is there any way to use Packer to apply the key to the output box?
This is an old question but since there's no answer, I'll contribute.
I was having the same problem; no matter what I changed in my Kickstart or provisioner scripts, my changes to the vagrant user's authorized_keys were not visible in the final box as built by Packer. Until I realized that Vagrant kept using a cached (and older!) version of my Vagrant box built instead of the latest one.
The reason is that the box was copied once by Vagrant as "my-box", and even if the box itself was changing as I was testing fixes for this, Vagrant kept using the old one without my fixes because it caches it, and does not frequently check for updates. The easiest solution is to add
config.vm.box_check_update = true
to your Vagrantfile. Alternatively, you could have your Vagrantfile give a different name to your box every time in config.vm.box via some Ruby code.
Hey guys so I have an xcode bot problem. Basically I have a bot that requires a pre-script to be ran. This script runs the command a git submodule init and update, and gets an ssh authentication error.
On the os x server machine it self the appropriate ssh keys have been set on the user admin (tested). In xcode on my machine the server is connect as the user admin. However it seems like when the script is being run it is not being run as admin(tested by creating a text file in ~ and wasnt there after). I was wondering if it was possible to su in the script, i've looked online and it seems like it wouldn't be possible because I don't know what user xcode bot is running the script as (my guess is its running as Guess)
Any advice on this? Or on a way to run the command as a different user(must be in the script)
_xcsbuildd is the account which the bot runs under. Make sure that account has the necessary permissions.
Xcode server runs an integration from a separate user called _xcsbuildd. If it is possible for you to login remotely to the machine that Xcode Server is running then you can login under that user through the Terminal, and should be able to add or check any ssh keys that are loaded with that user.
Here is a useful blog post on how to do this http://papaanton.com/setting-up-xcode-6-and-apple-server-4-0-for-continues-integration-with-cocoapods/
Scroll down to the part called Adding additional SSH Key to the Xcode Server That should be able to walk you through how to do that. I know its not an automated script, but its how I was able to get past my SSL issues, and maybe it'll help you as well
I've followed a couple of tutorials for creating an Amazon EC2 instance using the command line tools
http://www.zabada.com/tutorials/deploying-a-rails-application-to-production-on-amazon-ec2.php
http://www.smartfrog.org/wiki/display/sf/Starting+an+EC2+Image+by+Hand
and all is well, i
ec2-add-keypair (directing the output of ec2-add-keypair directly to a file in ~/.ssh)
chmod 600 the keypair
ec2-run-instance
ec2-describe-instances
then, when the new instance is running try to ssh on
ssh -i ~/.ssh/ec2-keypair ec2-user#foo.bar.amazon.com
At this point i'm ALWAYS prompted for a password. Obviously there's no password so it always refuses me access.
My question is, what am i doing wrong here? Why am i being prompted for a password and how can i put this right so i can ssh onto the machine i've just started?
I'm guessing this is something to do with my local setup, but as far as i know this machine hasn't had anything custom done with .ssh (there's certainly no config file or anything like that lying around that might be screwing with things).
Anyone have any ideas or suggestions?
ec2-user# ? Why not root# ?