I hereby claim:
- I am trel on github.
- I am trel (https://keybase.io/trel) on keybase.
- I have a public key whose fingerprint is 004A FE7A 693A 5C46 78BA A5CD E33D 0FEF 7ABE 43CF
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
{ | |
"irods_client_server_negotiation": "request_server_negotiation", | |
"irods_client_server_policy": "CS_NEG_REFUSE", | |
"irods_cwd": "/tempZone/home/rods", | |
"irods_default_hash_scheme": "SHA256", | |
"irods_default_number_of_transfer_threads": 4, | |
"irods_default_resource": "demoResc", | |
"irods_encryption_algorithm": "AES-256-CBC", | |
"irods_encryption_key_size": 32, | |
"irods_encryption_num_hash_rounds": 16, |
News / August 2018
Administrators and users of iRODS have, for a long time, found its rule engine and associated rule language a valuable tool for customizing their systems' data policy, workflows, and other data management needs. Whether you are configuring a specific Policy Enforcement Point (PEP) with a series of actions to respond to iRODS system events, or writing an application more specific to your iRODS Zone, the process of authoring rules sometimes demands a knowledge of certain techniques and