Re: Re[2]: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-02 Thread Shishkov Ilya
Ok, and what's about other VM arguments, not included to IgniteSystemProperties? пт, 2 июл. 2021 г. в 09:27, Zhenya Stanilovsky : > > -1 for extra arg, +1 for Ivan`s upper proposal : @IgniteSystemProperty > annotation. > Look, someone will set some of IGNITE_* option and after possibly cluster >

Re[2]: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-02 Thread Zhenya Stanilovsky
-1 for extra arg, +1 for Ivan`s upper proposal : @IgniteSystemProperty annotation. Look, someone will set some of IGNITE_* option and after possibly cluster problems will give this logs into analysis and engineer can`t reproduce such a case, cause no param is applied.   >An extra argument for

Re: Re[2]: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Atri Sharma
AFAIK, this allows users to pass in custom VM options which may be undesirable. On Thu, Jul 1, 2021 at 12:07 PM Zhenya Stanilovsky wrote: > > > +1 for reverting, can anybody (possibly ticket starter?) explain how jvm > settings will rise some security problems ? > > > > >I suppose, that we

Re[2]: Setting IGNITE_TO_STRING_INCLUDE_SENSITIVE=false prevents VM Arguments output

2021-07-01 Thread Zhenya Stanilovsky
+1 for reverting, can anybody (possibly ticket starter?) explain how jvm settings will rise some security problems ?   >I suppose, that we should revert this particular line. I don't understand >who ever considers vm options as sensitive info. > >ср, 30 июн. 2021 г., 22:52 Shishkov Ilya <