
Administrator
Medecins Sans Frontieres Argentina
with the translation Spanish-English of the module and with the up-to-date upgrade of the modules e.g. peer to peer and campaigning


End-user
EFF
The CiviCRM community has been a tremendous resource for new ideas and helping us solve problems. We are excited to contribute customizations EFF makes back to core and support new features such as batch entry for offline donations or multiple payment processors on one donation form.


Developer, Implementor
Web Access India Pvt. Ltd.
I have been part of CiviCRM project from the beginning and feels great to see how it has grown over the years.
I am glad to be associated with such a wonderful open source project and an awesome community around it.


Implementor, Developper
cividesk
The community around CiviCRM is international, multicultural, friendly, sometime opinionated but always respectful and welcoming new ideas. It is a real pleasure to interact with these people - but see for yourself: dive in and ask your first question on the forums!
We thoroughly appreciate CiviCRM as a software and this community, and when helping our customers implement and make the best of CiviCRM we are always looking for ways to contribute back.

Trainer
Emphanos
As a CiviCRM trainer and implementer CiviCRM provides a great solution that allows Emphanos to help NGOs improve their ability to reach out and spread their messages.


Implementator, Developer


Implementor, Developer
Pogstone, Inc.
I have been involved in the CiviCRM community for over 5 years, and enjoy implementing and programming CiviCRM for a variety of non-profits. I have been amazed at the rapid pace of innovation delivered with each new release, and CiviCRM's flexibility in being able to accommodate a variety of requirements. I have learned a lot about CiviCRM by participating in CiviCon, online forums, and CiviCRM book sprint.


DEVELOPER AND IMPLEMENTER


Administrator, Implementator, Developer, End-user
Freeform Solutions
Freeform Solutions uses CiviCRM for our internal CRM. We are also a NFP IT support organization and we implement CiviCRM for NFP organizations we work for because we find that CiviCRM is the best open source CRM out there.


End-user, Administrator, Implementor
ZING
We feel there are too many obstacles facing not-for-profits (NFPs) considering commercial CRM offerings, including many of those that are charity oriented. From licensing models which restrict the fluid expansion of an organisation's user base (why should you be punished with higher costs for being successful?), to support from commercial companies being inherently tied to one supplier; a NFP would benefit from the option to 'shop around' for those most appropriate, e.g. based on: proximity and availability on-site, cost, experience, value added services... They also often lack the capacity for charity relevant workflows, necessitating either customisations, complicated and inefficient workarounds or an en-masse call for new functionality, as individual charities do not appear to carry the weight required to influence subtle NFP-only changes to market leading software, without large expense.
On the flip side, CiviCRM is completely free and open-source, carrying with it a friendly, hard-working and enthusiastic community of developers and implementers, constantly listening to the users' needs and sculpting future releases to the requirements of NFP organisations. This is exciting!


implementor, administrator
AGH Strategies
We help nonprofits make the best use of their data to further their mission.


Implementor, Developer
Unitarian Universalist Church of Lancaster
Contact management, email marketing/management and web site integration.

Comments
Issue has been created
I've opened a complimentary issue.
I've wondered the same thing
I've wondered the same thing myself. Requiring the password on the command-line is a security minus rather than a security plus. As you've said, if you have access to the config file then you have database access...
Skip it
That's a no brainer, asking the password (on the cli) doesn't increase security, quite the contrary.
What ssh and phplist do is to have a whitelist of users that are allowed to run the cron. Not sure it adds anything but (sshd_config) you have:
AllowUsers bob cronjob whatever and if you want to run it as jammie it will block. I'm assuming the rationale would be that I can't create activities or what else as dlobo or dgg, only as the "technical" cronjob user(s) listed there
Don't have any opinion about it, beside yes, get rid of the mandatory password on the cli
X+
Thumbs up
It would be great to get that added. I'd also really like it if it could get triggered directly from Drupal's cron system, as it seems weird that I need to be running 2 separate updaters for the same site.
Url: