在使用移动应用时我们经常会用到上下文菜单。什么是上下文菜单?举个例子,当我们使用微信时,如果要删除、置顶或标记一条信息时,我们会怎么做?是的,这时我们就需要用到上下文菜单了。上下文菜单是指应用提供的,用于处理与当前信息有关的操作选项。

这个用于与用户交互的界面被广泛地使用于大多数流行的移动应用中。但不同的操作系统上下文菜单的使用方式是不一样的。一般情况下,这个主题是不会拿来讨论的,因为每个系统有自己的用户群,不需要讨论跟自己系统无关的用户体验。但跨平台的用户体验主要发生在为开发者提供跨平台的应用框架中,微软的Xamarin框架正是这样的体系。

PassXYZ是基于Xamarin的,所以PassXYZ的用户通常会在主流的系统中使用PassXYZ。虽然Xamarin尽量把在不同平台上的用户体验做得一致,但出于性能的考虑,最终实现都是使用各个系统本身的功能来完成的。这样,某些细节在不同平台间就会有少许差异。上下文菜单就是其中对PassXYZ影响最大的一项,所以在这里单独提出来说明一下。

PassXYZ的主要用户界面有两个:第一个用户界面是**目录(Group)条目(Entry)组成的列表页;第二个用户界面是条目(Entry)**详细信息的显示页。

目录(Group)和条目(Entry)的列表页

Fingerprint

在上面这个图中,从左到右依次显示的是同一个数据库在iOS,Android和Windows 10中打开的状态。在最左边的图中,我们可以看到,用户在iOS系统中可以通过向左滑动来显示一个条目的上下文菜单。通过上下文菜单,可以对该条目进行删除、编辑和拷贝的操作。同样的,在Android系统中,用户可以通过常按一个条目来显示上下文菜单。虽然上下文菜单的内容与其他系统是一样的,但它是显示在屏幕顶部的,如中图所示。再看最右侧的UWP应用,在Windows 10的UWP (Universal Windows Platform) 应用中,我们可以点击鼠标右键来显示上下文菜单。这一行为与普通Windows应用是一致的。

在PassXYZ中,目录条目的列表页通常支持对一个条目的拷贝删除编辑的操作。这些操作可以通过上下文菜单来执行。

条目(Entry)详细信息页

下面,我们再来看看条目详细信息页中的上下文菜单。

Fingerprint

条目详细信息页中,每一行显示的是该条目中的一个域。每一行,都有相应的上下文菜单。上下文菜单的内容是与这一行的类型相对应的。比如,上图中显示的是一个密码域所对应的上下文菜单,在阅览状态下密码域是被隐藏的,我们可以通过上下文菜单把密码拷贝到剪切版,也可以选择显示密码的内容。在不同平台中打开上下文菜单的方式是与上述**目录(Group)条目(Entry)**的列表页中一样的。

通过以上的简短说明,相信您已经掌握了如何在不同平台中使用PassXYZ的上下文菜单了。


PassXYZ是一款可以运行在安卓和苹果手机以及Windows10上的KeePass兼容应用。PassXYZ最大的特点是通过提供大量的个人信息记录模板来分享和传递良好的使用习惯。PassXYZ个人信息管理软件和PassXYZ公众号的目标是通过两者的结合来推动和提高公众的个人信息管理水平。

您可以通过苹果应用商店微软应用商店Google Play华为应用商店搜索关键字PassXYZ来下载该应用。如果您想获得更多模板或对个人信息安全及管理有兴趣,可以搜索关键字PassXYZ关注公众号。您也可以通过微信号passxyz_kpclib来添加此公众号。PassXYZ公众号专注于个人信息安全及管理的相关知识。

Context Action is a term used by the UI designers frequently when they work on a user interface design. As the users of mobile applications, we also use Context Action quite often. So, what is the Context Action? For an example, when we use WhatsApp, what do we do if we want to delete or mark a message? Yes, we actually use the Context Action for that item. Context Action refers to the actions that a user can take on a particular item which the user is working on.

Context Action is used in almost all the mobile platforms. However, the behaviors of the Context Action on different operating systems look quite different. Usually, this won�t be an issue. Thus, there are not many articles discussing on this topic. Each platform has their own group of users and the users do not care about cross-platform user experiences. Cross-platform user experiences are usually discussed in the framework to support cross-platform development. Xamarin from Microsoft is the cross-platform framework used by PassXYZ. Therefore, PassXYZ users may feel confused about different Context Action behaviors on different platforms. This is the reason why we compare the behaviors of the Context Action on different platforms in this article.

Even though Xamarin tried to bring consistent user experiences on all platforms, the low level implementations use the native components from the platform itself due to the performance concern.

PassXYZ has two main user interfaces:
1. A page including a list of groups and entries, let�s call it List Page.
2. A page showing the details of an entry, let�s call it Detail Page.

List Page

Fingerprint

From the above diagram, we can see the status of the same database on different operation systems, from the left to the right, namely, iOS, Android and Windows 10. On the left-hand side, it is the screenshot for iOS. The users can take actions on the current item by sliding it to the left. When the Context Action menu is shown, you will see three actions Copy, Edit and Delete. In the middle of the diagram, it is the Android system. The users can get the Context Action menu by long pressing the current item. The Context Action menu on Android is shown on the top of the screen. On the right-hand side of the diagram, it is the Universal Windows Platform (UWP) application of Windows 10. The UWP application inherited the same behavior from normal Windows applications. The users can access the Context Action menu using right mouse click.

Detail Page

Let�s have a look at the Detail Page in PassXYZ.

Fingerprint

In the Detail Page, it shows the content of an entry. There are multiple fields in an entry and they may have a different Context Action menu based on the type of the field. For an example, the password is usually hidden in the Detail Page. To show the content of the password, the users need to select the Show action from the Context Action menu. This is unique as to the password field. The way to access the Context Action menu in Detail Page is the same as the above-mentioned in the List Page.

After reading this brief explanation on the Context Action behaviors on different platforms, hopefully, PassXYZ users can now get used to it on different platforms.

How to report issues?

If you find any issues for PassXYZ or PassXYZ Cloud, you can report issues in the following ways:

  1. Submit an issue report at PassXYZ GitHub
  2. Send an email to support email at passxyz@foxmail.com
  3. Send a message to PassXYZ WeChat public account (passxyz_kpclib)
  4. If you have any comments on a particular topic, you can also add comments to the articles in either WeChat or GitHub

Test PassXYZ Beta version

PassXYZ or PassXYZ Cloud beta versions can installed from the below links.

iOS

  1. PassXYZ Cloud
  2. PassXYZ

Android

  1. PassXYZ Cloud
  2. PassXYZ

FAQ:

  1. How to install PassXYZ?
  2. How to use PassXYZ?

Fingerprint

Many people are using biometrics authentication method in our daily life, since they are convenient and easy to use. Slowly, you may have a perception that fingerprint or face recognition may replace your passwords one day. But you may be wondering, why this hasn�t happen yet? Every time, you reboot your mobile phone, the system will ask you for password to unlock your phone first, and then, you can use your fingerprint. If you want to turn on fingerprint or face recognition on your phone, you have to setup a PIN for the screen lock fist. Why the systems want to tie biometrics authentication together with passwords? The reason is biometrics authentication cannot replace passwords. Let�s have a look at the characteristics of biometrics authentication first.

Unique and immutable

Biometrics is unique and immutable information of ourselves, thus, they cannot be faked. As they cannot be faked or changed, we will be stuck in a dilemma if they are stolen by someone. From this point of view, biometrics is not safer than password. Biometrics and password have their own advantages and disadvantages, and cannot be replaced by each other.

Reliability

There are many factors that can affect the result of biometrics authentication. For example, humidity can affect the accuracy of fingerprint detection. I often heard the complaints from my friends that they always have problems to use fingerprint in autumn or winter. That is because the humidity in autumn and winter is low, so their fingers are too dry for the fingerprint sensors. Face recognition and iris recognition are also facing the similar issues, i.e., they can only be done with enough light. Therefore, biometrics authentication cannot be used alone as the reliability can be affected by many factors.

Comparison method

We can easily understand that biometrics authentication and password based authentication use different comparison methods. The comparison of password is very simple and accurate. The result can be either success or failure. The techniques used by biometrics are similar to image recognition. There is not a straightforward result of success or failure. Image recognition can only judge whether the level of similarity is within certain range or not. According to the degree of similarity, it tells you roughly on success or failure. This is another reason why biometrics authentication is not reliable enough.

Device dependency and complex data structure

Biometrics uses a much more complex data structure comparing to password. The data generated by the fingerprint sensor is defined by the vendor which cannot be used on other devices unless they are from the same vendor. This makes the fingerprint data device-dependent. Actually, other biometrics, such as iris recognition, also has the same problem. Therefore, the biometrics data cannot be used for authentication directly due to the compatibility issue. For example, the same fingerprint may generate different data on Android and iOS systems.

Well, how can we resolve the compatibility issue? Let�s say a banking application, if you want to turn on fingerprint, you have to login to the app using username and password first. When you turn on fingerprint from the setting of the app, the app will store authentication information in the secure storage of the device. This authentication information could be your username and password or something that the app can use to communicate with the application backend. The secure storage is device-unique which could be Keychain on iPhone or Keystore on Android. The data in the secure storage are isolated at the application level. One application cannot access the data stored by another application. The next time when you login to the banking app using the fingerprint, the system will unlock the secure data and the app will use the stored information to communicate to the application backend. That is, you actually provide your authentication information through fingerprint, but you are not using the fingerprint data to authenticate with the app directly.

Authentication information can be anything about you

Authentication information can actually be anything about you besides passwords or biometrics data. For example, you may need to provide your name, card number and date of birth so as to report the loss of your credit card. You may need to provide your username, ID card number and the remaining balance in your account in order to restore a locked PayPal account.

Bank counters

Right now, many banks have replaced the traditional counters with intelligent counters. When we use these intelligent counts, do we have all the data needed to perform the transaction? Facing the future, we have to organize our personal information nicely in order to deal with the challenges in our digital life.


If you are interested in the personal information management, please add PassXYZ Wechat public account by searching the keyword PassXYZ or link it using Wechat name passxyz_kpclib. You can also find more information about PassXYZ on its website and install it from Google Play, Apple Store or Microsoft Store.

For Windows 10 users, you can now get a free version of PassXYZ following the steps below:
1. Added PassXYZ Wechat public account
2. Send key word UWP to get a registration code
3. Install PassXYZ from Microsoft store using the registration code (200 users can use this code)

I had been in trouble of managing a large number of accounts since I joined the IT industry more than ten years ago. At that time, I had dozens of company and personal accounts to remember. At the beginning, I tried to use the same username and password to manage all of them so that I could deal with a large number of accounts without too many problems. However, the company accounts had to be changed every quarter. For setting the password, it had to be a combination of at least eight letters in upper or lower cases with special characters and numbers. As it is difficult to remember such kind of password, I spent some time to figure out a few passwords which can meet the said criteria. I planned to use them repeatedly. Unfortunately, I found that the system could remember more than ten previous passwords that I used, and, I could not re-use them. I ran out of the prepared passwords very quickly. From then on, I had to create sophisticated passwords for the different accounts from time to time. The more complicated the passwords are, the more difficulties you will get to remember them. In order to find an easy way for me to use the passwords, I started to record them using a document. Initially, I recorded the information in an Excel file in the company laptop which was the most frequently used device. Although it was easy for me to check the passwords, the problem was that I had to send the laptop to the IT department frequently for resolving both hardware and software issues. The IT department usually had the highest system privilege, so it was not safe to store the secure information in an Excel file.

How to choose a password management application

To deal with this issue, I started to search whether there were applications for the password management. At that time, the IT industry was still young. There was not too much software available on the market. There were no software stores like Google Play or Apple Store. Later on, I found a software called CodeWallet. If you search it today, there will not be too much information about CodeWallet. I did try to use a few password management applications until I found KeePass. Thereafter, I stuck with using KeePass for about ten years till today. You may be wondering why I stayed with KeePass or KeePass family software for so long. Well, you will get the answer after you read my following several criteria of choosing password management software.

Safety

After using some password management software, one question always in my mind is that why I can trust them? Do they have any back doors? I believe that the safety is at the top of the list when most of people start to look for password management software. Of course, the developers of the software must be trustable. How can we qualify them? Can the software from a large company be trusted? Since I have worked in multi-national companies for many years, I knew that each department in a big company is just likes a small company. Unless it is a flagship product, otherwise, the product from a big company will have not many differences comparing to that from a start-up company.
Is there a way to overcome this doubt? The answer is yes. We do not have to focus on the qualification of developers only. If the software was open source, we could start from the source code directly. We can qualify the source code instead of the developer in this way. This was the initial motivation that I chose KeePass. The quality of open source software is closely related to the popularity of itself. There are a large number of developers involved in popular open source software, so the quality of source code can be improved from time to time. This is exactly the case for KeePass.

The popularity and quality can, in turn, help to increase the life time of the software itself. The commercial software that I used has been discontinued whilst KeePass is still alive.

File format

With the increase of KeePass popularity, the KeePass data format becomes the de facto standard data format for open source password management software. This is another reason that I stay with KeePass for so long.

There are a large number of derived KeePass applications available on almost every platform that I used. Just like the file format in the office software, even though there are many word processing applications in the market, Microsoft Office still can dominate the market largely due to its file format which is the de facto standard in this market.

In order to help the developers to reuse KeePass to build derived application easily, the author of KeePass separated the major functionalities of KeePass into a library called KeePassLib. This is one of the key reasons why KeePass data format is used widely.

The first KeePass derived application used KeePassLib is KeePassPPC which is a porting of KeePass on Windows CE platform. When Android and iOS become the two major operating systems for mobile devices, the developers ported KeePassLib to both Android and iOS platforms. However, Android uses Java as the development language while iOS uses Objective C. It is time consuming to translate KeePassLib from the original C# language to either Java or Objective C. That is the reason why the development of KeePass derived applications on these two platforms is far behind the official KeePass development on Windows by the original author Dominik Reichl. Till today, the KeePass author Dominik Reichl is still actively working on the KeePass development on Windows and releases new KeePass version frequently. It is a big challenge for the developers on both Android and iOS to keep up with the official releases.

This situation was getting better when Microsoft released Xamarin as a cross platform development environment for Android, iOS, Mac OS X and Windows. The first KeePass application on Android using Xamarin is KeePass2Android. It kept almost the entire KeePassLib in C# and developed KeePass2Android on top of it. That was the reason why I used Keepass2Android for a few years till my own application PassXYZ published on all major platforms (Android, iOS and Windows 10) recently.

Keepass2Android is an Android application rewritten using C# with the help of Xamarin. As it was not written in a cross platform way, the author did not release it on other platforms, such as iOS and Windows. I have iOS devices as well as Android and Windows devices. After waiting for many years, I decided to develop a cross platform KeePass application which can be run on all major platforms using Xamarin. Then, I started to port KeePassLib to Xamarin as a Portable Class Library. This project can be found on the open source repository GitHub under the name KPCLib (KeePass Portable Class Library). On top of KPCLib, I developed the KeePass derived application - PassXYZ. PassXYZ has been released at Google Play, Apple Store and Microsoft Store.

Storage

After discussions on Safety and Data format, let’s talk about another factor that we need to look at when we try to find a suitable password management application. Where do we want to store our secure data? The choices are local data or cloud. How can we decide? There is not a straightforward answer to this question, as it is correlative with three factors which are safety, ease of use and reliability.

But, why the choice of storage location is contradictory to safety, ease of use and reliability?

For the safety of secure data file, we all know that the less people have the access, the more safety the data file has.

For example, why the banks still allow their customers to use 6 digits number as the PIN for ATM? And, why all companies require a sophisticated combination of upper/lower cases with numbers and special characters as the password for their accounts? Does it mean that the company accounts have higher security requirements than that of the bank�s? Obviously not. The complication of the password should depend on the numbers of people who can access the secure data file. There are very limited numbers of persons who can access the secure data file in banks. However, in a company, much more people can access the secure data file. So, it is more risky that the secure data file in a company may be copied by the attackers.

The attackers aiming to a bank account have very limited time and space to attack the target while the attackers to a company�s may have almost un-limited time and space to do so. When the attackers attack the ATM or bank accounts from internet, they may not have chances to run through all the possibilities of 6 digits numbers. On the other hand, the attackers of company accounts may be able to run brute force software anywhere to try out all the possibilities of the password. As such, company accounts obviously require a much more complicated password so as to prevent it from being decrypted by the brute force software.

We learnt from the above that the location you store your secure data file determines how complicated your password should be. If you store your data file locally at home, it may be safe as the bank. But, if you store your date file on the cloud, the situation will be similar to the company.

Definitely, it is easier to use if you store your data on the cloud, but at the same time, you have to be aware of the safety issue. You need a strong master password to protect yourself. If you store your data file locally, you will have less concerns on the master password.

Then, how about the reliability of both local and cloud? The simple answer is that both are not reliable enough. The reliability of your data file, to a great extent, depends on your practices of managing your data file. No matter where you store your data file, you need to backup them frequently. The best practices in data file management will increase the difficulty of usage a little, but you will be in a better position in term of the chance of losing your data.

It is not difficult to use password management software, but it takes time to form a good habit following the best practices. When you are aware that you need password management software to help you, you also need to understand that the knowledge about how to manage your information better are equally important.

I created a PassXYZ Wechat public account when my PassXYZ software was released. This is because I believe all the users of password management software need both software and the best practice of personal information management. PassXYZ Wechat public account is a place that can be used to share the best practices among users.

If you are interested in the personal information management, please add PassXYZ Wechat public account by searching keyword PassXYZ or link it using Wechat name passxyz_kpclib. You can also find more information about PassXYZ on its website and install it from the following links

Apple Store

Microsoft Store

Google Play

PassXYZ是一款跨平台的KeePass兼容个人信息管理软件,可以在Android,苹果和Windows10上使用。

iOS

苹果手机用户可以在苹果商店里下载PassXYZ。用户可以搜索关键字PassXYZ或者点击下面链接在苹果商店里找到PassXYZ。

Apple Store

Windows 10

在Windows 10上,PassXYZ是一款UWP应用。UWP是Universal Windows Platform的缩写。UWP是在微软商店里发行的应用。通过微软的审核并使用微软商店的签名,相较传统的Windows应用,UWP应用更安全,很适合密码管理类应用的发行。Windows 10的用户可以搜索关键字PassXYZ或点击下面链接在微软商店里找到PassXYZ。

Microsoft Store

Android

Android的情况比较复杂。Android商店基本上分为国内和国外两种情况。

国外Android商店比较统一,基本都用Google Play。Google Play由Google提供,功能非常强大,而且安全性在所有Android商店里是最高的。如果您是Google Play的用户,可以直接搜索关键字PassXYZ或点击下面链接在Google Play里找到PassXYZ。

Google Play

国内因为无法使用Google Play,Android用户基本使用的都是国内各个Android手机的应用商店。国内的应用商店比较分散而且安全性和质量参差不齐,如果使用华为手机建议用户通过华为应用商店下载PassXYZ。可以直接搜索关键字PassXYZ或扫描下面的二维码在华为应用商店里找到PassXYZ。非华为手机用户,仍然可以使用下面的链接,但只能在电脑上下载后,通过电脑安装到手机。

华为应用商店

PassXYZ is a KeePass compatible cross-platform application which can run on Android, iOS and Windows 10. It is available in the above App stores.

iOS

You can download PassXYZ at Apple Store using the following methods:

  1. Search keyword “PassXYZ” at Apple Store, or
  2. Click the below link

Apple Store

Windows 10

On Windows 10, PassXYZ is an UWP application. UWP means Universal Windows Platform which is the format of Windows store application. All UWP applications are reviewed by Microsoft before they are available for the public. This also means UWP applications are safer than the traditional Windows applications.

You can download PassXYZ at Microsoft Store using the following methods:

  1. Search keyword “PassXYZ” at Microsoft Store, or
  2. Click the below link

Microsoft Store

Android

You can download PassXYZ at Google Play using the following methods:

  1. Search keyword “PassXYZ” at Google Play, or
  2. Click the below link

Google Play

Privacy Notice

Effective Date: July 8, 2018

This privacy notice discloses the privacy practices for PassXYZ application and our websites:

Information Collection, Use, and Sharing

This website is built using the services provided by GitHub. It is a static website and does not collect any information. Please refer to the GitHub Privacy Statement about the agreement before you use GitHub services.

PassXYZ application is an application to store your personal information on your own devices and encrypted in the KeePass database format. PassXYZ application may access network to retrieve resources such as font or icon etc.

Notification of Changes

You can always go to PassXYZ website to find the latest Privacy Notice.

這篇文章是寫給PassXYZ初始用戶的簡短使用說明。如果您是KeePass的資深用戶,可以跳過這篇文章去PassXYZ網站閱讀另外一篇叫深入理解PassXYZ的文章(PassXYZ的網站鏈接請點擊幫助頁面的了解更多)。

PassXYZ與其他密碼管理軟件一樣,使用其實相當簡單,沒有太多復雜的使用操作。當安裝好PassXYZ後,打開的第一個頁面是建立一個用戶名和設置一個主密碼。這裏需要提醒一下的是,這個主密碼非常重要,一旦忘記,就沒有人能打開這個數據庫了。

設置好用戶名和主密碼後,進入的將是一個可以記錄您所有個人信息的管理系統。那麽如何開始使用呢?屏幕右上角有三個圖標,根據圖標標識,您一定能認出來它們是搜索添加退出吧?

現在,您就可以開始添加您想讓PassXYZ幫您記住的任何個人信息了,比如說銀行卡、身份證、護照、社保卡、各類證書、常用網站賬號等等。以身份證為例吧:點擊加號圖標+,您可以看到屏幕會顯示目錄條目便簽從模板中選擇共四個選項。沒發現身份證選項啊?沒關系,您可以先去從模板中選擇裏找找。很多常用的添加項目PassXYZ都有特制的固定模板,即便模板裏沒有您需要的添加項目,您也有三個輸入辦法:第一,懶人的辦法,所有找不到的添加項目都可以使用通用選項條目,然後自行逐項輸入您所需要記錄的信息,最後保存即可。這個是原來KeePass自帶的。第二,到PassXYZ網站上找找,那兒有更多模板。第三,如果都不滿意,您還可以自己在模板中創建一個新的。當您開始創建模板時,您已經是PassXYZ達人了!

上面介紹了條目從模板中選擇。您這會兒可能會問,那目錄便簽又是什麽?目錄其實就是文件夾,例如您可以首先建立一個叫銀行的目錄,然後進入此目錄,再選用條目形式分別輸入您各個銀行賬戶的信息,這樣,您所有的銀行信息都可以整齊地存放在銀行目錄下,方便您日後翻閱查找。再說便簽吧,它就是一個您可以用來記錄任何東西的地方,比如說這篇文章,也就是一個便簽PassXYZ中的便簽是支持Markdown格式的,所以您可以用Markdown語法來美化便簽

話說回來,身份證這項,在PassXYZ自帶模板裏是可以找到的。在模板裏選擇身份證,然後填上相關信息並保存就好了。除了證件上的信息,您還可以把證件的照片或掃描件作為附件加上。這樣,當您下次在外辦事遇到緊急情況需要證件復印件時,直接打開PassXYZ用微信分享一下就可以了。
PassXYZ的基本使用其實就是這麽簡單,想了解更多,歡迎您關註PassXYZ網站。

可能碰到的問題:

支持指紋登錄嗎?
支持,去設置中打開就可以了。

可以導出數據嗎?
可以,去設置中導出。

可以同步嗎?
沒問題,上一步導出後,在其他設備上導入,然後在設置中同步即可。

PassXYZ自帶的模板可以在這裏下載:

  1. 英文模板
  2. 中文簡體模板
  3. 中文繁體模板

这篇文章是写给PassXYZ初始用户的简短使用说明。如果您是KeePass的资深用户,可以跳过这篇文章去PassXYZ网站阅读另外一篇叫深入理解PassXYZ的文章(PassXYZ的网站链接请点击帮助页面的了解更多)。

PassXYZ与其他密码管理软件一样,使用其实相当简单,没有太多复杂的使用操作。当安装好PassXYZ后,打开的第一个页面是建立一个用户名和设置一个主密码。这里需要提醒一下的是,这个主密码非常重要,一旦忘记,就没有人能打开这个数据库了。

设置好用户名和主密码后,进入的将是一个可以记录您所有个人信息的管理系统。那么如何开始使用呢?屏幕右上角有三个图标,根据图标标识,您一定能认出来它们是搜索添加退出吧?

现在,您就可以开始添加您想让PassXYZ帮您记住的任何个人信息了,比如说银行卡、身份证、护照、社保卡、各类证书、常用网站账号等等。以身份证为例吧:点击加号图标+,您可以看到屏幕会显示目录条目便签从模板中选择共四个选项。没发现身份证选项啊?没关系,您可以先去从模板中选择里找找。很多常用的添加项目PassXYZ都有特制的固定模板,即便模板里没有您需要的添加项目,您也有三个输入办法:第一,懒人的办法,所有找不到的添加项目都可以使用通用选项条目,然后自行逐项输入您所需要记录的信息,最后保存即可。这个是原来KeePass自带的。第二,到PassXYZ网站上找找,那儿有更多模板。第三,如果都不满意,您还可以自己在模板中创建一个新的。当您开始创建模板时,您已经是PassXYZ达人了!

上面介绍了条目从模板中选择。您这会儿可能会问,那目录便签又是什么?目录其实就是文件夹,例如您可以首先建立一个叫银行的目录,然后进入此目录,再选用条目形式分别输入您各个银行账户的信息,这样,您所有的银行信息都可以整齐地存放在银行目录下,方便您日后翻阅查找。再说便签吧,它就是一个您可以用来记录任何东西的地方,比如说这篇文章,也就是一个便签PassXYZ中的便签是支持Markdown格式的,所以您可以用Markdown语法来美化便签

话说回来,身份证这项,在PassXYZ自带模板里是可以找到的。在模板里选择身份证,然后填上相关信息并保存就好了。除了证件上的信息,您还可以把证件的照片或扫描件作为附件加上。这样,当您下次在外办事遇到紧急情况需要证件复印件时,直接打开PassXYZ用微信分享一下就可以了。
PassXYZ的基本使用其实就是这么简单,想了解更多,欢迎您关注PassXYZ网站。

可能碰到的问题:

支持指纹登录吗?
支持,去设置中打开就可以了。

可以导出数据吗?
可以,去设置中导出。

可以同步吗?
没问题,上一步导出后,在其他设备上导入,然后在设置中同步即可。

PassXYZ自带的模板可以在这里下载:

  1. 英文模板
  2. 中文简体模板
  3. 中文繁体模板
0%