Java编码指南-编写安全可靠程序的75条建议-(英文版)

chapter 1　security　/　安全 11.　limit the lifetime of sensitive data 2限制敏感数据的生命周期 2.　do not store unencrypted sensitive information on the client side 5不要在客户端存储未经加密的敏感数据3.　provide sensitive mutable classes with unmodifiable wrappers 9为敏感可变类提供不可修改的包装器4.　ensure that security-sensitive methods are called with validated arguments 11确保安全敏感方法被调用时参数经过验证5.　prevent arbitrary file upload 13防止任意文件上传6.　properly encode or escape output 16正确地编码或转义输出7.　prevent code injection 20防止代码注入8.　prevent xpath injection 23防止xpath注入9.　prevent ldap injection 27防止ldap注入10.　do not use the clone() method to copy untrusted method parameters 31不要使用clone()方法来复制不可信的方法参数11.　do not use object.equals() to compare cryptographic keys 34不要使用object.equals()来比较密钥12.　do not use insecure or weak cryptographic algorithms 36不要使用不安全的弱加密算法13.　store passwords using a hash function 37使用散列函数存储密码14.　ensure that securerandom is properly seeded 42确保securerandom正确地选择随机数种子15.　do not rely on methods that can be overridden by untrusted code 44不要依赖可以被不可信代码覆写的方法16.　avoid granting excess privileges 50避免授予过多特权17.　minimize privileged code 54最小化特权代码18.　do not expose methods that use reduced-security checks to untrusted code 56不要将使用降低安全性检查的方法暴露给不可信代码19.　define custom security permissions for fine-grained security 64对细粒度的安全定义自定义安全权限20.　create a secure sandbox using a security manager 67使用安全管理器创建一个安全的沙盒21.　do not let untrusted code misuse privileges of callback methods 72不要让不可信代码误用回调方法的特权chapter 2 defensive programming　/　防御式编程 7922.　minimize the scope of variables 80最小化变量的作用域23.　minimize the scope of the @suppresswarnings annotation 82最小化@suppresswarnings注解的作用域24.　minimize the accessibility of classes and their members 84最小化类及其成员的可访问性25.　document thread-safety and use annotations where applicable 89文档化代码的线程安全性26.　always provide feedback about the resulting value of a method 96为方法的结果值提供反馈27.　identify files using multiple file attributes 99使用多个文件属性识别文件28.　do not attach significance to the ordinal associated with an enum 106不要赋予枚举常量的序号任何特殊意义29.　be aware of numeric promotion behavior 108注意数字提升行为30.　enable compile-time type checking of variable arity parameter types 112对可变参数的类型做编译时类型检查31.　do not apply public final to constants whose value might change in later releases 115不要把其值在以后版本里可能会发生变化的常量设置为public final32.　avoid cyclic dependencies between packages 118避免包之间的循环依赖33.　prefer user-defined exceptions over more general exception types 121使用用户自定义的异常而非宽泛的异常类型34.　try to gracefully recover from system errors 123尽量从系统错误中优雅恢复35.　carefully design interfaces before releasing them 125布接口前请谨慎设计36.　write garbage collection–friendly code 128编写对垃圾回收机制友好的代码chapter 3 reliability　/　可靠性 13137.　do not shadow or obscure identifiers in subscopes 132不要在子作用域里遮蔽或者掩盖标识符38.　do not declare more than one variable per declaration 134不要在一个声明里声明多个变量39.　use meaningful symbolic constantsto represent literal values in program logic 138在程序逻辑中用有意义的符号常量代表文字值40.　properly encode relationships in constant definitions 142在常量定义中恰当地表示相互之间的关系41.　return an empty array or collection instead of a null value for methods that return an array or collection 143对于返回数组或者集合的方法，用返回一个空数组或者集合来替代返回一个空值42.　use exceptions only for exceptional conditions 146只在异常的情况下使用异常43.　use a try-with-resources statement to safely handle closeable resources 148使用try-with-resources语句安全处理可关闭的资源44.　do not use assertions to verify the absence of runtime errors 151不要使用断言来验证不存在的运行时错误45.　use the same type for the second and third operands in conditional expressions 153在条件表达式中，第二和第三个操作数应使用相同类型46.　do not serialize direct handles to system resources 157不要序列化直接指向系统资源的句柄47.　prefer using iterators over enumerations 159更倾向于使用迭代器而不是枚举48.　do not use direct buffers for short-lived, infrequently used objects 162对于短生存周期、不常用的对象不要使用直接缓冲区49.　remove short-lived objects from long-lived containe