SELECT config_value FROM ctp_configWHERE config_item = 'encrypt_data' AND config_category = 'system_switch';
{"encryptMode": 1,"encryptModules": [{"moduleId": 1,"encryptAction": {"userPassword": "enable","attachment": "middle","text": "disable","secrecy": null,"appLog": "disable","signatureData": null,"salary": null,"officePhone": null,"cellPhone": null,"email": null,"homeAddress": null,"socialSecurityAccount": null,"idcard": null}}, {"moduleId": 2,"encryptAction": {"userPassword": null,"attachment": null,"text": null,"secrecy": null,"appLog": null,"signatureData": null,"salary": "enable","officePhone": "disable","cellPhone": "disable","email": "disable","homeAddress": null,"socialSecurityAccount": null,"idcard": "disable"}}, {"moduleId": 3,"encryptAction": {"userPassword": null,"attachment": null,"text": null,"secrecy": null,"appLog": null,"signatureData": "disable","salary": null,"officePhone": null,"cellPhone": null,"email": null,"homeAddress": null,"socialSecurityAccount": null,"idcard": null}}],"encryptModeEnums": [1, 2, 3]}
select config_value from ctp_config where config_item = 'action_algorithm_map' and config_category='system_switch';[{"key": "1","actionMap": {"ENCRYPT_EMAIL": "SYS_AES","ENCRYPT_ATTACHMENT": "SYS_AES","ENCRYPT_APP_LOG": "SYS_AES","ENCRYPT_ID_CARD": "SYS_AES","ENCRYPT_OFFICE_PHONE": "SYS_AES","ENCRYPT_CELL_PHONE": "SYS_AES","ENCRYPT_PWD": "SYS_SHA256","ENCRYPT_SALARY": "SYS_NUMBER","ENCRYPT_TEXT": "SYS_AES","SIGNATURE_DATA": "SYS_SHA256"}}, {"key": "2","actionMap": {"ENCRYPT_EMAIL": "SYS_SM4_V_3","ENCRYPT_ATTACHMENT": "SYS_SM4_V_3","ENCRYPT_APP_LOG": "SYS_SM4_V_3","ENCRYPT_ID_CARD": "SYS_SM4_V_3","ENCRYPT_OFFICE_PHONE": "SYS_SM4_V_3","ENCRYPT_CELL_PHONE": "SYS_SM4_V_3","ENCRYPT_PWD": "SYS_SM3","ENCRYPT_SALARY": "SYS_NUMBER","ENCRYPT_TEXT": "SYS_SM4_V_3","SIGNATURE_DATA": "SYS_SM3"}}, {"key": "sansecJCE","actionMap": {"ENCRYPT_EMAIL": "SAN_SM4","ENCRYPT_ATTACHMENT": "SAN_SM4","ENCRYPT_APP_LOG": "SAN_SM4","ENCRYPT_ID_CARD": "SAN_SM4","ENCRYPT_OFFICE_PHONE": "SAN_SM4","ENCRYPT_CELL_PHONE": "SAN_SM4","ENCRYPT_PWD": "SAN_SM3","ENCRYPT_SALARY": "SYS_NUMBER","ENCRYPT_TEXT": "SAN_SM4","SIGNATURE_DATA": "SAN_SM3"}}]
|
|
|
|
|
|
|
|
|
|
|
|
|
（三未信安） |
|
|
// SHA-256加密（默认）new EncryptCoderSha256().signature("明文密码", "登录账号名");// SM3国密加密new EncryptCoderSm3Impl().signature("明文密码", "登录账号名");// 三未信安SM3加密new EncryptCoderSansecSM3Impl().signature("明文密码", "登录账号名");
但是，又有一个问题，有些邪恶的人会使用知道人的账号提前去登录别人的账号，导致信息泄露等。可以开发更新后将密码通过短信或者邮箱等方式发送给对方，各自的密码使用脚本批量初始化生成好安全的密码即可。
当然，也可以参考seeyon-ctp-core.jar中的加密算法实现，来自定义实现加密算法，也是可以的。
2、强制使用复杂密码策略，避免弱密码风险；
3、结合多因素认证（MFA），如短信验证码、动态令牌等。
原文始发于微信公众号（OA大助手）：原来致远OA的登录密码是这么玩的呀，快看看你能找到规律吗？
免责声明:文章中涉及的程序(方法)可能带有攻击性，仅供安全研究与教学之用，读者将其信息做其他用途，由读者承担全部法律及连带责任，本站不承担任何法律及连带责任；如有问题可邮件联系(建议使用企业邮箱或有效邮箱,避免邮件被拦截，联系方式见首页)，望知悉。
- 左青龙
- 微信扫一扫
-
- 右白虎
- 微信扫一扫
-
评论