Re: [WebDNA] Apache .htpasswd

This WebDNA talk-list message is from

2014

It keeps the original formatting. numero = 111240
interpreted = N
texte = This is a multi-part message in MIME format.------=_SW_1198253628_1395258173_mpa=Content-Type: text/plain; charset=us-ascii; format=flowed[snip]>>> This is what I tried - and doesn't work :)>> Searching a database of users and then writing the file:>> [WriteFile secure=F&file=htpasswd][founditems][email_address]:[encrypt> method=Base64][this_password][/encrypt]> [/founditems][/writefile]"[encrypt method=APOP]" is WebDNA's md5 generator. It's been on our list to someday make an alias for "APOP"called "md5", which is a much better descriptor of the functionality.method=APOP works in the newer builds, as I believe we fixed a bug in this some time ago.>> Apache server complains about the file and I can see the Base64 > encryption> is not correct (thought I would give it a shot!!).>> The shell script:>> [WriteFile secure=F&file=htpasswd][founditems][shell]htpasswd -nb> [email_address] [this_password][/shell][/founditems][/writefile]>> The shell script unfortunately adds two carriage returns each time - > not> sure how to stop it from doing that. The shell script does work > though.>The returns in [shell] are a bug in the current releases of the WebDNA. You can get ridof the ending white space using a number of other WebDNA tags.. [getchars trim=end..] or [middle endbefore=%0A etc..Sincerely,Donovan------=_SW_1198253628_1395258173_mpa=Content-Type: text/html; charset=utf-8Content-Transfer-Encoding: quoted-printable[snip]

This is what I tried - and doesn't w=ork :)

Searching a database of users and then writing the file:
[WriteFile secure=3dF&file=3dhtpasswd][founditems][email_address]:[enc=rypt
method=3dBase64][this_password][/encrypt]
[/founditems][/writefil=e]

=

Apache server complains about the file and I can s=ee the Base64 encryption
is not correct (thought I would give it a shot!!=).

The shell script:

[WriteFile secure=3dF&file=3dhtpasswd=][founditems][shell]htpasswd -nb
[email_address] [this_password][/shell][=/founditems][/writefile]

The shell script unfortunately adds two carr=iage returns each time - not
sure how to stop it from doing that. The she=ll script does work though.

------=_SW_1198253628_1395258173_mpa=-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Apache .htpasswd (Tom Duke 2014) Re: [WebDNA] Apache .htpasswd (Donovan Brooke 2014) Re: [WebDNA] Apache .htpasswd (Dan Strong 2014) [WebDNA] Apache .htpasswd ("IBS Ltd." 2014)

This is a multi-part message in MIME format.------=_SW_1198253628_1395258173_mpa=Content-Type: text/plain; charset=us-ascii; format=flowed[snip]>>> This is what I tried - and doesn't work :)>> Searching a database of users and then writing the file:>> [WriteFile secure=F&file=htpasswd][founditems][email_address]:[encrypt> method=Base64][this_password][/encrypt]> [/founditems][/writefile]"[encrypt method=APOP]" is WebDNA's md5 generator. It's been on our list to someday make an alias for "APOP"called "md5", which is a much better descriptor of the functionality.method=APOP works in the newer builds, as I believe we fixed a bug in this some time ago.>> Apache server complains about the file and I can see the Base64 > encryption> is not correct (thought I would give it a shot!!).>> The shell script:>> [WriteFile secure=F&file=htpasswd][founditems][shell]htpasswd -nb> [email_address] [this_password][/shell][/founditems][/writefile]>> The shell script unfortunately adds two carriage returns each time - > not> sure how to stop it from doing that. The shell script does work > though.>The returns in [shell] are a bug in the current releases of the WebDNA. You can get ridof the ending white space using a number of other WebDNA tags.. [getchars trim=end..] or [middle endbefore=%0A etc..Sincerely,Donovan------=_SW_1198253628_1395258173_mpa=Content-Type: text/html; charset=utf-8Content-Transfer-Encoding: quoted-printable[snip]

This is what I tried - and doesn't w=ork :)

Searching a database of users and then writing the file:
[WriteFile secure=3dF&file=3dhtpasswd][founditems][email_address]:[enc=rypt
method=3dBase64][this_password][/encrypt]
[/founditems][/writefil=e]

=

Apache server complains about the file and I can s=ee the Base64 encryption
is not correct (thought I would give it a shot!!=).

The shell script:

[WriteFile secure=3dF&file=3dhtpasswd=][founditems][shell]htpasswd -nb
[email_address] [this_password][/shell][=/founditems][/writefile]

The shell script unfortunately adds two carr=iage returns each time - not
sure how to stop it from doing that. The she=ll script does work though.

------=_SW_1198253628_1395258173_mpa=-- Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

problems with 2 tags (1997) Re:listfiles-looking for slick solution (1997) Help w/Multi User Admins (1997) Image upload (2000) [ShowNext] (1997) Help! WebCat2 bug (1997) Protect and Serve (1999) Adding up weights (1998) [WebDNA] RESTART WebDNA (2016) Weird Code (2003) Here's how to kill a Butler Database. (1997) 2 databases (1998) WebCat2: multiple currency support (1997) carriage returns in data (1997) Another webcatalog site!! (1997) SQL Ref. (1999) Some ThankYou page problems (1997) carrying values forward (1998) WebDNA Mail issues (2002) Updating Prices in Online Database (1999)