search for: wherewithal

...really NOT helpful... > I searched two days long how can I check it and didn't found anything > useful... > > Could someone suggest me a way to check if my Asterisk is an "Open > Relay" that accept connections from every peer? Someone on this list is bound to have the wherewithal to be able to do that. All they will need to know is the IP address of your Asterisk server. I suggest that if anyone offers to help you by remotely penetration-testing your system, you post "on-list" that you'll contact them "off-list" to give them the server IP. That...

...gt;> I searched two days long how can I check it and didn't found anything >> useful... >> >> Could someone suggest me a way to check if my Asterisk is an "Open >> Relay" that accept connections from every peer? > Someone on this list is bound to have the wherewithal to be able to do that. > All they will need to know is the IP address of your Asterisk server. > > I suggest that if anyone offers to help you by remotely penetration-testing > your system, you post "on-list" that you'll contact them "off-list" to give > them...

2015-06-08 22:35 GMT+02:00 D'Arcy J.M. Cain <darcy at vex.net>: > On Mon, 8 Jun 2015 22:24:33 +0200 > Luca Bertoncello <lucabert at lucabert.de> wrote: > > Kevin Larsen <kevin.larsen at pioneerballoon.com> schrieb: > > > Basically, they are hoping that you are running the equivalent of a > > > mail server open relay. They are trying to use you

Hello, Our campus environment would find it very useful to pass user- environment variables for certain login ssh connections, but of course want to avoid the security problems with LD_PRELOAD and PermitUserEnvironment as described in sshd_config manpages. Would the best answer be a patch that adds PermitUserEnvironment support inside match blocks? Are there technical or other reasons

> To be clear, I'm not against moving the version up, I just want to > make sure that people understand that this is not *just* a version > upgrade, but a development philosophy move for all Linux developers > and production environments (of which we have plenty). This move was > proposed before and was rejected for the reasons I pointed out: > maintenance. Yes. It is a move

...back to my analogy: we require a relatively modern C++ compiler (in fact, it is past due to update our requirements there....). The reason is that if you are building a compiler from source, it seems entirely reasonable to expect you to either use a relatively modern OS environment, or to have the wherewithal to bootstrap things using one of the numerous options available. Adding CMake to the potential set of things you need to bootstrap seems like an extremely small incremental burden compared to that of getting a modern C++ toolchain. (Although clearly they won't always both be required in the sam...

ocaml-augeas is used only by virtlibguestfs, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): Bundle the ocaml-augeas library for use by libguestfs build: switch embedded copy of ocaml-augeas .gitignore | 1 + 3rdparty/ocaml-augeas/COPYING.LIB | 515

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *