* Upload correct data array
* Require BufferArray Encryption for upload to server
The CipherArrayBuffer tiny type is only created by CryptoService
and required by all upload methods
* Add test for attachment upload encryption
* Skip FirefoxAccounts during Firefox CSV Import
Firefox exports 'chrome://FirefoxAccounts' if Firefox Accouts are used
in browser. It's quite hacky - password field in CSV is actually a JSON
encoded data, not a password.
Because it's not a useful record, it should be skipped during import.
* Fix indentation
* Move test Firefox test data to files, fix linter errors
* update package http-proxy-agent
* Update syntax appropriately
* Explicitly add utils package to fix broken tests
* Revert "Explicitly add utils package to fix broken tests"
This reverts commit 2cf03fdcbae89e55124c7e36201238520434f8cc.
* Import util in spec to make sure it gets bundled
* Revert "Import util in spec to make sure it gets bundled"
This reverts commit 79264cdab0ef37af855d64a6dc3ef574575309d2.
* Add alias to ensure util module resolves in tests
Co-authored-by: Thomas Rittson <trittson@bitwarden.com>
* Do not export trashed items
* Test Item exporting
Does not test organization export. Export's use of apiService is not
very testable. We will either need a testApiService or to refactor
apiService to make mocking easier.
* Linter fixes
* Use logService for console messages
* Implement a base ConsoleLog service
Use this class as a default for other services that would like to output
to console. This service is overriden in CLI and Desktop to use CLI's
consoleLogService and electronLogService, respectively.
* Use browser-process-hrtime for timing
* test LogService implementations
* Ignore default import of hrtime
* Clean up imports. Require ConsoleLog injection
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Change cipher type based on csv type header
* Test identity and credit card import
* Do not use node 'fs' module
Karma is being used for automated tests so node modules are not available
* WIP: mac and windows 1password importer split
Need to improve windows field identification to limit secret data
exposure and improve user experience
* Hide fields with likely secret values
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Fix import of 1password csv
* 1password is using '\' as a quote escape character.
* 1password's csv headers are sometimes capitalized. We want to identify
them case insensitively
* Change cipher type based on csv type header
* Translate 1password data to correct fields
* Test identity and credit card import
* linter fixes
* Do not use node 'fs' module
Karma is being used for automated tests so node modules are not available
Co-authored-by: Matt Gibson <mdgibson@Matts-MBP.lan>
* Fix import of expiration date from LastPass
Signed-off-by: Felipe Santos <felipecassiors@gmail.com>
* handle empty cc exp from lastpass, add test
* check for month/year null/whitespace
* check for empty expiration from lp import
Co-authored-by: Felipe Santos <felipecassiors@gmail.com>
* allow base importer to receive custom field type
* 1password importer uses hidden field type
for custom fields marked as 'concealed'
* 1password 1pif importer specs
* remove 'focus' from specs
* change field type logic into simple one liner
* Add sequentialize to prevent parralel loading of cipher keys
Massively improves start up performance of extensions
* Add tests for sequentialize
* Fix sequentialize as it was caching calls for all instances together
* Add sequentialize to the functions that have internal caches
* Adding sequentialize to getOrgKeys makes big performance difference
* Update cipher.service.ts
* Update collection.service.ts
* Update folder.service.ts
