bugGNU Health - Bugs: bug #52020, Missing bcrypt dependency in...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #52020: Missing bcrypt dependency in gnuhealth-setup

Submitter:  Luis Falcon <meanmicio>
Submitted:  Thu 14 Sep 2017 04:07:22 PM UTC
   
 
Category:  Security Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Fixed Privacy:  Public
Assigned to:  meanmicio Open/Closed:  Closed
Release:  3.2.0 Module:  gnuhealth-setup
Component:  None

Discussion

Thu 14 Sep 2017 04:15:30 PM UTC, comment #1: 

Fixed on changeset 2765:a7f3aa138162

Luis Falcon <meanmicio>
Group administrator
Thu 14 Sep 2017 04:07:22 PM UTC, original submission:  

Mathias Behrle noticed that the standard installation for GNU Health (gnuhealth-setup), is missing the bcrypt package.

Although Tryton fallbacks to SHA1 algorithm for hashing the passwords if it does not find bcrypt, we recommend to use Bcrypt.

Bcrypt is a "slow" hash algorithm, thus, makes it harder (from the time point of view) to brute force attacks, and the penalty from the login user is not noticeable (specially across the network).

We will release a new version for gnuhealth-setup (3.2.1), which will include bcrypt in the dependency list.

In the meantime, just install the bcrypt package manually with the gnuhealth user

gnuhealth $ pip3 install --user bcrypt

Don't forget to restart (no need to update) the Tryton server.

PS: This applies just to the standard / vanilla GNU Health distribution. Those installations that use pypi packages have already the dependency in place.

Bests
Luis


Luis Falcon <meanmicio>
Group administrator

 

Attached Files

This item currently has no attached files.

 

Dependencies

This item does not depend on any other items.

No items depend on this one.

 

Mail Notification Carbon-Copy List

Carbon-Copy List
  • -email is unavailable- added by meanmicio (Submitted the item)
  •  

    Votes

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    History

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-09-14 meanmicio StatusConfirmed Fixed
        Open/ClosedOpen Closed
        ReleaseNone 3.2.0

    Back to the top

    Powered by Savane 3.16-1b88.
    Corresponding source code