* Make card number hidden
* Add support for password reprompt
* Rename PasswordPrompt to Reprompt
* Protect autofill
* Use Enums.CipherRepromptType
* Fix iOS not building
* Protect iOS autofill
* Update to match jslib
* Fix failing build
* Deleted appveyor.yml
* Remove Include of appveyor.yml from sln-file
* Deleted ci-build-apks.ps1 referenced by appveyor.yml
* Replaced build badge in README.md
* add support for disable send policy
* cleanup
* show/hide options support for send search results
* additional failsafes and copy function consolidation
* added missing disabled send icon to android renderer
* async fix and string updates
* Send feature for mobile
* added fallback for KdfIterations
* additional property exclusions for tests
* support encryptedFileData as byte array comparison in SendServiceTests
* formatting
* requested changes
* additional changes
* change position of send service registration to match declaration order
* Expand Hkdf crypto functions
* Add tests for hkdf crypto functions
Took the testing infrastructure from bitwarden/server
* Move Hkdf to cryptoFunctionService
* Port changes from bitwarden/jslib#192
* Port changes from bitwarden/jslib#205
* Make Send Expiration Optional implement changes from bitwarden/jslib#242
* Bug fixes found by testing
* Test helpers
* Test conversion between model types
* Test SendService
These are mostly happy-path tests to ensure a reasonably correct
implementation
* Add run tests step to GitHub Actions
* Test send decryption
* Test Request generation from Send
* Constructor dependencies on separate lines
* Remove unused testing infrastructure
* Rename to match class name
* Move fat arrows to previous lines
* Handle exceptions in App layer
* PR review cleanups
* Throw when attempting to save an unkown Send Type
I think it's best to only throw on unknown send types here.
I don't think we want to throw whenever we encounter one since that would
do bad things like lock up Sync if clients get out of date relative to
servers. Instead, keep the client from ruining saved data by complaining
last minute that it doesn't know what it's doing.
* [SupportedBrowsers] Small update
See PR for more info.
* Remove `org.ungoogled.chromium` from AutofillHelpers.CompatBrowsers too
Reason: deprecated.
* Remove `org.ungoogled.chromium` from autofillservice.xml too
Reason: deprecated.
* url -> URL
* Attempt URI healing with https prior to http
Browsers are moving away from displaying URI scheme in a way
accessibility can easily grab. This causes this URI healing to be relied
upon more frequently. It should attempt https prior to http due to
prevelence of https and security concerns with passwords over http.
* Just use https as the URI healing scheme
* Initial commit of personal ownership policy
* Updated logic for returning from allowing cipher creation from notification
* fixed small edge case when user in one org // adjusted error message to match all platforms
* Removed test code
