Skip to main content

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below:

BAD PASSWORD: it is too simplistic/systematic

no matter how hard password you give it will show the same.

Solution:
#########

Check if your password is Ok with the below command,

jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check
D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic


Now Create a password with the below command :


jino@ndz~$ echo $(tr -dc '[:graph:]'
7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;

You can see that this password will be ok with the cracklib-check.

jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                
7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK


Thats all,
Thanks.

Comments

Popular posts from this blog

K8s External Secrets integration between AWS EKS and Secrets Manager(SM) using IAM Role.

What is K8s External Secrets and how it will make your life easier? Before saying about External Secrets we will say about k8s secrets and how it will work. In k8s secrets we will create key value pairs of the secrets and set this as either pod env variables or mount them as volumes to pods. For more details about k8s secrets you can check my blog http://jinojoseph.blogspot.com/2020/08/k8s-secrets-explained.html   So in this case if developers wants to change the ENV variables , then we have to edit the k8s manifest yaml file, then we have to apply the new files to the deployment. This is a tiresome process and also chances of applying to the wrong context is high if you have multiple k8s clusters for dev / stage and Prod deployments. So in-order to make this easy , we can add all the secrets that is needed in the deployment, in the AWS Secret Manager and with the help of External secrets we can fetch and create those secrets in the k8s cluster. So what is K8s external Secret? It is an

Extending Your EBS Volume in Linux AWS EC2

First you have to select the EBS volume >> Actions >> Modify Volume . Now select the total volume that you want to increase to in the size section. Now click on the Modify button. Now finally do the below steps after login to the server for extending the additionally allocated space. # df -h  >> This will show you the Filesystem like '/dev/xvda1'. Expand the modified partition using  growpart  (note that you need to add a space between the device name and the partition number): # sudo  growpart /dev/xvda 1  # sudo growpart /dev/nvme0n1 1  >> for /dev/nvme0n1p1 A look at the  lsblk  output confirms that the partition  /dev/xvda1  now fills the available space on the volume: #  root@logserver:~# lsblk NAME    MAJ:MIN RM SIZE RO TYPE MOUNTPOINT xvda    202:0    0  40G  0 disk  └─xvda1 202:1    0  40G  0 part / To extend a Linux file system # resize2fs /dev/xvda1  # resize2fs /dev/nvme0n1p1 https://docs.amazonaws.cn/en_us/