How do I lock my Virtual Machines (VM) in virtual box to avoid accidental deletion? IE: Password? Prompt?
Hmm, you can download the extension pack, which allows you to set a password from the vbox downloads page, but I don't know whether or not this would make you enter the password before deleting it. To do so, download the extension pack from vbox downloads page, open up vbox, highlight the machine in question, go to settings, general, encryption(tab above name). There, enable encryption (checkbox), whichever encryption you prefer, password (anything you want).
Related
I'm trying to figure out where all WHM settings are stored. I got a task to prepare some template with WHM and cPanel installed but I can't find anywhere any information what is the name of the database where information (with settings) are stored.
I'm precisely looking for the option to turn on email notification in cPHulk about banned user IPs. I know that I can set it up later but I don't want to make any of initial setup in WHM/cPanel.
Is any chance to manually change this settings value ? (either in database or file).
I'm looking as well where are stored values for WHM option: "Show IP Address Usage"
By default, you can only preconfigure WHM using cpanel.config file as described in their docs: https://documentation.cpanel.net/display/1144Docs/The+cpanel.config+File
Unfortunately, this only covers 'Tweak Settings' section, so you can't preconfigure cPHulk using it. One of the alternatives would be to use WHM API and fire it after the server is installed. With this API you have way more options, e.g. cPHulk controls are there: https://documentation.cpanel.net/display/SDK/WHM+API+1+Functions+-+load_cphulk_config
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.
Sorry for my bad English, but if you can help my it will be great.
I have couple of file system over my network and every night I need to take one file from another file system to mine.
for that to happen i'm using a Batch script how mapping me the drive with net use command.
my problem is that i don't want the password will go through clear text
( To see my password or to sniff it).
my questions is :
there is any way that i can encrypt my password and still login with the same credentials.
Thank You
If you can set up a Domain controller using either one of your Windows machines, or Samba, then you could use Trusted authentication based on the user executing the scheduled job that executes the batch file.
Alternately, you could encrypt the password and have a program decrypt it and execute the net use, but you're always* going to be faced with the fact that if your computer can send the password out when you don't type it in, then your computer knows your password, and anyone with physical access to that computer can get your password.
*Unless your computer doesn't know the password, and instead relies on an HSM (Hardware Security Module).
I had the same thing but found a nice workaround.
The passwords are not stored in DOS so I went from the run menu and simply typed the name of the path like "\server\files".
When it asked for credentials I ticked the checkbox "Save credentials"
The password will then be stored in your Windows Credential Manager (control panel) and this way your dos batch file fwill always now the password.
I think I need to add a key from the user keyring to the kernel keyring on login for this, but let me just explain the whole thing:
I have a custom ecryptfs directory set up with a huge annoying passphrase, because Ubuntu refuses to implement support for key files:
2011: Unfortunately, we're not building ecryptfs against ssl at this time, due to license incompatibilities (as noted below). I'm going to leave this bug open, though, and try and get those sorted out.
2012: there are no plans to improve this feature in the near
term. It is a considerable amount of work, yet no developers have shown
interest in the feature.
I want to mount/'unlock' this ecryptfs directory automatically when I log in, without having to enter this annoying passphrase manually. With an encrypted home in Ubuntu (also ecryptfs) this happens with a key that is unwrapped using the login password, but this does not work for custom mounts.
For other uses (e.g. LUKS) you can simply store the key/passphrase in your user keyring. But because ecryptfs works in the kernel, this key needs to be stored in the kernel keyring, not the user keyring.
Manually, you would add the key to the kernel keyring using ecryptfs-add-passphrase or ecryptfs-manager, after which you can mount and unmount the ecryptfs directory as much as you want. But after a reboot, this key is gone again, and with good reason.
But I want it back automatically after I login with my user so I can mount/unmount the ecryptfs directory again without having to enter it's password. How can I do this?
update
On Archlinux there is this tool called ecryptfs-simple developed specifically for this purpose: ecryptfs-simple is a utility for users that want to work with eCryptfs in the simplest way possible. The idea is to make eCryptfs as easy to use as EncFS.
Apparently, you can setup automatic mounting with ecryptfs-simple -a, but this tool is not available for Ubuntu, and I don't know if this setup survives a reboot.
It sounds like you want to manipulate keys, so keyctl might be your weapon of choice. Unless you're referring to some other Ubuntu-specific keyring I'm unfamiliar with. From man keyctl I can copy a key from the root/sudo/(kernel?) keyring into my user keyring with this command, something similar should work for you:
sudo keyctl pipe (wantedkeyid#) | keyctl padd user newkeydesc #u
And maybe you've already read ArchWiki's excellent article on using eCryptfs. https://wiki.archlinux.org/index.php/System_Encryption_with_eCryptfs#Auto-mounting
It's got info on using Ubuntu tools, or eCryptfs manually, and a section on auto-mounting (with PAM). Or maybe a simple bash script to ecryptfs-add-passphrase (reading your keyfile) & mount your folder would be easier? And ecryptfs itself supports reading the passphrase from a file too with passphrase_passwd_file=, see man ecryptfs
You need to store the passphrase somewhere, and then you can mount the filesystem automatically. But it's probably a bad idea — to save the key locally.
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.