"Quality is the parent, the source of all subjects and objects." - Robert Pirsig

Fits Observation: Henry Gurr’s How Our Mind Works


Henry S Gurr’s Article, Book, & Mind-Map, Projects


SiteMaster Henry S Gurr’s Earth Friendly Projects:


SiteMaster Henry S Gurr’s Tech Corner & Projects:



ZMMQuality WebSite: Information Concerning
*** Zen and the Art of ***
Motorcycle Maintenance
** by Robert Pirsig **

Home Page: Fors ZMM Quality WebSite
News&NewsArchive: Re Robert Pirsig & Book
ZMM Book (Full Text) Free On Internet



SUMMARY=>How Find Way In This ZMMQ Site


SUMMARY=> Robert Pirsig Zen Art Motorcycle Maint.


Celebrate: Robert Pirsig’s July1968 Motorcycle Trek


SUMMARY=>Experts & Readers Provide Guidance


SUMMARY=>SpecialStudies Zen Art Motorcycle Maint


SUMMARY=>Memories: Dennis Gary English MSU


SUMMARY=>Research Montana State UniversityMSU


SUMMARY=>“Pirsig Pilgrims”&“Fellow ZMM Travelers”

AFTER Above Link ComeUp, GoTo ''Zen and..Last Hurrah”


SUMMARY=>Maps+Info: ZMM Travel & Mountain Climb


Resources: Pirsig & Zen Art of Motorcycle Maint.


SUMMARY=>Software&Hardware: Create This WebSite


Thanks To Persons Who Created & Supported ZMMQ


PLEASE NOTICE: THE FOLLOWING 4 HANDY LINKS:

ALSO PLEASE NOTICE THESE SAME 4 HANDY LINKS: BOTTOM EVERY ZMMQ PAGE


  

TO ACCESS PHOTO ALBUMS,
Click any photo below: **OR**
Mouse Hover, Over Photo, For Album Description

These 12 Photos were taken by Robert Pirsig’s very own camera, as he Chris, Sylvia and John made that 1968 epic voyage upon which The Travel Narrative for Mr Pirsig’s ‘‘Zen and the Art of Motorcycle Maintenance‘‘ (ZMM) book was based. Taken in 1968 along what is now known as ‘‘The ZMM Book Travel Route ‘‘ each photo scene is actually ‘‘Written-Into ‘‘ Mr. Pirsig’s book => ‘‘Zen and the Art of Motorcycle Maintenance‘‘ (ZMM)

Author Robert Pirsig’s Own 12 Color Photos, Of His 1968 ZMM Travel Route Trip: Each Is Written-Into His ZMM Book. AFTER the 5 Albums Cones Up, Read & ClickOn 2nd Down.

Each of the 832 photographs in these Four Albums show a scene described in the book ‘‘Zen and Art of Motorcycle Maintenance‘‘. Each photo was especially researched and photographed along the ZMM Route to show a specific ZMM Book Travel Description Passage: This passage is shown in quote marks below the respective photo. As you look at each of these photos, you will be viewing scenes similar to those that author Pirsig, Chris, and the Sutherlands might have seen, on that epic voyage, upon which the book ‘‘Zen and the Art of Motorcycle Maintenance‘‘ was based. Thus it is, that these 832 photographs are ‘‘A Color Photo Illustrated Zen and Art of Motorcycle Maintenance‘‘. Indeed ‘‘A Photo Show Book‘‘ for ZMM. Sights & Scenes Plus Full Explanation.

My ZMM Travel Route Research Findings, Are A Page-By-Page, Color Photo Illustrated ZMM. AFTER the 5 Albums Cones Up, Read & ClickOn Top Album.

Each of these 28 photos are Full Circle Panorama Photos Seven-Feet-Wide. They were taken along the Travel Route of the book ‘‘Zen and the Art of Motorcycle Maintenance‘‘. They show a 360 degree view, made by stitching together eight photos. These Panoramic Photos, complement and add to those of my Photo Album ABOVE named  => ‘‘A Color Photo Illustrated ZMM Book, With Travel Route Sights & Scenes Explained‘‘.

ZMM Travel Route Research PANORAMIC PHOTOS 7ft wide! Henry Gurr, 2002 ZMM Research Trip. AFTER the 5 Albums Cones Up, Read & ClickOn 2nd Down.

This album shows what I saw  on my RETURN trip home (San Francisco California to Aiken South Carolina), Summer 2002. These 55 photos were taken along the Route of the “1849er’s Gold Rush to California” (In Reverse Direction). After I completed my ZMM Research, I RETURNED home by way of the Route of the ‘49’s Gold Rush. This route included the route of the “California Gold Rush Trail” (in Nevada & California), as well as portions of the Oregon Trail' all the way into Missouri. These 1849er’s Travel Route Photos, were taken AFTER I took those Photos shown in the above Album named “A Color Photo Illustrated ZMM Book, With Travel Route Sights & Scenes Explained”.

Henry Gurr’s 2002 Research Photos: California Gold Rush Trail & Oregon Trail. AFTER the 5 Albums Cones Up, Read & ClickOn 3rd Down.

Each of these seven 360 degree  Full Circle Panoramic Photos were taken along the route of the Gold Rush ‘1849’ers from Missouri to California. Each is 7 foot wide! These Panorama Photos complement and add to those of my Photo Album above named  => "Henry Gurr’s Research Photos: California Gold Rush Trail & Pioneer Oregon Trail".   AFTER the 5 Albums Cones Up, Read & ClickOn Top Album.

California Gold RushTrail & Pioneer Oregon Trail PANORAMIC PHOTOS 7ft wide! Henry Gurr, 2002 ZMM RETURN Trip. AFTER the 5 Albums Cones Up, Read & ClickOn Top Album.

Enjoy 225 Photos of Flowers & Red Wing Blackbirds Along the ZMM Route. This Album of  Color Photos shows every Flower and Red Wing Blackbird (RWBB) that I could “get within my camera sights!!”  This was done in honor of the ZMM Narrator's emphasis of Flowers and Redwing Blackbirds in the book “Zen and the Art of Motorcycle Maintenance”. I was very surprised to find RWBB's the entire travel route from Minneapolis to San Francisco.

In Honor of ZMM Narrator’s Emphasis: 225 Color Photos of ZMM Travel Route Flowers & Red Wing Blackbirds. AFTER the 5 Albums Cones Up, Read & ClickOn 5th Down.

These 165 photos show ‘‘Tourist Experiences’‘ the ZMM Traveler may have along the ZMM Route.

My 2002 ZMM Travel Route Experience: By Henry Gurr ZMMQ Site Master. AFTER the 5 Albums Cones Up, Read & ClickOn 3rd Down.

Starting Monday 19 July 2004, Mark Richardson traveled the ZMM Route, on his trusty Jakie Blue motorcycle. Mark made these 59 interesting photographs of what he saw along the way. As he toured, he pondered his own life destiny (past present future), and sought to discover his own deeper personal meaning of the book “Zen and the Art of Motorcycle Maintenance”.

Mark Richardson’s 19 July 2004, ZMM Route Trip & Photo Journal. AFTER the 5 Albums Cones Up, Read & ClickOn 5th Down.

The former home (~1968) of John and Sylvia Sutherland, at 2649 South Colfax Ave, Minneapolis MN, shown in 18 photos. Despite John's quite negative disparaging statements in ZMM, about their home back in Minneapolis, this same house, shown in these photos, looks to us like a wonderful, beautiful home along a very nice, quiet, shady street, in a perfectly fine Minneapolis Neighborhood!

John & Sylvia Sutherland of “The ZMM Book”: 18Potos Of Former Minneapolis Home>2649 South Colfax Ave, AFTER the 5 Albums Cones Up, Read & ClickOn 4th Down.

A 36 Photo Tour of Two University of South Carolina Buildings:  a) Etherredge Performing Arts Center Lobby + b) Ruth Patrick Science Education Center, some of which show “Built In Educational Displays

Site Master Henry Gurr's Campus: Photos Of Two Buildings (of 32 total), University of South Carolina Aiken. AFTER the 5 Albums Cones Up, Read & ClickOn 2nd Down.

A 105 Photo Tour of Science Building
At The University of South Carolina Aiken, Aiken SC.
Also showing a) Flowers & Exotic Plants In The Greenhouse
And b) The Rarely Seen Equipment Service Room & Dungeon.
Site Master Henry Gurr's Campus: Photos Of Science Building, One (of 32 total Buildings) At The University of South Carolina Aiken. AFTER the 5 Albums Comes Up, Read & ClickOn 5th Down.

IThese 15 photos show persons & scenes, related to how we got this ZMMQ WebSite going, back in ~2002. Included are "screen captures" of our software systems in use. A few of these photos show the screen views of what we were “looking at,” some including brief notes & hints on how to get around some of the problems we experienced.

Software We Used ~2002, In Creating and Maintaining This ZMMQ WebSite: Illustrated & Explained. AFTER the 5 Albums Cones Up, Read & ClickOn Top Albun.

Attach:ZmmqWikiThumbForWikiMenuLinkToMscFacPixPg2.jpg Δ
1947-60: Photos of MSC Faculty & Sarah Vinke (Vinki Vinche Finche Finch)


In Hawaiian WIKI MEANS => Quick N’ Easy N’ Better! For Anything You Do!!
Wikis began 1994, Ward Cunningham gave name "WikiWikiWeb"..Cont Heret
UP-TO-DATE INFORMATION & HOW TO USE pmWiki
The Pages You Are NOW Reading, Are Powered By pmWiki WebSite SftWare:


ZMMQ Site => Various UN-Complete Work In Process



Revised}DaveMatos130715+HenryGurr140227;16036;170214;180920;181127,200217,200312, 200318, 200831, 210626, 220508,220926,240209-12 , 240319-21, 240530, 240915, 241220.--]
File = WikiZmmq)MenuSidebar.CuzWantPreservPrev240914CpyFnServerServAgain01+FxNgLinks3.docx
PrevFile = WikiZmmq)MenuSidebar.CuzWantPreservPrev240914CpyFnServerServAgain01+FxNgLinks2.docx
PrevFile = WikiZmmq)MenuSidebar..BecuzPrevSvAsNg 240319CpyFnServer07)CpyFmServAgain01.docx
PrevFile = WikiZmmq)MenuSidebar..BecuzPrevSvAsNg 2403`9CpyFnServer07.docx
PrevFile = WikiZmmq)MenuSidebar..200217..210626..220508EdtSvd+Fx&AddLine13+Rev1.docx
File = WikiZmmq)MenuSidebar..200217..210626..220508EdtSvd+Fx&AddLine12.docx
PrevFile = WikiZmmq)MenuSidebar..200217..210626..220508EdtSvd,doc.Hsg02.docx
PrevFile = WikiZmmq)MenuSidebar..FaFaFa200217.06Fa200830Fa210626.Hsg01.doc




authors

PmWiki has built-in support for password-protecting various areas of the wiki site. Authors generally want to be able to apply passwords to individual pages or to wiki groups. Wiki Administrators can apply passwords to individual pages, to wiki groups, or to the entire site. Setting an edit password on a page or group (or the entire site) is one of the most common ways to stop spam. As with any access control system, the password protection mechanisms described here are only a small part of overall system and wiki security.

As an author editing pages...

An author will generally set 3 types of passwords:

  1. to control who can see a page or group, use read passwords
  2. to control who can edit a page or group, use edit passwords
  3. to control who can alter the passwords used to protect a page or group, use attr passwords

If required most page actions can be password protected.

Protect an individual page

To set a password on an individual wiki page, add the page action

?action=attr

to the page's URL (address) to access its attributes. Using the form on the attributes page, you can set or clear the read, edit, or attr passwords on the page. In the form you enter the passwords as cleartext; PmWiki encrypts them for you automatically when it stores them.

Additional options:

  • Leaving a field blank will leave the attribute unchanged.
  • To remove a password from a page (reverting back to the group's or site's default), enter
    clear
  • To indicate that the page can be edited even if a group or site password is set, enter
    @nopass
  • To lock a page for everybody but the admin, enter
    @lock
  • To assign the site's site-wide passwords to the read, edit, or attr password for the page, enter
    @_site_edit, @_site_read or @_site_upload

Protect a wiki group of pages

To set a password on a wiki group is slightly more difficult -- you just set the passwords on a special page? in each group called

First, you can get to the attributes page for GroupAttributes by entering a URL (address) like

http://example.com/pmwiki/pmwiki.php?n=GroupName.GroupAttributes?action=attr

Replace example.com with your domain name, and GroupName with the name of the group

Then, using the form on the attributes page, you can set or clear the read, edit, or attr passwords for the entire group. In the form you enter the passwords as cleartext; PmWiki encrypts them for you automatically.

Additional options:

  • To remove a password from a group (reverting back to the site's default), enter
    clear
  • To indicate that the group can be edited even if a site password is set, enter
    @nopass
  • To lock a group for everybody but the admin, enter
    @lock
  • (Beginning with Ver 2.2.3) To assign the site's site-wide passwords to the read, edit, or attr password for the group, enter
    @_site_edit, @_site_read or @_site_upload

Passwords

Passwords may consist of any combination of characters, except double "quotes" or 'apostrophes'.
Passwords with spaces or colons must be entered using quotes, eg "foo bar" or "foo:bar".
Obviously longer is better, and on some systems passwords need to have 4 or more characters.

Multiple passwords

Multiple passwords for a page, group or site are allowed.
Simply enter multiple passwords separated by a space. This allows you to have a read password, a write password, and have the write password allow read/write access. In other words, if the read password is

alpha

and the edit password is

beta

then enter

Set new read password: alpha beta
Set new edit password: beta

This says that either

alpha

or

beta

can be used to read pages, but only

beta

may edit. Since PmWiki checks the passwords you've entered since the browser has been opened, entering a read password that is also a write password allows both reading and writing.

Protect the site

Passwords can be applied to the entire wiki website in config.php.
See passwords administration for details.

administrator

As an administrator ...

You can set passwords on pages and groups exactly as described above for authors. You can also:

  1. set site-wide passwords for pages and groups that do not have passwords
  2. use attr passwords to control who is able to set passwords on pages
  3. use upload passwords to control access to the file upload capabilities (if uploads are enabled)
  4. use an admin password to override the passwords set for any individual page or group
  5. use SiteAdmin.AuthList to view the permissions settings for pages that have permissions set.

For more information on password options available to administrators, see PasswordsAdmin.

Which password wins?

In PmWiki, page passwords override group passwords, group passwords override the default passwords, and the admin password overrides all passwords. This gives a great deal of flexibility in controlling access to wiki pages in PmWiki.

The special page? SiteAdmin.AuthList is a page list of all pages with access permissions set.

Opening access to pages in protected groups/sites

Sometimes we want to "unprotect" pages in a group or site that is otherwise protected. In these cases, the special password

@nopass

is used to indicate that access should be allowed to a page without requiring a password.

For example, suppose Main.GroupAttributes has an edit password set, thus restricting the editing of all pages in Main. Now we want Main.WikiSandbox to be editable without a password. Using

clear

for the edit password for Main.WikiSandbox doesn't unprotect the page, because the password is being set by the group. Instead, we set the edit password for Main.WikiSandbox to the special value

@nopass

which tells PmWiki to ignore any site-wide or group-level passwords for that page.

How can I password protect all the pages and groups on my site? Do I really have to set passwords page by page, or group by group?

Administrators can set passwords for the entire site by editing the config.php file; they don't have to set passwords for each page or group. For example, to set the entire site to be editable only by those who know an "edit" password, an administrator can add a line like the following to local/config.php:

$DefaultPasswords['edit'] = pmcrypt('edit_password');

For more information about the password options that are available only to administrators, see PasswordsAdmin.

I get http error 500 "Internal Server Error" when I try to log in. What's wrong?

This can happen if the encrypted passwords are not created on the web server that hosts the PmWiki.
The PHP crypt() function changed during the PHP development, e.g. a password encrypted with PHP 5.2 can not be decrypted in PHP 5.1, but PHP 5.2 can decrypt passwords created by PHP 5.1.
This situation normally happens if you prepare everything on your local machine with the latest PHP version and you upload the passwords to a webserver which is running an older version.
The same error occurs when you add encrypted passwords to local/config.php.

Solution: Create the passwords on the system with the oldest PHP version and use them on all other systems.

How can I create private groups for users, so that each user can edit pages in their group, but no one else (other than the admin) can?

Modify the edit attribute for each group to id:username, e.g. set the edit attribute in JaneDoe.GroupAttributes to id:JaneDoe.

There is a more automatic solution, but it's probably not a good idea for most wikis. Administrators can use the AuthUser recipe and add the following few lines to their local/config.php file to set this up:

$group = FmtPageName('$Group', $pagename);
$DefaultPasswords['edit'] = 'id:'.$group;
include_once("$FarmD/scripts/authuser.php"); 

This automatically gives edit rights to a group to every user who has the same user name as the group name. Unfortunately it also gives edit rights to such a user who is visiting a same-named group not just for pages in that group, but for any page on the wiki that relies on the site's default edit password. This can create security holes.

How come when I switch to another wiki within a farm, I keep my same authorization?

PmWiki uses PHP sessions to keep track of authentication/authorization information, and by default PHP sets things up such that all interactions with the same server are considered part of the same session.
For security considerations about shared session pools, see the "Session injection" chapter in Cookbook:SessionSecurityAdvice.
To fix the browser-side convenience issue, one easy way is to make sure each wiki uses a different cookie name for its session identifier. Near the top of one of the wiki's local/config.php files, before calling authuser or any other recipes, add a line like:

session_name('XYZSESSID');

You can pick any alphanumeric name for XYZSESSID; for example, for the cs559-1 wiki you might choose

session_name('CS559SESSID');

This will keep the two wikis' session cookies independent of each other.

Is it possible to test the password level for display and/or if condition? Example: * (:if WriterPassword:) (display Edit link) (:ifend:)

You can use (:if auth edit:). See ConditionalMarkup.

Can I use (:if …:) to hide secrets in a wiki page?

You can, but usually that's not secure.
The recommended strategy is to put secrets in a separate page and restrict all read-related¹ access permissions to those users who are allowed to read the secrets.
To display the secrets in another page, you can include (parts of) the secrets page:
Users with read access to the secrets will readily see them, whereas other users see nothing or (at your choosing) some other text, e.g. a login link.

¹ Currently (version 2.2.99), these are: read (would allow include), edit (would show the source), attr (would allow to obtain read/edit), diff (would allow viewing any change), source (allows raw source display)

The reason why Conditional Markup isn't suitable for access control is that it only applies for rendering wikitext as a web page, and that's just one of many ways to access a page's text.
In order to rely on Conditional Markup for protection of secrets, you'd have to restrict all access methods that can circumvent it.
To do so, you'd need to keep track of all methods available.
In a default installation of PmWiki, some of the easy methods include: Editing a page, viewing its edit history, its source, or including fragments of it into the edit preview of another page. (Preview: To avoid traces in RecentChanges.)
However, this list is far from exhaustive, and could easily grow with Recipes? or future versions of PmWiki.



This page may have a more recent version on pmwiki.org: PmWiki:Passwords, and a talk page: PmWiki:Passwords-Talk.

Recent Changes (All) | Edit Sidebar | Wiki Help | Page History | Edit Page Powered by PmWiki