I think i got what wjm means "not safety", usually, we will add an
disclaimer at the feature in this situation, something like,
when setting port to 0, the port will be random assigned , the
security-related matters introduced by this are the responsibility of the
user.
Best Regards,
---
Zen Lin
for some production, they must provide communication matrix to final
customers before deploy software.
but in this time they DO NOT use port 0 feature just no problem.
so it's a false proposition
but to debate this problem with those peoples will waste a lot of time..
2018-07-13 10:34
The "not safety" explain doesn't make sense.
With the help of service-center, we can find out the port finally.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Jul 13, 2018 at 10:11 AM, wjm wjm wrote:
> in fact, customer not set port to 0 means disable it, i don't think we need
> a
in fact, customer not set port to 0 means disable it, i don't think we need
a option.
"not safety" means, if customer set port to 0, they can not know which port
will be used
sigh, so strange..
2018-07-13 9:46 GMT+08:00 Willem Jiang :
> Can we add an option for it?
> In this way we can
Can we add an option for it?
In this way we can disable it when there is security issue we need to take
care.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Jul 13, 2018 at 9:34 AM, Kirin Wang wrote:
> +1 ，
> I think is a good feature,
> @wjm Could you provide more information
+1 ，
I think is a good feature,
@wjm Could you provide more information about the safety issue? that is
a interesting topic.
wjm wjm 于2018年7月13日周五 上午9:30写道：
> +1
>
> when cse project start, i implement this feature, but teams said that is
> not safe..
> at last we delete the feature.
>
+1
when cse project start, i implement this feature, but teams said that is
not safe..
at last we delete the feature.
2018-07-13 9:23 GMT+08:00 郑扬勇 :
> Hi:
> Like spring-boot server.port=0, Java Chassis can support random port:
>
> servicecomb:
> rest:
> address: 0.0.0.0:0
>
