Re: wotaskd and ssh
Paul Hoadley <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.wonder-disc |
|---|---|
| Message-ID | <[email protected]> |
On 23/02/2013, at 10:56 PM, Pascal Robert <[email protected]> wrote: > Le 2013-02-22 à 23:58, Paul Hoadley <[email protected]> a écrit : > >> I objected last time this came up (though I don't remember being the only one). I'm just against changing the _default_ behaviour of a long-standing, central piece of software like this. I guess it _is_ ideological, yes. Of course I have a firewall between wotaskd and the internet, it's just the principle—someone might have some bizarro configuration we haven't thought of, and this might bite them. > > If we follow that logic, that means we will never add new features into wotaskd. That does not follow at all. Maybe we need to pause right here—you understand that my only objection is to _enabling it by default_, right? > It's not changing the behaviour Sure it is... > it's opening a new TCP port. Exactly. > That built-in SSH server is the first step for easy deployment from Jenkins and from WOLips. Yeah, probably that people with existing "complex" deployment workflow won't use it. Again, you seem to be mis-characterising my position as against _the feature_. I'm not. I just don't think it should be enabled by default. > But I could settle that it's off by default Great! That's all I've ever been suggesting. -- Paul Hoadley http://logicsquad.net/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Wonder-disc mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wonder-disc