StarUML 3.0
<?php | |
/** | |
* Authenticate customer | |
* | |
* @param string $login | |
* @param string $password | |
* @throws Mage_Core_Exception | |
* @return true | |
* |
<?php | |
/** | |
* Authenticate customer | |
* | |
* @param string $login | |
* @param string $password | |
* @return bool | |
* @throws \Magento\Framework\Exception\LocalizedException | |
* Use \Magento\Customer\Api\AccountManagementInterface::authenticate |
#!/usr/bin/env bash | |
#styles | |
VP_NONE='\033[00m' | |
VP_RED='\033[01;31m' | |
VP_GREEN='\033[01;32m' | |
VP_YELLOW='\033[01;33m' | |
VP_PURPLE='\033[01;35m' | |
VP_CYAN='\033[01;36m' | |
VP_WHITE='\033[01;37m' |
These set of scripts are for Magento 2. For Magento 1, see this Gist.
If you’re a DevOps engineer or a web developer, there’s a good chance that you’re already familiar and using the SSH key authentication on a daily basis. Whether it’s for logging into the remote server or when pushing your commit to the remote repository. It provides us with better security than the traditional password-based authentication.
But, when is the last time you created or upgraded your SSH key? And did you use the latest recommended public-key algorithm? If it was more than five years ago and you generated your SSH key with the default options, you probably ended up using RSA algorithm with key-size less than 2048 bits long.
To check all available SSH keys on your computer, run the following command on your terminal: