any ideas on how to generate temporary passwords in witango? @RANDOM will give
me an integer, yes, but how to create combination of integer/alpha not obvious.
TO UNSUBSCRIBE: Go to
Roland,
Here's one way:
@EXCLUDE
@ASSIGN request$pwSpecChars value=!...@#$*+=?
@ASSIGN request$PWValidChars
value=ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz23456789@VAR
request$pwSpecChars
@ASSIGN request$pwValidLen value=@LENGTH '@@local$pwValidChars'
@IFEMPTY @ARG pwLen
@ASSIGN
In pseudo code:
@FOR stop=8
@assign ascii_val @random low=97 high=122
@assign password '@@password@char @@acsii_val'
/@FOR
Of course, you can use a other ascii ranges for the numbers, capital letters
and special characters.
In fact, I think nearly all ascii values from 33 through 126 are
thank you all for privately and posted snippets.
On Apr 20, 2010, at 9:26 AM, Roland Dumas wrote:
any ideas on how to generate temporary passwords in witango? @RANDOM will
give me an integer, yes, but how to create combination of integer/alpha not
obvious.
I like passwords that are more memorable. There are webservices you could call
with @URL that could provide that, here is one I saw.
http://www.diplodock.com/Products/PasswordGenerator/WebService/default.aspx
There are many others.
--
Robert Garcia
President - BigHead Technology
VP
and the follow-up
witango is case insensitive. seems that mysql is also case insensitive.
How do I set a look-up that is case sensitive? So that password is not
the same as ?
TO UNSUBSCRIBE: Go to
@IF @CIPHER action=hash type=md5 str=db_password = @CIPHER action=hash
type=md5 str=arg_password
-Original Message-
From: Roland Dumas [mailto:radu...@mac.com]
Sent: Tuesday, April 20, 2010 2:09 PM
To: witango-talk@witango.com
Subject: Witango-Talk: case matching
and the follow-up
@cipher in witango 5.0?
if so, can this be done in the search action?
On Apr 20, 2010, at 11:14 AM, Robert Shubert wrote:
@IF @CIPHER action=hash type=md5 str=db_password = @CIPHER action=hash
type=md5 str=arg_password
-Original Message-
From: Roland Dumas
I know for sure that @cipher is in 5.0, but it may work a little
differently.
You certainly can do this comparison in the search action if you:
A) store the password as the HASH (do one of the @ciphers when you set the
password)
Or
B) use MySQLs HASH function, at quick glance I think you would
I had a little misfortune this last weekend. I have a Recommend It program
on our commerce sites where someone can recommend the site to their friends
by entering up to 3 email address and a personal comment and then the
program emails accordingly.
You guessed it, I believe someone wrote a
ah, this works on 5.0 Thanks!
On Apr 20, 2010, at 11:14 AM, Robert Shubert wrote:
@IF @CIPHER action=hash type=md5 str=db_password = @CIPHER action=hash
type=md5 str=arg_password
-Original Message-
From: Roland Dumas [mailto:radu...@mac.com]
Sent: Tuesday, April 20, 2010 2:09 PM
MySQL is not case insensitive. MySQL can EITHER be case sensitive, or case
insensitive.
When you setup a database, or table, or even at the column level, there is a
COLLATION option. So if you are using encoding of UTF8, then you are probably
using collation of utf8_general_ci. That ci on the
Hi,
I tried a CAPTHA but didn't have any luck. Then I read it is better to
have the person uncheck a checkbox before submitting.
Ted
From: Fogelson, Steve [mailto:stevefogel...@askics.net]
Sent: Tuesday, April 20, 2010 3:20 PM
To: witango-talk@witango.com
Subject: Witango-Talk:
another winner suggestion. thank you again.
On Apr 20, 2010, at 11:27 AM, Robert Shubert wrote:
I know for sure that @cipher is in 5.0, but it may work a little
differently.
You certainly can do this comparison in the search action if you:
A) store the password as the HASH (do one of the
hmm, playing with this. For UTF8, the collation options are utf8_bin and then a
series of language specific _ci options.
for ascii, there are choices of ascii_bin and ascii_general_ci
etc.
On Apr 20, 2010, at 12:32 PM, Robert Garcia wrote:
MySQL is not case insensitive. MySQL can EITHER be
ok, I see. If I set char set at ascii and collation at ascii_bin, then the
match becomes case sensitive. Simplest solution. thank you, again.
On Apr 20, 2010, at 12:32 PM, Robert Garcia wrote:
MySQL is not case insensitive. MySQL can EITHER be case sensitive, or case
insensitive.
When
What I do is have people solve a simple math problem (ie. 3 + 4 = ?) where they
would enter 7 in a
text box. The first two numbers are random single digit numbers so that answer
will change each time.
This is easy to implement and seems to work well.
Stefan
utf8_bin, is case sensitive. You want to use utf8_general or utf8_general_ci
for mostly text fields.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
15520 Coutelenc Rd
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
rgar...@bighead.net -
18 matches
Mail list logo
