lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140617141455.6d756370@ultegra>
Date:	Tue, 17 Jun 2014 14:14:55 -0700
From:	Jacob Pan <jacob.jun.pan@...ux.intel.com>
To:	Neil Horman <nhorman@...driver.com>
Cc:	linux-kernel@...r.kernel.org, Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH 2/2] tmon: set umask to a reasonable value

On Tue, 17 Jun 2014 16:05:09 -0400
Neil Horman <nhorman@...driver.com> wrote:

> current, the tmon umask value is set to 0, which mean whatever the
Currently, ..., which means ...
> permission mask in the shell are when starting tmon in daemon mode
> are what the permissions of any created files will be.  We should
> likely set something more explicit, so lets go with the usual 022
> 
Just some grammar suggestion. Otherwise,
Acked-by: Jacob Pan <jacob.jun.pan@...ux.intel.com>

> Signed-off-by: Neil Horman <nhorman@...driver.com>
> CC: Zhang Rui <rui.zhang@...el.com>
> CC: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> ---
>  tools/thermal/tmon/tmon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/thermal/tmon/tmon.c b/tools/thermal/tmon/tmon.c
> index 059e0be..09b7c32 100644
> --- a/tools/thermal/tmon/tmon.c
> +++ b/tools/thermal/tmon/tmon.c
> @@ -355,7 +355,7 @@ static void start_daemon_mode()
>  	disable_tui();
>  
>  	/* change the file mode mask */
> -	umask(0);
> +	umask(S_IWGRP | S_IWOTH);
>  
>  	/* new SID for the daemon process */
>  	sid = setsid();

[Jacob Pan]

-- 
Thanks,

Jacob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ