Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 Oct 2015 at 11:58 UTC
Updated:
27 Apr 2016 at 20:41 UTC
Jump to comment: Most recent
Comments
Comment #2
sajithathukorala commentedComment #3
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #4
Anatolii88 commentedHi @SajithAthukorala. Thank you for contribution. there are some minor issues on automated test service.
http://pareview.sh/pareview/httpgitdrupalorgsandboxsajithathukorala25803...
It should be easy to fix.
Manual Review
Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
List of identified issues:
- Can you implement hook_help() for your module so it would be easy for the users to find help page for your module.
Also integrate your README.txt file in hook_help().
- It would be good to use hook_permission() too.
- There are some errors in .js file, those are not a reason to block the project application but it would be better to fix.
- Is there some configuration page to your module? admin/modules/easy-installer - this link doesn't work on my local site.
Thank you!
This review uses the Project Application Review Template.
Comment #5
rahulbaisanemca commentedHi SajithAthukorala, Thanks for contribution to community, kindly add hook_help in this format.
https://www.drupal.org/node/161085
Comment #6
sajithathukorala commentedHi @anatolii88,
Thank you for reviewing module. I just updated the code with your issues
-Added hook_help and integrate README.txt with it.
-Added hook_permission with new permission.
-Solved all the js errors which showed by eslint on pareview.sh.
-There are no configuration page for this module, when you access "/admin/modules/easy-installer" page it will crawl the drupal.org contribute module page and display them on data tables. This process take 15-20 seconds for the first time.Can you please check with the cache
Thank You !!!
Comment #7
rakesh.gectcrManual Review:
@SajithAthukorala
Thanks for the module . Looks ok for me.
configure = /admin/modules/easy-installerComment #8
sajithathukorala commented@rahulbaisanemca - thank you for your reply
@rakesh.gectcr -
Thank you for your reply and ideas. really appreciate it.
Comment #9
prashant.c@SajithAthukorala
Avoid using files from remote URLs:
drupal_add_js('https://code.jquery.com/jquery-1.11.3.min.js', 'external');
drupal_add_js('https://cdn.datatables.net/1.10.9/js/jquery.dataTables.min.js', 'external');
drupal_add_js('https://cdnjs.cloudflare.com/ajax/libs/pace/1.0.2/pace.js', 'external');
drupal_add_js('https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js', 'external');
drupal_add_css('http://cdn.datatables.net/1.10.9/css/jquery.dataTables.min.css', 'external');
Comment #10
sajithathukorala commentedHi @prashant.c
Thank you for reviewing module. I removed all the remote URLs . Now module requires jquery update module,and users have to add data table package and pace.js manually into module (more info added in README.txt).
Thank You.
Comment #11
mimran commentedHi looks fine for me
Comment #12
sajithathukorala commentedComment #13
sajithathukorala commentedSorry My mistake , I have mistakenly update the issue , Revert back to previous state,
Comment #14
tessa bakkerHi SajithAthukorala,
I can see why you developed this module, but after looking into your code this shouldn't be promoted to a project.
The reason for that is, that your module could be fun for prototyping a website, but has many security issues.
If you look at the Drupal core's Update Module, you can see that there is a special 'access callback' named 'update_manager_access' to check if someone can install a new module, also there are many more functions in Update to make sure nothing goes wrong while installing a new module.
Also many servers don't allow the function 'exec' because of many security risks. Using this with Drush (also not possible on many servers for user: www-data) this isn't the way to go.
To make this module work I would suggest the following:
Instead of downloading en installing a module in the most unsecure way, let the Update Module do this for you.
Find a way to send the modules Tar url to the Update form, let the user than decide to start the installation process and this could be a very handy module.
Also make use of the same 'access callback' as the Update Module for your pages.
Comment #15
sajithathukorala commentedHi Tessa,
Thank you for reviewing my module and your suggestions, I really appreciate it, I will look into that solution and will update the code , Thanks again.
Comment #16
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #17
klausiAdding the security tag to indicate that a security issue was found here. And please don't remove the security tag, we keep that for statistics and to show examples of security problems.