| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates: lberk/marko merges, build+docs updates |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 5 Jan 2016 17:27:55 -0500 (EST) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <y0mio37n8i3.fsf@xxxxxxxx> |
| References: | <805278639.3777112.1451891182627.JavaMail.zimbra@xxxxxxxxxx> <780203978.3777208.1451891272970.JavaMail.zimbra@xxxxxxxxxx> <y0mio37n8i3.fsf@xxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | Bbt2y8H5MgvKNu+vtm8GNyaJkc5vwA== |
| Thread-topic: | pcp updates: lberk/marko merges, build+docs updates |
(repeating the same thing over and over isn't going to change anything, so here's my final reply on this topic too...) ----- Original Message ----- > > Reinstate notes about pmwebd -P option being deprecated, > > [...] it has perfectly safe & legimitate [sic] uses, [...] I've not seen a realistic case for elevating remote privileges and circumventing the pmcd/DSO authentication model in this way, just for webapps. The existing, selective dropping of barriers on the server side (ala pmdaproc) is a more sensible approach, suiting both PMWEBAPI and PMAPI clients. Since there's no real need for this little hole to remain in the long-term, even as opt-in, I think marking it as deprecated does convey the situation well. Let's move on, thanks. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Overly chatty XXX/TODO comments in PCP code, Nathan Scott |
|---|---|
| Next by Date: | Re: pcp updates: lberk/marko merges, build+docs updates, Frank Ch. Eigler |
| Previous by Thread: | Re: pcp updates: lberk/marko merges, build+docs updates, Frank Ch. Eigler |
| Next by Thread: | Re: pcp updates: lberk/marko merges, build+docs updates, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |