Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Ralf Friedl
Matt Whitlock wrote: On Tuesday, 25 March 2014, at 10:52 pm, Cristian Ionescu-Idbohrn wrote: I find out that using that option: -x hostname:foo ^ shows up in /proc/pid/cmdline as: -x hostname foo ^ /proc/pid/cmdline reflects any changes

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Bernd Petrovitsch
On Mit, 2014-03-26 at 10:01 +0100, Ralf Friedl wrote: [] But the /proc/pid/cmdline interface doesn't convert null bytes to spaces. Doing so would lose information. Some programs may choose to do this conversion, but programs reading cmdline must be prepared for null bytes anyway. hex

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
On Wed, 26 Mar 2014, Ralf Friedl wrote: Matt Whitlock wrote: On Tuesday, 25 March 2014, at 10:52 pm, Cristian Ionescu-Idbohrn wrote: I find out that using that option: -x hostname:foo ^ shows up in /proc/pid/cmdline as: -x hostname foo ^

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Matt Whitlock
On Wednesday, 26 March 2014, at 12:46 pm, Cristian Ionescu-Idbohrn wrote: Is it possible to restrain from modifying the arguments for the command line? The problem is that the process watcher used here is dependant on having the original/unmodified /proc/pid/cmdline. If the watched process

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
On Wed, 26 Mar 2014, Matt Whitlock wrote: On Wednesday, 26 March 2014, at 12:46 pm, Cristian Ionescu-Idbohrn wrote: Is it possible to restrain from modifying the arguments for the command line? The problem is that the process watcher used here is dependant on having the original/unmodified

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Matt Whitlock
On Wednesday, 26 March 2014, at 1:19 pm, Cristian Ionescu-Idbohrn wrote: But really, this is not an `init' question, as I see it. It's about keeping the original/unmodified program arguments in /proc/pid/cmdline. I know of no other program doing such sort of thing, although I think I

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
On Wed, 26 Mar 2014, Matt Whitlock wrote: On Wednesday, 26 March 2014, at 1:19 pm, Cristian Ionescu-Idbohrn wrote: But really, this is not an `init' question, as I see it. It's about keeping the original/unmodified program arguments in /proc/pid/cmdline. I know of no other program

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Matt Whitlock
On Wednesday, 26 March 2014, at 1:38 pm, Cristian Ionescu-Idbohrn wrote: On Wed, 26 Mar 2014, Matt Whitlock wrote: Tons of programs modify their argv arrays. Alright, you know better. It's common for programs that accept sensitive information (such as passwords) via command-line arguments

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Denys Vlasenko
On Wed, Mar 26, 2014 at 12:46 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: My guess is also that udhcpcd does something like strchr(hostname, ':') = '\0'; I was suspecting something like that, but had difficulties to locate where in the code that is being done.

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
On Wed, 26 Mar 2014, Denys Vlasenko wrote: On Wed, Mar 26, 2014 at 12:46 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: My guess is also that udhcpcd does something like strchr(hostname, ':') = '\0'; I was suspecting something like that, but had difficulties

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Denys Vlasenko
On Wed, Mar 26, 2014 at 2:13 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: On Wed, 26 Mar 2014, Denys Vlasenko wrote: On Wed, Mar 26, 2014 at 12:46 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: My guess is also that udhcpcd does something like

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Bob Dunlop
Hi, As I've written in a previous message, I know nothing of such other programs, but I'd be intrested to learn more. Modifying argv[] has been around since V6 unix to my knowledge. Some games used to modify it so other users could see your score via ps etc. Some programs even had

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Laurent Bercot
Yes, there's still much to learn. Do you happen to know of some popular examples? A lot of long-running processes that spawn several children and assign different tasks to them will do this, for informative purposes. (I personally think that the argv of a process is not the right place for

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Michael Conrad
On 03/26/2014 09:13 AM, Cristian Ionescu-Idbohrn wrote: On Wed, 26 Mar 2014, Denys Vlasenko wrote: But how that respawn tool going to work with other programs? As I've written in a previous message, I know nothing of such other programs, but I'd be intrested to learn more. There is no

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
A big thanks to all of you guys. I now feel enlightened :) On Wed, 26 Mar 2014, Laurent Bercot wrote: Just off the top of my head: Now that you write it down: sshd (from openssh) I realize I knew about this one, all along. avahi-daemon dovecot and even among the good guys:

Re: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cristian Ionescu-Idbohrn
On Wed, 26 Mar 2014, Michael Conrad wrote: All mysql utilities overwrite passwords in cmdline as a security measure. http://dev.mysql.com/doc/refman/5.1/en/password-security-user.html Well, I recently learned there's some effort put in the linux kernel to help with that sort of thing. See:

RE: /proc/pid/cmdline and udhcpcd

2014-03-26 Thread Cathey, Jim
This long predates Linux. Some small percentage of programs rely upon being able to modify the argv array. This is especially valuable to programs that fork heavily but that do not exec. The individual tines may thus be labeled with their roles so that they can be identified in ps, for example.