Jump to content

Mitro

From Alfawiki
Adapted from the English Wikipedia article Mitro, available under CC BY-SA 4.0Updated 28 November 2025
Mitro
Company typePrivate
IndustryComputer security software
Founded2012
FounderVijay Pandurangan, Evan Jones, Adam Hilss
Defunct2015-10-06
FateService discontinued; team joined Twitter; source code released as free software
SuccessorPassopolis
Headquarters
United States
Key people
Vijay Pandurangan, Evan Jones, Adam Hilss
ProductsPassword manager software

Mitro served as a password manager tailored for both individuals and teams, enabling secure storage of login credentials and facilitating shared access.

The Mitro service was officially discontinued on October 6, 2015.

Its replacement, Passopolis, is a password management solution developed utilizing Mitro's original source code.

History

Established in 2012 by Vijay Pandurangan, Evan Jones, and Adam Hilss, Mitro received $1.2 million in seed investment from Google Ventures and Matrix Partners.

On July 31, 2014, the Mitro team joined Twitter and made the software's source code publicly available on GitHub under the GPL license as free software.

The timeline leading to shutdown was as follows:

  • July 11, 2015: Announcement of service discontinuation
  • July 18, 2015: Disabled creation of new accounts
  • August 4, 2015: Issued final shutdown notification
  • September 24, 2015: Transitioned to read-only mode
  • October 6, 2015: Service officially ended
  • October 31, 2015: Complete deletion of user data

The decision to cease operations stemmed from the significant expenses and operational challenges involved in maintaining the platform on a part-time basis without adequate resources. The team emphasized security and dependability by opting to terminate the service.

Previous users were encouraged to switch to Passopolis or alternative services such as 1Password, Dashlane, or LastPass.

Twitter formally ended Mitro’s service on October 5, 2015.

Security

Mitro utilized Google's Keyczar library on its servers along with Keyczar JS within browsers for encryption purposes. Its security architecture featured:

  • A master key employing 128-bit AES encryption derived through PBKDF2 (using SHA-1 with 50,000 iterations and a 16-byte salt)
  • RSA encryption with 2048-bit keys incorporating OAEP-SHA1 for distinct signing and encryption operations
  • AES encryption at 128-bit strength in CBC mode combined with PKCS5 padding
  • Integrity protection of encrypted data via HMAC-SHA1

See also

External links