12-16-2018
I am also sometimes refused by today's overloaded GUIs where you often cannot see if a picture is a navigation or an advertisement. (If you are suspicious and have time you can try options on it, right mouse click or "click+hold").
I have seen a wanted action, for example a "continue" button, after 2 seconds being replaced by an advertisement...
Fortunately not on Unix.com. Yet.
Back to the passwords.
In the good old times we ran "crack" on the Unix pw crypts.
The input for crack was made of a top 100 list and a dictionary and a top 100 modification rules.
Users with a cracked pw got mail, with tips for a safe pw.
A wrong pw was punished with a delay before it prompted for a new pw. That made hacking less attractive.
Today companies establish "good" passwords by enforcing longer pws, character set rules, and comparisons against a history of old pws. (Storing pws in a DB? I get sick!)
Then, companies intoduce multi-factor authentication. You must install a dozen apps on mobile devices that generate pin codes. Of course these apps are 100% safe...
And then, there is a dozen applications that have there own pws - of cause with all flavours of security turned on!
If you work for 3 companies there is hardly enough space on the backside of your keyboard to hold all the passwords and pin codes...
4 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear all,
I need to automate/script a user password change process. I'm helpless cannot use expect since it's not installed and cannot install it either. Do i have an alternative. I can store the password in a file and that would be the password that would be set to all the users. If not i don't... (1 Reply)
Discussion started by: earlysame55
1 Replies
2. UNIX for Advanced & Expert Users
I've been using various versions of UNIX and Linux since 1993, and I've never run across one that showed your password as you type it in when you log in, or one that stored passwords in plain text rather than encrypted. I'm writing a script for work for a security audit, and two of the... (5 Replies)
Discussion started by: Anne Neville
5 Replies
3. What is on Your Mind?
What is on Your Mind?
2018 FIFA World Cup - Wikipedia
I'm hoping that England are drawn into positions B2, D3, G3 or G4 so that all their games will be outside usual UK office hours and people will not desert the office with mystery illnesses to watch the games.
Expecting failure, so I... (1 Reply)
Discussion started by: rbatte1
1 Replies
4. What is on Your Mind?
Happy Holidays.
Here are my randoms thought at the end of 2018 in no particular order.
You Are Truly Blessed
IT people are lucky. We get to use our brains extensively to solve complex and challenging computer-technology related problems. This is very good for our brains. Programming,... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT FREEBSD
gpioctl
GPIOCTL(1) BSD General Commands Manual GPIOCTL(1)
NAME
gpioctl -- GPIO control utility
SYNOPSIS
gpioctl -l [-f ctldev] [-v]
gpioctl -t [-f ctldev] pin
gpioctl -c [-f ctldev] pin flag [flag ...]
gpioctl [-f ctldev] pin [0|1]
DESCRIPTION
The gpioctl utility could be used to manage GPIO pins from userland and list available pins.
The options are as follows:
-c pin flag [flag ...]
Configure pin by setting provided flags. The following flags are currently defined:
IN Input pin
OUT Output pin
OD Open drain pin
PP Push pull pin
TS Tristate pin
PU Pull-up pin
PD Pull-down pin
II Inverted input pin
IO Inverted output pin
-f ctldev GPIO controller device to use If not specified, defaults to /dev/gpioc0
-l list available pins
-t pin toggle value of provided pin number
-v be verbose: for each listed pin print current configuration
EXAMPLES
o List pins available on GPIO controller defined by device /dev/gpioc0
gpioctl -f /dev/gpioc0 -l
o Set the value of pin 12 to 1
gpioctl -f /dev/gpioc0 12 1
o Configure pin 12 to be input pin
gpioctl -f /dev/gpioc0 -c 12 IN
SEE ALSO
gpio(4), gpioiic(4), gpioled(4)
HISTORY
The gpioctl utility appeared in FreeBSD 9.0.
AUTHORS
The gpioctl utility and this manual page were written by Oleksandr Tymoshenko <gonzo@freebsd.org>.
BSD
November 7, 2013 BSD