Fix misspell issues.
See, $ gometalinter --vendor --disable-all --enable=misspell ./... sqlite3.go:1379:45⚠️ "succesfully" is a misspelling of "successfully" (misspell) sqlite3.go:1390:30⚠️ "registerd" is a misspelling of "registered" (misspell) sqlite3_func_crypt.go:16:27⚠️ "ceasar" is a misspelling of "caesar" (misspell) sqlite3_func_crypt.go:43:59⚠️ "Ceasar" is a misspelling of "Caesar" (misspell) sqlite3_opt_userauth_test.go:450:27⚠️ "succesful" is a misspelling of "successful" (misspell) sqlite3_opt_userauth_test.go:456:27⚠️ "succesful" is a misspelling of "successful" (misspell)
This commit is contained in:
@@ -13,7 +13,7 @@ import (
|
||||
|
||||
// This file provides several different implementations for the
|
||||
// default embedded sqlite_crypt function.
|
||||
// This function is uses a ceasar-cypher by default
|
||||
// This function is uses a caesar-cypher by default
|
||||
// and is used within the UserAuthentication module to encode
|
||||
// the password.
|
||||
//
|
||||
@@ -40,7 +40,7 @@ import (
|
||||
// password X, sqlite_crypt(X,NULL) is run. A new random salt is selected
|
||||
// when the second argument is NULL.
|
||||
//
|
||||
// The built-in version of of sqlite_crypt() uses a simple Ceasar-cypher
|
||||
// The built-in version of of sqlite_crypt() uses a simple Caesar-cypher
|
||||
// which prevents passwords from being revealed by searching the raw database
|
||||
// for ASCII text, but is otherwise trivally broken. For better password
|
||||
// security, the database should be encrypted using the SQLite Encryption
|
||||
|
||||
Reference in New Issue
Block a user