<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/passwordsafe/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 12 Nov 2026 18:27:22 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/passwordsafe/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>#357 Symbian OS port</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/357/?limit=25#5815</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; Next_Release_(example)&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rony Shapiro</dc:creator><pubDate>Thu, 12 Nov 2026 18:27:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netbab331274b28a11f897f86d9d72f56145cc14fec</guid></item><item><title>#375 Security Questions and Answers</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/375/?limit=25#bd40</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Unfortunately in 2026 security questions are still a thing, mandatory for some financial websites and utilities and used as a 2nd factor during the normal login flow&lt;span&gt;[1]&lt;/span&gt;.  Following best practices, I treat them as passwords and store them as sensitive custom fields, so they can be copied using the right-click menu. The main inconvenience is in generating them. Let's say I'm setting up a new account that requires me to choose secret questions as part of the sign-up flow:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;After creating a new entry with a password I save and close the entry.&lt;/li&gt;
&lt;li&gt;Then press Ctrl-A to open a new entry dialog and generate a password (the random secret answer), copy it, and close the dialog without saving.&lt;/li&gt;
&lt;li&gt;Go back to the main entry, create a new custom field and paste the generated value, save and close.&lt;/li&gt;
&lt;li&gt;Repeat this 2 more times (or however many the website requires).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;One enhancement that comes to mind is having a "generate random value" button in the edit custom field dialog. For simplicity it could use the same policy as the main entry.&lt;br/&gt;
A step that's a bit more controversial is to have up to 3 "secret question" fields per entry that are treated as 1st class citizens - e.g. added to the dragbar and located at the 1st level of the right-click menu. Additional questions could be added as custom fields.&lt;/p&gt;
&lt;p&gt;Not sure how many people share the same misfortune of having to deal with secret questions.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[1]&lt;/span&gt; (sigh) I wish those providers would just follow the &lt;a href="https://pages.nist.gov/800-63-4/sp800-63b.html" rel="nofollow"&gt;NIST 800-63&lt;/a&gt; guidelines, namely &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Verifiers and CSPs SHALL NOT prompt subscribers to use knowledge-based authentication (KBA) (e.g., “What was the name of your first pet?”) or security questions when choosing passwords.&lt;/p&gt;
&lt;/blockquote&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dmitry Erastov</dc:creator><pubDate>Thu, 12 Nov 2026 02:39:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete84cde7ec99fa6bd6d31a479307f2ecf51c884f2</guid></item><item><title>#357 Symbian OS port</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/357/?limit=25#4e59</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This can probably be closed now since Symbian is long dead.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dmitry Erastov</dc:creator><pubDate>Thu, 12 Nov 2026 00:39:06 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1dbb57be161146613e6679768e26e2cb021f1c86</guid></item><item><title>right-click on entry in Treeview feature to be able to display a custom value</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/942/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently displaying a custom value that is hidden requires editing the entry, selecting the Custom Fields tab and then right clicking on the custom value to select Show Value. Furthermore, extra steps are sometimes necessary to resize the Value column to see all the characters in the value field whether the value is hidden or not.&lt;/p&gt;
&lt;p&gt;It would be very convenient if the user could simply right-click on the entry in the Treeview and select a 'Display Custom Field Value' option (similar to the current 'Copy Custom Field Value') which would display the custom field value the user selects in popup window that the user would be responsible to close.  An example use case for this is viewing a credit card # to give to someone over the phone.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MrMe</dc:creator><pubDate>Fri, 14 Aug 2026 21:00:38 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1a8ae389dc363b6c4fbce3c1fdb5b9cec9f046bb</guid></item><item><title>#941 Add a group property to exclude entries from search results</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/941/?limit=25#c1e0/0327</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Rony,&lt;/p&gt;
&lt;p&gt;The database filter approach was just an idea. I support whatever solution is best.&lt;/p&gt;
&lt;p&gt;I agree that archiving entries to a separate 'archive' database is a simple solution. If the database gets too large, I think that a user would likely want to archive entries to a separate database, especially if using a slow computer. However, before deciding to archive entries to a separate database, I know I have entries (all under a single top-level group) that I don't need to be found in Search and that I'm not ready to remove from my main database, which is why I support this feature. &lt;/p&gt;
&lt;p&gt;Not sure if your "archive" flag approach also means that Find would not surface those items? If so, then the archive flag would be fine with me.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MrMe</dc:creator><pubDate>Tue, 04 Aug 2026 15:22:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb7133933b786cc0f87163e4e3418e77ba2839d9e</guid></item><item><title>#941 Add a group property to exclude entries from search results</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/941/?limit=25#c1e0</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm not sure about this. My main concern is that people will set this and forget it, or set this incorrectly and as a result miss entries that they'd otherwise see.&lt;/p&gt;
&lt;p&gt;A simpler solution (what I do) is keep a separate "archive" database, and move entries to this (via drag &amp;amp; drop) as needed. This also provides the advantage of keeping the main database trimmed down.&lt;/p&gt;
&lt;p&gt;If we decide to implement this, I'd define this as an "archive" flag, and visually indicate it by, say, graying out the group's icon and text, and applying it recursively to all subgroups.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rony Shapiro</dc:creator><pubDate>Mon, 03 Aug 2026 06:01:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net75fb3f89b8a899c499fdc4fc5bc35f55d9d2d1c4</guid></item><item><title>#941 Add a group property to exclude entries from search results</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/941/?limit=25#1979</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I too would love to have this feature.&lt;/p&gt;
&lt;p&gt;I was thinking of the another way this feature could be implemented.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="mf"&gt;1.&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Currently&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;you&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;can&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;have&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;filters&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;that&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;are&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stored&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kd"&gt;data&lt;/span&gt;&lt;span class="n"&gt;base&lt;/span&gt;&lt;span class="mf"&gt;.&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Filters&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stored&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kd"&gt;data&lt;/span&gt;&lt;span class="n"&gt;base&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;could&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;be&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kd"&gt;def&lt;/span&gt;&lt;span class="n"&gt;ined&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;for&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;groups&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;entries&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;that&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;you&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;don&lt;/span&gt;&lt;span class="err"&gt;'&lt;/span&gt;&lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;want&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;appear&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Find&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;search&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="mf"&gt;.&lt;/span&gt;
&lt;span class="mf"&gt;2.&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;An&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;enhancement&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Find&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;would&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;be&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;ability&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;configure&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;it&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;with&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;filters&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stored&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kd"&gt;data&lt;/span&gt;&lt;span class="n"&gt;base&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;that&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Find&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;would&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;use&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;determine&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;entries&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;exclude&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;during&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;searching&lt;/span&gt;&lt;span class="mf"&gt;.&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;The&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;new&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;configuration&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Find&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;would&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;need&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;be&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;setting&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;that&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;is&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stored&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;in&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kd"&gt;data&lt;/span&gt;&lt;span class="n"&gt;base&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;so&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;the&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;on&lt;/span&gt;&lt;span class="n"&gt;ly&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;needs&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;to&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;do&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;it&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kr"&gt;on&lt;/span&gt;&lt;span class="n"&gt;ce&lt;/span&gt;&lt;span class="mf"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MrMe</dc:creator><pubDate>Fri, 31 Jul 2026 14:52:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net649e543de838a8b2cfa9a466efe1a43c089b1866</guid></item><item><title>Add a group property to exclude entries from search results</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/941/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello, &lt;/p&gt;
&lt;p&gt;Password Safe currently allows users to restrict searches using Advanced Find criteria. However, these criteria are session-specific and must be configured again after restarting the application.&lt;/p&gt;
&lt;p&gt;This is inconvenient for groups containing entries that should remain in the database but should not normally appear in search results, such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;archived accounts;&lt;/li&gt;
&lt;li&gt;obsolete or disabled credentials;&lt;/li&gt;
&lt;li&gt;decommissioned systems;&lt;/li&gt;
&lt;li&gt;historical entries;&lt;/li&gt;
&lt;li&gt;test accounts.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For example, I maintain an Archive group. Its entries must remain accessible, but they create unnecessary noise in routine searches&lt;/p&gt;
&lt;p&gt;Here is my request : Is it possible to  add a persistent search behavior property to groups, similar to the functionality available in KeePass.&lt;/p&gt;
&lt;p&gt;A possible setting in the group properties dialog could be:&lt;/p&gt;
&lt;p&gt;Searching entries in this group:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Inherit from parent&lt;/li&gt;
&lt;li&gt;Disabled&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When set to &lt;em&gt;Disabled&lt;/em&gt;, entries belonging to the group should be excluded from normal search results.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Noshell</dc:creator><pubDate>Wed, 29 Jul 2026 12:47:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfda5d5f248a7aacb618627a3848459d5870ebf8c</guid></item><item><title>#940 Restore ability to copy Notes on Add/Edit entry screen</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/940/?limit=25#f1e8</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Probably should have titled this 'Restore ability to copy Notes on Add/Edit entry screen &lt;em&gt;using a single button click&lt;/em&gt;' since it also possible to right click on the Notes area twice, once to select all text and a second time to copy all to the clipboard. However, this is not as convenient as the single click copy feature that the tabbed interface between Notes and Custom Fields eliminated.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MrMe</dc:creator><pubDate>Fri, 19 Jun 2026 13:40:54 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net523a338e0692531b839b66c97121e41174ab7a72</guid></item><item><title>Restore ability to copy Notes on Add/Edit entry screen</title><link>https://sourceforge.net/p/passwordsafe/feature-requests/940/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;V3.72pre introduced a tab interface on the Add/Edit entry screen to switch between Notes and Custom Fields tabs, as a result the ability in versions prior to v3.72pre to copy the entire Notes field to the clipboard  by simply clicking on the 'Notes'  heading is no longer possible.  This is a general feature for all fields on the Add/Edit entry screen where any of the headings (e.g. Password, URL, Email, etc.) can be clicked on to copy the corresponding field to the clipboard.&lt;/p&gt;
&lt;p&gt;This FR recommends adding a Copy Notes text on the Notes tab to restore the ability to copy Notes while on the Add/Edit entry screen for consistency with the ability to copy any of the other fields. See enclosed picture of v3.72pre Add/Edit screen Notes tab and suggestion of highligted area where a Copy Notes text might work.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MrMe</dc:creator><pubDate>Fri, 19 Jun 2026 13:24:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb0a17d48796b9cbb74244ba370c54d6bb439e1fc</guid></item></channel></rss>