SAFE Network Dev Update - April 25, 2019

I have tested the safe_auth CLI on the community network and it also works on this network. Example session here:

# Compile from source (in safe-authenticator-cli directory):
$ cargo build
    Finished dev [unoptimized + debuginfo] target(s) in 0.49s

# Go to the generated directory:
$ cd target/debug

# Download crust config file for community network and rename it for safe_auth application:
$ curl -L https://raw.githubusercontent.com/Thierry61/tfa_safenetwork/master/clients/SAFE%20Browser.crust.config -o safe_auth.crust.config
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   385  100   385    0     0   1915      0 --:--:-- --:--:-- --:--:--  1915

# Export environmement variables for account credentials:
$ export SAFE_AUTH_SECRET SAFE_AUTH_PASSWORD

# Enter account credentials:
$ read -s -p "Secret: " SAFE_AUTH_SECRET; echo
Secret:
$ read -s -p "Password: " SAFE_AUTH_PASSWORD; echo
Password:

# Launch CLI application to get PUT balance and list authorized apps:
$ ./safe_auth -aby
Logged in the SAFE Network successfully!
Account's current balance (PUTs done/available): 57/943
+-----------------------------------------+---------------------+------------------+-----------------------------------------------------------------------------------+
| Authorised Applications                 |                     |                  |                                                                                   |
+-----------------------------------------+---------------------+------------------+-----------------------------------------------------------------------------------+
| Id                                      | Name                | Vendor           | Permissions                                                                       |
+-----------------------------------------+---------------------+------------------+-----------------------------------------------------------------------------------+
| net.maidsafe.safe-browser               | SAFE Browser        | Maidsafe.net Ltd | _public: {Read, Insert, Update, Delete}                                           |
|                                         |                     |                  | apps/net.maidsafe.safe-browser: {Read, Insert, Update, Delete, ManagePermissions} |
+-----------------------------------------+---------------------+------------------+-----------------------------------------------------------------------------------+
| net.maidsafe.examples.webhostingmanager | Web Hosting Manager | MaidSafe         | _publicNames: {Read, Insert, Update, Delete}                                      |
|                                         |                     |                  | _public: {Read, Insert, Update, Delete}                                           |
+-----------------------------------------+---------------------+------------------+-----------------------------------------------------------------------------------+

The procedure should work on any network (Alpha 2 or local network). Just copy the SAFE Browser.crust.config file of an operational SAFE Browser for your network and rename it to safe_auth.crust.config.

21 Likes