?????? [DISCUSS]Shall Java Chassis support random port
For security reasons, we should listen as less network interface as possible. So we make this design to listen only one network address. For users want this feature, it's really save a lot of time for them to configure ip address. I remember this is the original security reasons for 0.0.0.0 to listen only one address. However, we still follow the common ways, 0.0.0.0 to listen all possible network interface, and user have to configure the target network interface if they want only listen one network interface. This problem regarding to random port, it is only hard to give port matrix to configure fire wall, and it's a option of users. I think we can provide this feature. -- -- ??: "wjm wjm"; : 2018??7??13??(??) 10:54 ??: "dev"; : Re: [DISCUSS]Shall Java Chassis support random port 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 GMT+08:00 Willem Jiang : > 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 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 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 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. > > > > > > > > > > 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 > > > > > > highway: > > > > > > address: 0.0.0.0:0 > > > > > > > > > > > > Best Regards & Thanks! > > > > > > > > > > > > > > >
Re: [DISCUSS]Shall Java Chassis support random port
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 zenlintechnofr...@gmail.com Focused on Micro Service and Apache ServiceComb wjm wjm 于2018年7月13日周五 上午10:54写道: > 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 GMT+08:00 Willem Jiang : > > > 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 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 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 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. > > > > > > > > > > > > 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 > > > > > > > highway: > > > > > > > address: 0.0.0.0:0 > > > > > > > > > > > > > > Best Regards & Thanks! > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS]Shall Java Chassis support random port
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 GMT+08:00 Willem Jiang : > 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 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 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 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. > > > > > > > > > > 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 > > > > > > highway: > > > > > > address: 0.0.0.0:0 > > > > > > > > > > > > Best Regards & Thanks! > > > > > > > > > > > > > > >
Re: [DISCUSS]Shall Java Chassis support random port
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 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 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 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. > > > > > > > > 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 > > > > > highway: > > > > > address: 0.0.0.0:0 > > > > > > > > > > Best Regards & Thanks! > > > > > > > > > >
Re: [DISCUSS]Shall Java Chassis support random port
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 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 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. > > > > > > 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 > > > > highway: > > > > address: 0.0.0.0:0 > > > > > > > > Best Regards & Thanks! > > > > > >
Re: [DISCUSS]Shall Java Chassis support random port
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 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. > > > > 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 > > > highway: > > > address: 0.0.0.0:0 > > > > > > Best Regards & Thanks! > > >
Re: [DISCUSS]Shall Java Chassis support random port
+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. > > 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 > > highway: > > address: 0.0.0.0:0 > > > > Best Regards & Thanks! >
Re: [DISCUSS]Shall Java Chassis support random port
+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 > highway: > address: 0.0.0.0:0 > > Best Regards & Thanks!
[DISCUSS]Shall Java Chassis support random port
Hi: Like spring-boot server.port=0, Java Chassis can support random port: servicecomb: rest: address: 0.0.0.0:0 highway: address: 0.0.0.0:0 Best Regards & Thanks!