passwordsafe-linux — For users and developers interested in the Linux (and Mac) port of PasswordSafe

[Passwordsafe-linux] Releasing PasswordSafe 1.19.0 [wx]

[pwsafe.org <ro...@pw...>]

Hi,

Although there are still open issues and work-in-progress, I've decided to
release a new wx version to track the latest Windows release, Thanks to all
for your contributions!

Any help in setting up a flatpak update appreciated.

Cheers,

Rony

[Passwordsafe-linux] PasswordSafe available on flathub

[pwsafe.org <ro...@pw...>]

Hi,

I'm pleased to announce that PasswordSafe is now available as a flatpak at
https://flathub.org/apps/org.pwsafe.pwsafe

This makes PasswordSafe available on a large number of Linux distributions
immediately, without having to build a custom package.

Thanks to igor2x for his help and patience.

Cheers,

Rony

[Passwordsafe-linux] Announcing PasswordSafe 1.16.0 for Linux

[pwsafe.org <ro...@pw...>]

Hi,

First PasswordSafe release of 2023 is for Linux distros, available at
https://github.com/pwsafe/pwsafe/releases/tag/1.16.0/
and
https://sourceforge.net/projects/passwordsafe/files/Linux/1.16.0/

If you'd like a release for a specific distro/architecture that's not in
the above, drop me a note and I'll see what I can do.

Cheers,

Rony

Re: [Passwordsafe-linux] Thoughts on TOTP/HOTP support in PasswordSafe?

[Bill B. <de...@bl...>]

Hi again,

Someone contacted me privately and suggested that HOTP might be
problematic, since the counter must be kept in sync with the server.

If the user has their database set to read-only, then that creates an
issue, as does recovering an older database from backup.

If we can find a way around those issues, then great.  If not, then it
would probably be better to only provide TOTP support.  (HTOP would
still need to be implemented because TOTP relies upon it, but we could
not expose it and keep it internal-only)

Bill



On Thu, Oct 03, 2019 at 11:18:02PM -0400, Bill Blough via Passwordsafe-linux wrote:
> Hi all,
> 
> I've been considering implementing TOTP/HOTP support in PasswordSafe.
> The idea is that you would be able to store the seed for a given
> account, then have PasswordSafe generate the TOTP/HOTP code as needed
> (instead of using something like Google Authenticator).
> 
> However, I've had some people (unrelated to this project) suggest that
> this is a Bad Idea^TM.  Since I'm writing this email, it's probably obvious
> that I disagree.  I'd be happy to explain my rationale if anyone wants to
> discuss it.
> 
> I do think it would be convenient functionality to have for those of use
> that would use it, and I'm willing to do the work.  Well, at least for
> core and wx.  I could probably do the Windows implementation too, but I
> haven't done Windows GUI programming in something like 20 years. As
> such, if someone else wanted to handle that piece, I'd be grateful.
> 
> That said, I don't want to spend the time and effort needed to implement
> it only to find out that everyone thinks I'm completely bonkers and that
> it will never get merged.
> 
> So is this something I should pursue, or should I skip it?
> 
> Regards,
> Bill
> 
> -- 
> GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84
> 
> 
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux

-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Re: [Passwordsafe-linux] [Passwordsafe-devel] Thoughts on TOTP/HOTP support in PasswordSafe?

[Bill B. <de...@bl...>]

Hi Mark,

Thanks for the info!  This definitely gives me more to think about.

Also, I very much appreciate the offer to answer questions.  I may take
you up on that at some point.

Regards,
Bill

On Fri, Oct 04, 2019 at 01:51:11PM +0100, Mark McGuill wrote:
> Hi there,
> 
> I've done a bit of work on this for my app (Strongbox) which supports
> KeePass and Password Safe.
> 
> In the KeePass windows world people used plugins to manage this feature. It
> has proven to be popular and has been made native in KeePassXC (A cross
> platform KeePass client) and also in my own app.
> 
> I'd be happy to help with any queries you have. Currently if a user adds a
> TOTP via my app to their Password Safe database I support this by appending
> an OTPAUTH url to their notes field (less than ideal but functional).
> 
> To answer one of the questions raised above:
> 
> - Are the specs for the various authenticators out there (Authy, Google
> Authenticator, etc.) publicly available and usable to implement a clone in
> pwsafe?
> Yes (the standard is RFC 6238)
> 
> Other things to think about off the top of my head for anyone looking to
> implement this:
> 
> - Parameters are often required (Hash Algorithm (usually SHA1), Number of
> Digits (usually 6), Period (usually 30 seconds))
> - OTPAUTH urls could be supported, they combine the parameters, the seed
> and some metadata like the Issuer, Name, Username and look like:
> 
> otpauth://totp/
> ACME%20Co:joh...@em...?secret=HXDMVJECJJWSRB3HWIZR4IFUGFTMXBOZ&issuer=ACME%20Co&algorithm=SHA1&digits=8&period=31
> 
> They are usually scanned from a QR Code.
> 
> - Some people use a variant of the standard RFC 6238 algo for use with
> "Steam" tokens, a gaming provider.
> 
> FWIW, this is handled in the KeePass world by using "Custom Fields",
> basically a feature that allows for a set of Key-Value Pairs. I don't
> believe the equivalent exists in the Password Safe world and you might not
> want to go that route anyway, but in short a TOTP configuration can be
> added to any entry alongside a regular password.
> 
> Hope that's helpful.
> 
> Best,
> -Mark
> 
> On Fri, 4 Oct 2019 at 09:07, pwsafe.org <ro...@pw...> wrote:
> 
> > Hi Tom,
> >
> > I think that Bill meant adding one time password support for
> > different sites, not for authenticating PasswordSafe itself using TOTP/HOTP.
> >
> > Yubikey is currently supported, including the ability to configure a
> > backup device as you described.
> >
> > Rony
> >
> > On Fri, Oct 4, 2019 at 7:38 AM Tom Mitchell <mi...@ni...> wrote:
> >
> >> On Thu, Oct 3, 2019 at 8:55 PM Bill Blough via Passwordsafe-linux
> >> <pas...@li...> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I've been considering implementing TOTP/HOTP support in PasswordSafe.
> >>
> >> It seems possible and interesting but I would rather add YubiKey  support
> >> first.
> >> One weakness with password managers is key management for the password
> >> manger
> >> software itself.  Two YubiKey device support please.   A pair of
> >> YubiKey  devices allows a second device to be
> >> kept in a sealed tamper evident envelop of the managers or company
> >> office safe. The encrypted password-safe file
> >> can be replicated as needed for portability.
> >>
> >> One problem with the Google and Microsoft Authentication  is they are
> >> tied to devices that
> >> are easy to misplace and also have fragile to strong unlock features.
> >> They are useful.
> >>
> >>
> >>
> >> --
> >>           T o m    M i t c h e l l ( o n   N i f t y E g g )
> >>
> >>
> >> _______________________________________________
> >> Passwordsafe-linux mailing list
> >> Pas...@li...
> >> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> >>
> >
> >
> > --
> > Ubi dubium, ibi libertas (where there is doubt, there is freedom)
> > _______________________________________________
> > Passwordsafe-devel mailing list
> > Pas...@li...
> > https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel
> >


> _______________________________________________
> Passwordsafe-devel mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel


-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Re: [Passwordsafe-linux] [Passwordsafe-devel] Thoughts on TOTP/HOTP support in PasswordSafe?

[Bill B. <de...@bl...>]

On Fri, Oct 04, 2019 at 08:13:07AM +0300, pwsafe.org wrote:
> A few thoughts:
> 
> - This will require format changes - at least one new field to indicate the
> entry is for a OTP, and not a "regular" password.

I was just looking through the format docs for V3 and V4, and they both
list "Two-Factor Key" as a (yet to be implemented) field type (0x1b).
Is it safe to assume we could use this?  Though we would still need
additional fields for OTP parameters (e.g., hash algorithm, length of the
generated code, etc.)

Since applications are supposed to be able to handle unknown fields in a
forward-compatible way, it seems like there shouldn't be an issue with
adding new fields to the existing formats (as opposed to waiting and
adding it to the next format).  Is this correct?


> - Are the specs for the various authenticators out there (Authy, Google
> Authenticator, etc.) publicly available and usable to implement a clone in
> pwsafe?

Yes, the HOTP spec is RFC4226 [1] and the TOTP spec is RFC6238 [2].
While I wouldn't be surprised if certain vendors had "peculiarities"
with their implementation, I'd expect the vast majority of differences
to be handled by changing the OTP parameters.

> - The biggest challenge for implementing this is to do so in a way that
> won't "penalize" the users of "classic" passwords. By "penalize" I mean
> require extra clicks/keystrokes over what's required today to create and
> use a given entry.

I'm open to other ideas, but my initial thought for the UI is

  - The entry's view/edit dialog would get an additional tab for
    OTP-related configuration.  On this tab, the user could enter their
    seed/key and configure their parameters.

    Since I expect that the average user doesn't want to have to know/care
    about which hash algorithm to choose and similar things, I think we
    could create some "presets" for common configurations, and give them
    user-friendly names/descriptions.  Then also have a way for advanced
    users to manually set the parameters if needed.

  - The entry's right-click menu would get two additional items:

      - Display Authenticator Code - opens a dialog that shows the code and
        time remaining indicator (similar to how "Display Password as QR
        Code" opens a dialog today).  This basically presents the same
        interface as most authenticator apps.  There could optionally be
        a button here to copy the code to the clipboard.

      - Copy Authenticator Code to Clipboard - copies the code to the
        clipboard.


If implemented as I described above, then the user might have to move
past two additional items in the right-click menu.  But I don't think
there would be any additional clicks to create/use an entry unless the
user decided to use OTP for that entry.


Bill



[1] https://tools.ietf.org/html/rfc4226
[2] https://tools.ietf.org/html/rfc6238



-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Re: [Passwordsafe-linux] [Passwordsafe-devel] Thoughts on TOTP/HOTP support in PasswordSafe?

[Mark M. <mar...@gm...>]

Hi there,

I've done a bit of work on this for my app (Strongbox) which supports
KeePass and Password Safe.

In the KeePass windows world people used plugins to manage this feature. It
has proven to be popular and has been made native in KeePassXC (A cross
platform KeePass client) and also in my own app.

I'd be happy to help with any queries you have. Currently if a user adds a
TOTP via my app to their Password Safe database I support this by appending
an OTPAUTH url to their notes field (less than ideal but functional).

To answer one of the questions raised above:

- Are the specs for the various authenticators out there (Authy, Google
Authenticator, etc.) publicly available and usable to implement a clone in
pwsafe?
Yes (the standard is RFC 6238)

Other things to think about off the top of my head for anyone looking to
implement this:

- Parameters are often required (Hash Algorithm (usually SHA1), Number of
Digits (usually 6), Period (usually 30 seconds))
- OTPAUTH urls could be supported, they combine the parameters, the seed
and some metadata like the Issuer, Name, Username and look like:

otpauth://totp/
ACME%20Co:joh...@em...?secret=HXDMVJECJJWSRB3HWIZR4IFUGFTMXBOZ&issuer=ACME%20Co&algorithm=SHA1&digits=8&period=31

They are usually scanned from a QR Code.

- Some people use a variant of the standard RFC 6238 algo for use with
"Steam" tokens, a gaming provider.

FWIW, this is handled in the KeePass world by using "Custom Fields",
basically a feature that allows for a set of Key-Value Pairs. I don't
believe the equivalent exists in the Password Safe world and you might not
want to go that route anyway, but in short a TOTP configuration can be
added to any entry alongside a regular password.

Hope that's helpful.

Best,
-Mark

On Fri, 4 Oct 2019 at 09:07, pwsafe.org <ro...@pw...> wrote:

> Hi Tom,
>
> I think that Bill meant adding one time password support for
> different sites, not for authenticating PasswordSafe itself using TOTP/HOTP.
>
> Yubikey is currently supported, including the ability to configure a
> backup device as you described.
>
> Rony
>
> On Fri, Oct 4, 2019 at 7:38 AM Tom Mitchell <mi...@ni...> wrote:
>
>> On Thu, Oct 3, 2019 at 8:55 PM Bill Blough via Passwordsafe-linux
>> <pas...@li...> wrote:
>> >
>> > Hi all,
>> >
>> > I've been considering implementing TOTP/HOTP support in PasswordSafe.
>>
>> It seems possible and interesting but I would rather add YubiKey  support
>> first.
>> One weakness with password managers is key management for the password
>> manger
>> software itself.  Two YubiKey device support please.   A pair of
>> YubiKey  devices allows a second device to be
>> kept in a sealed tamper evident envelop of the managers or company
>> office safe. The encrypted password-safe file
>> can be replicated as needed for portability.
>>
>> One problem with the Google and Microsoft Authentication  is they are
>> tied to devices that
>> are easy to misplace and also have fragile to strong unlock features.
>> They are useful.
>>
>>
>>
>> --
>>           T o m    M i t c h e l l ( o n   N i f t y E g g )
>>
>>
>> _______________________________________________
>> Passwordsafe-linux mailing list
>> Pas...@li...
>> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>>
>
>
> --
> Ubi dubium, ibi libertas (where there is doubt, there is freedom)
> _______________________________________________
> Passwordsafe-devel mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel
>

Re: [Passwordsafe-linux] Thoughts on TOTP/HOTP support in PasswordSafe?

[pwsafe.org <ro...@pw...>]

Hi Tom,

I think that Bill meant adding one time password support for
different sites, not for authenticating PasswordSafe itself using TOTP/HOTP.

Yubikey is currently supported, including the ability to configure a backup
device as you described.

Rony

On Fri, Oct 4, 2019 at 7:38 AM Tom Mitchell <mi...@ni...> wrote:

> On Thu, Oct 3, 2019 at 8:55 PM Bill Blough via Passwordsafe-linux
> <pas...@li...> wrote:
> >
> > Hi all,
> >
> > I've been considering implementing TOTP/HOTP support in PasswordSafe.
>
> It seems possible and interesting but I would rather add YubiKey  support
> first.
> One weakness with password managers is key management for the password
> manger
> software itself.  Two YubiKey device support please.   A pair of
> YubiKey  devices allows a second device to be
> kept in a sealed tamper evident envelop of the managers or company
> office safe. The encrypted password-safe file
> can be replicated as needed for portability.
>
> One problem with the Google and Microsoft Authentication  is they are
> tied to devices that
> are easy to misplace and also have fragile to strong unlock features.
> They are useful.
>
>
>
> --
>           T o m    M i t c h e l l ( o n   N i f t y E g g )
>
>
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>


-- 
Ubi dubium, ibi libertas (where there is doubt, there is freedom)

Re: [Passwordsafe-linux] Thoughts on TOTP/HOTP support in PasswordSafe?

[Tom M. <mi...@ni...>]

On Thu, Oct 3, 2019 at 8:55 PM Bill Blough via Passwordsafe-linux
<pas...@li...> wrote:
>
> Hi all,
>
> I've been considering implementing TOTP/HOTP support in PasswordSafe.

It seems possible and interesting but I would rather add YubiKey  support first.
One weakness with password managers is key management for the password manger
software itself.  Two YubiKey device support please.   A pair of
YubiKey  devices allows a second device to be
kept in a sealed tamper evident envelop of the managers or company
office safe. The encrypted password-safe file
can be replicated as needed for portability.

One problem with the Google and Microsoft Authentication  is they are
tied to devices that
are easy to misplace and also have fragile to strong unlock features.
They are useful.



-- 
          T o m    M i t c h e l l ( o n   N i f t y E g g )

Re: [Passwordsafe-linux] [Passwordsafe-devel] Thoughts on TOTP/HOTP support in PasswordSafe?

[pwsafe.org <ro...@pw...>]

A few thoughts:

- This will require format changes - at least one new field to indicate the
entry is for a OTP, and not a "regular" password.
- Are the specs for the various authenticators out there (Authy, Google
Authenticator, etc.) publicly available and usable to implement a clone in
pwsafe?
- The biggest challenge for implementing this is to do so in a way that
won't "penalize" the users of "classic" passwords. By "penalize" I mean
require extra clicks/keystrokes over what's required today to create and
use a given entry.

Discussion?

On Fri, Oct 4, 2019 at 6:18 AM Bill Blough via Passwordsafe-devel <
pas...@li...> wrote:

> Hi all,
>
> I've been considering implementing TOTP/HOTP support in PasswordSafe.
> The idea is that you would be able to store the seed for a given
> account, then have PasswordSafe generate the TOTP/HOTP code as needed
> (instead of using something like Google Authenticator).
>
> However, I've had some people (unrelated to this project) suggest that
> this is a Bad Idea^TM.  Since I'm writing this email, it's probably obvious
> that I disagree.  I'd be happy to explain my rationale if anyone wants to
> discuss it.
>
> I do think it would be convenient functionality to have for those of use
> that would use it, and I'm willing to do the work.  Well, at least for
> core and wx.  I could probably do the Windows implementation too, but I
> haven't done Windows GUI programming in something like 20 years. As
> such, if someone else wanted to handle that piece, I'd be grateful.
>
> That said, I don't want to spend the time and effort needed to implement
> it only to find out that everyone thinks I'm completely bonkers and that
> it will never get merged.
>
> So is this something I should pursue, or should I skip it?
>
> Regards,
> Bill
>
> --
> GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84
>
>
> _______________________________________________
> Passwordsafe-devel mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel
>


-- 
Ubi dubium, ibi libertas (where there is doubt, there is freedom)

[Passwordsafe-linux] Thoughts on TOTP/HOTP support in PasswordSafe?

[Bill B. <de...@bl...>]

Hi all,

I've been considering implementing TOTP/HOTP support in PasswordSafe.
The idea is that you would be able to store the seed for a given
account, then have PasswordSafe generate the TOTP/HOTP code as needed
(instead of using something like Google Authenticator).

However, I've had some people (unrelated to this project) suggest that
this is a Bad Idea^TM.  Since I'm writing this email, it's probably obvious
that I disagree.  I'd be happy to explain my rationale if anyone wants to
discuss it.

I do think it would be convenient functionality to have for those of use
that would use it, and I'm willing to do the work.  Well, at least for
core and wx.  I could probably do the Windows implementation too, but I
haven't done Windows GUI programming in something like 20 years. As
such, if someone else wanted to handle that piece, I'd be grateful.

That said, I don't want to spend the time and effort needed to implement
it only to find out that everyone thinks I'm completely bonkers and that
it will never get merged.

So is this something I should pursue, or should I skip it?

Regards,
Bill

-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Bill B. <de...@bl...>]

On Sat, Jul 06, 2019 at 01:17:55PM +0300, pwsafe.org wrote:
> So now I'm considering three options:
> 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> 3. Switch to the Qt UI framework, which appears to be much more polished
> than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> Source License is GPL 2/3, but I think that this is compatible with the
> project's license (that is, I think a mixed license would work).
> 

I think consolidating to one cross-platform UI makes sense from an
implementation/maintenance standpoint.

I expect that the quickest way forward would be #2 (switch the Windows
version to use wx).

Then if it's decided that QT is a better choice, that migration could
happen in the future for all platforms at the same time.


Just my 2c.

Bill





> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux


-- 
GPG: 5CDD 0C9C F446 BC1B 2509  8791 1762 E022 7034 CF84

[Passwordsafe-linux] VB: SV: PasswordSafe's Windows UI frameworks

[PER T. <per...@op...>]

---- Ursprungligt meddelande ----
Ämne: SV: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks
Skickat: 8 juli 2019 10:53
Från: PER Tunedal <per...@op...>
Till: "pwsafe.org" <ro...@pw...>
Kopia: 

Hi, 
It all depends on what users you target. For a pure Windows user, it's confusing and annoying if the interface doesn't follow the Windows standard. If the look and feel is different and the logic is different. You might easily be lost and give up, rather than have to learn something new. And the software might not look professional, poor quality might be inferred. 

Qt-programs had a very old fashioned look, some years ago. I don't know what it's like nowadays. 

On the other hand interoperability is important. Everyone has a smartphone. I think there might be even more iPhone users than Linux users?

I use Windows, different flavors of Linux and an Android phone. My family all use Windows and iPhone. We all use iPad. 

Maybe you have a good knowledge of the current users. How many percent are using each platform? What platforms are increasing? 

Yours, 
Per Tunedal 

Skickat från min Xperia™-smartphone från Sony

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Scott R. <sr...@fi...>]

My first thought is 'watever is going to make your life easiest in the
long run' - I suspect te Qt UI framework may be te answer there, but
am not certain.

My second thought echoes that of all the other replies you've gotten -
anything that makes the Linux version better / easier.  I'm using the
Windows version at work, the Linux version at home.

On Sat, Jul 06, 2019 at 01:17:55PM +0300, pwsafe.org wrote:
> Hi,
> 
> I'm at a crossroad with regards to the Windows version of PasswordSafe, and
> would like to get input from the members of this list.
> 
> PasswordSafe's Windows UI is built directly upon MFC from the first
> releases. This means that over time, we've enhanced MFC's functionality by
> deriving classes from MFC with functionality "borrowed" from other sources.
> 
> Case in point: CPWToolbar is derived from the CToolBar MFC class, with code
> added to support the PasswordSafe graphics. Problem is, new display
> technology is poorly supported by CPWToolBar::CToolBar.
> 
> Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
> the new functionality that was previously hand-coded in CPWToolBar. The
> switch to CPWToolBar::CMFCToolBar, however, is non-trivial.
> 
> Also, the PasswordSafe Windows UI is getting a bit old, compared to today's
> programs, and could use a general facelift.
> 
> So now I'm considering three options:
> 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> 3. Switch to the Qt UI framework, which appears to be much more polished
> than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> Source License is GPL 2/3, but I think that this is compatible with the
> project's license (that is, I think a mixed license would work).
> 
> Thoughts, anyone?

-- 
Scott Raun
sr...@fi...

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Bill W. <wo...@ne...>]

My vote would be to spend that time improving the Linux version.

I also use the Java version on my Macs and the Android version.

Thanks very much for maintaining this incredibly useful program!

pwsafe.org <ro...@pw...> wrote:

> Hi,
> 
> I'm at a crossroad with regards to the Windows version of PasswordSafe, and would
> like to get input from the members of this list.
> 
> PasswordSafe's Windows UI is built directly upon MFC from the first releases. This
> means that over time, we've enhanced MFC's functionality by deriving classes from
> MFC with functionality "borrowed" from other sources.
> 
> Case in point: CPWToolbar is derived from the CToolBar MFC class, with code added to
> support the PasswordSafe graphics. Problem is, new display technology is poorly
> supported by CPWToolBar::CToolBar.
> 
> Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of the new
> functionality that was previously hand-coded in CPWToolBar. The switch to
> CPWToolBar::CMFCToolBar, however, is non-trivial.
> 
> Also, the PasswordSafe Windows UI is getting a bit old, compared to today's
> programs, and could use a general facelift.
> 
> So now I'm considering three options:
> 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> 3. Switch to the Qt UI framework, which appears to be much more polished than
> wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open Source License is
> GPL 2/3, but I think that this is compatible with the project's license (that is, I
> think a mixed license would work).
> 
> Thoughts, anyone?
> 
> Rony
> 
> 
> ----------------------------------------------------
> Alternatives:
> 
> ----------------------------------------------------
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux

-- 
Bill Wohler <wo...@ne...> aka <Bil...@na...>
http://www.newt.com/wohler/, GnuPG ID:610BD9AD

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Bill D. <bi...@du...>]

On 7/6/19 9:52 AM, DJC wrote:
> Hi, Rony.
> 
> Good question.  As a user of both Linux and Windows, I'd far prefer an 
> interface that's as similar as possible between the two, and I don't 
> give a hoot for the Windows version to have a "pure Windows" flavor.  It 
> does seem to me that using a library that basically supports more than 
> one OS is a great advantage for future maintenance and development.

This is pretty much my opinion as well.

And thanks to the developers and maintainers for all the hard work you do.

-- 
Bill D. <bi...@du...>

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Todd L. <ut...@em...>]

Last Windows I used was WinME. I'd like Windows folks to have usable software, but like Jaap, I'm personally more concerned with play-nice-with-Linux. -- Todd

On 7/6/19 8:57 AM, Jaap Berkhout wrote:

Hi Rony,

December last year I switched from Windows 7 Ultimate to Linux Mint 19.
   I therefore use the Linux version of PasswordSafe (version 1.08.1).
I realize that the Linux users are (at the moment) a small subgroup of
your users.  Still, as far as I am concerned, a switch to a (sub)system
that plays nice with Linux has preference.

On 06.07.19 12:17, pwsafe.org wrote:


Hi,

I'm at a crossroad with regards to the Windows version of PasswordSafe,
and would like to get input from the members of this list.

PasswordSafe's Windows UI is built directly upon MFC from the first
releases. This means that over time, we've enhanced MFC's functionality
by deriving classes from MFC with functionality "borrowed" from other
sources.

Case in point: CPWToolbar is derived from the CToolBar MFC class, with
code added to support the PasswordSafe graphics. Problem is, new display
technology is poorly supported by CPWToolBar::CToolBar.

Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
the new functionality that was previously hand-coded in CPWToolBar. The
switch to CPWToolBar::CMFCToolBar, however, is non-trivial.

Also, the PasswordSafe Windows UI is getting a bit old, compared to
today's programs, and could use a general facelift.

So now I'm considering three options:
1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
2. Switch to the wxWidgets UI for Windows as the shipping UI.
3. Switch to the Qt UI framework, which appears to be much more polished
than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
Source License is GPL 2/3, but I think that this is compatible with the
project's license (that is, I think a mixed license would work).

Thoughts, anyone?

Rony


_______________________________________________
Passwordsafe-linux mailing list
Pas...@li...<mailto:Pas...@li...>
https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux









_______________________________________________
Passwordsafe-linux mailing list
Pas...@li...<mailto:Pas...@li...>
https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[DJC <dj...@re...>]

Hi, Rony.

Good question.  As a user of both Linux and Windows, I'd far prefer an 
interface that's as similar as possible between the two, and I don't give a 
hoot for the Windows version to have a "pure Windows" flavor.  It does seem 
to me that using a library that basically supports more than one OS is a 
great advantage for future maintenance and development.

Pete

On 06-Jul-19 12:17, pwsafe.org wrote:
> Hi,
> 
> I'm at a crossroad with regards to the Windows version of PasswordSafe, and
> would like to get input from the members of this list.
> 
> PasswordSafe's Windows UI is built directly upon MFC from the first
> releases. This means that over time, we've enhanced MFC's functionality by
> deriving classes from MFC with functionality "borrowed" from other sources.
> 
> Case in point: CPWToolbar is derived from the CToolBar MFC class, with code
> added to support the PasswordSafe graphics. Problem is, new display
> technology is poorly supported by CPWToolBar::CToolBar.
> 
> Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
> the new functionality that was previously hand-coded in CPWToolBar. The
> switch to CPWToolBar::CMFCToolBar, however, is non-trivial.
> 
> Also, the PasswordSafe Windows UI is getting a bit old, compared to today's
> programs, and could use a general facelift.
> 
> So now I'm considering three options:
> 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> 3. Switch to the Qt UI framework, which appears to be much more polished
> than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> Source License is GPL 2/3, but I think that this is compatible with the
> project's license (that is, I think a mixed license would work).
> 
> Thoughts, anyone?
> 
> Rony 
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> 

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[William B. <cur...@gm...>]

I agree with Jaap.

On Sat, Jul 6, 2019 at 7:58 AM Jaap Berkhout <j.j...@xs...> wrote:

> Hi Rony,
>
> December last year I switched from Windows 7 Ultimate to Linux Mint 19.
>    I therefore use the Linux version of PasswordSafe (version 1.08.1).
> I realize that the Linux users are (at the moment) a small subgroup of
> your users.  Still, as far as I am concerned, a switch to a (sub)system
> that plays nice with Linux has preference.
>
> On 06.07.19 12:17, pwsafe.org wrote:
> > Hi,
> >
> > I'm at a crossroad with regards to the Windows version of PasswordSafe,
> > and would like to get input from the members of this list.
> >
> > PasswordSafe's Windows UI is built directly upon MFC from the first
> > releases. This means that over time, we've enhanced MFC's functionality
> > by deriving classes from MFC with functionality "borrowed" from other
> > sources.
> >
> > Case in point: CPWToolbar is derived from the CToolBar MFC class, with
> > code added to support the PasswordSafe graphics. Problem is, new display
> > technology is poorly supported by CPWToolBar::CToolBar.
> >
> > Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
> > the new functionality that was previously hand-coded in CPWToolBar. The
> > switch to CPWToolBar::CMFCToolBar, however, is non-trivial.
> >
> > Also, the PasswordSafe Windows UI is getting a bit old, compared to
> > today's programs, and could use a general facelift.
> >
> > So now I'm considering three options:
> > 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> > 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> > 3. Switch to the Qt UI framework, which appears to be much more polished
> > than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> > Source License is GPL 2/3, but I think that this is compatible with the
> > project's license (that is, I think a mixed license would work).
> >
> > Thoughts, anyone?
> >
> > Rony
> >
> >
> > _______________________________________________
> > Passwordsafe-linux mailing list
> > Pas...@li...
> > https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> >
>
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Keith M. <j.k...@gm...>]

As a user who relies on pwsafe to sync my pws between Linux, Android and
Windows devices I second Jaap B's vote for the solution most amenable to
multiplatform support.
Keith Morgan

sent from my mobile phone

On Sat, Jul 6, 2019, 08:58 Jaap Berkhout <j.j...@xs...> wrote:

> Hi Rony,
>
> December last year I switched from Windows 7 Ultimate to Linux Mint 19.
>    I therefore use the Linux version of PasswordSafe (version 1.08.1).
> I realize that the Linux users are (at the moment) a small subgroup of
> your users.  Still, as far as I am concerned, a switch to a (sub)system
> that plays nice with Linux has preference.
>
> On 06.07.19 12:17, pwsafe.org wrote:
> > Hi,
> >
> > I'm at a crossroad with regards to the Windows version of PasswordSafe,
> > and would like to get input from the members of this list.
> >
> > PasswordSafe's Windows UI is built directly upon MFC from the first
> > releases. This means that over time, we've enhanced MFC's functionality
> > by deriving classes from MFC with functionality "borrowed" from other
> > sources.
> >
> > Case in point: CPWToolbar is derived from the CToolBar MFC class, with
> > code added to support the PasswordSafe graphics. Problem is, new display
> > technology is poorly supported by CPWToolBar::CToolBar.
> >
> > Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
> > the new functionality that was previously hand-coded in CPWToolBar. The
> > switch to CPWToolBar::CMFCToolBar, however, is non-trivial.
> >
> > Also, the PasswordSafe Windows UI is getting a bit old, compared to
> > today's programs, and could use a general facelift.
> >
> > So now I'm considering three options:
> > 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> > 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> > 3. Switch to the Qt UI framework, which appears to be much more polished
> > than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> > Source License is GPL 2/3, but I think that this is compatible with the
> > project's license (that is, I think a mixed license would work).
> >
> > Thoughts, anyone?
> >
> > Rony
> >
> >
> > _______________________________________________
> > Passwordsafe-linux mailing list
> > Pas...@li...
> > https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> >
>
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>

Re: [Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[Jaap B. <j.j...@xs...>]

Hi Rony,

December last year I switched from Windows 7 Ultimate to Linux Mint 19.
   I therefore use the Linux version of PasswordSafe (version 1.08.1).
I realize that the Linux users are (at the moment) a small subgroup of
your users.  Still, as far as I am concerned, a switch to a (sub)system
that plays nice with Linux has preference.

On 06.07.19 12:17, pwsafe.org wrote:
> Hi,
> 
> I'm at a crossroad with regards to the Windows version of PasswordSafe,
> and would like to get input from the members of this list.
> 
> PasswordSafe's Windows UI is built directly upon MFC from the first
> releases. This means that over time, we've enhanced MFC's functionality
> by deriving classes from MFC with functionality "borrowed" from other
> sources.
> 
> Case in point: CPWToolbar is derived from the CToolBar MFC class, with
> code added to support the PasswordSafe graphics. Problem is, new display
> technology is poorly supported by CPWToolBar::CToolBar.
> 
> Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
> the new functionality that was previously hand-coded in CPWToolBar. The
> switch to CPWToolBar::CMFCToolBar, however, is non-trivial.
> 
> Also, the PasswordSafe Windows UI is getting a bit old, compared to
> today's programs, and could use a general facelift.
> 
> So now I'm considering three options:
> 1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
> 2. Switch to the wxWidgets UI for Windows as the shipping UI.
> 3. Switch to the Qt UI framework, which appears to be much more polished
> than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
> Source License is GPL 2/3, but I think that this is compatible with the
> project's license (that is, I think a mixed license would work).
> 
> Thoughts, anyone?
> 
> Rony
> 
> 
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> 

[Passwordsafe-linux] PasswordSafe's Windows UI frameworks

[pwsafe.org <ro...@pw...>]

Hi,

I'm at a crossroad with regards to the Windows version of PasswordSafe, and
would like to get input from the members of this list.

PasswordSafe's Windows UI is built directly upon MFC from the first
releases. This means that over time, we've enhanced MFC's functionality by
deriving classes from MFC with functionality "borrowed" from other sources.

Case in point: CPWToolbar is derived from the CToolBar MFC class, with code
added to support the PasswordSafe graphics. Problem is, new display
technology is poorly supported by CPWToolBar::CToolBar.

Micorsoft has replaced CToolBar with CMFCToolBar, which contains much of
the new functionality that was previously hand-coded in CPWToolBar. The
switch to CPWToolBar::CMFCToolBar, however, is non-trivial.

Also, the PasswordSafe Windows UI is getting a bit old, compared to today's
programs, and could use a general facelift.

So now I'm considering three options:
1. Local fix: Move from CPWToolBar::CToolBar to CPWToolBar::CMFCToolBar
2. Switch to the wxWidgets UI for Windows as the shipping UI.
3. Switch to the Qt UI framework, which appears to be much more polished
than wxWidgets, for Windows, and perhaps for Linux as well. The Qt Open
Source License is GPL 2/3, but I think that this is compatible with the
project's license (that is, I think a mixed license would work).

Thoughts, anyone?

Rony

[Passwordsafe-linux] PasswordSafe for Linux 1.08BETA is out

[pwsafe.org <ro...@pw...>]

Hi,

I've uploaded some debs and rpms for the above in
https://github.com/pwsafe/pwsafe/releases/tag/1.07BETA
and
https://sourceforge.net/projects/passwordsafe/files/Linux-BETA/1.08BETA/

Thanks to all contributors, especially SauravG and RafaelX.

Cheers,

  Rony

Re: [Passwordsafe-linux] Missing libcurl

[pwsafe.org <ro...@pw...>]

Hi,

libcurl is used in 1.07 to fix the ability to check for newer releases via
Help->About.

Looks like libcurl isn't installed by default on Linux Mint Cinnamon.

I've added an explicit requirement for the libcurl package in the Linux
Debian build. If someone would care to gie it a spin, it's in
https://pwsafe.org/tmp/passwordsafe-debian-1.07.1-BETA.amd64.deb (sig in
https://pwsafe.org/tmp/passwordsafe-debian-1.07.1-BETA.amd64.deb.sig).

Cheers,

  Rony

On Sat, Jan 5, 2019 at 6:27 PM Loren Wilson <net...@gm...> wrote:

> More information about the missing libcurl.so.4.
> System running Linux Mint 18.3 KDE 64-bit, with Linux 4.15.0-42-generic
> installs and runs fine.
> System running Linux Mint 18.3 Cinnamon 64-bit, with Linux
> 4.15.0-42-generic fails to install correctly and then fails with the error
> about the missing libcurl.so.4
> I have to revert clear back to PasswordSafe Linux 1.03 Beta to get a
> running install on the Cinnamon system.
> Sorry, gmail does not give the option of changing the subject line.
>
> On Thu, Jan 3, 2019 at 5:00 AM <
> pas...@li...> wrote:
>
>> Send Passwordsafe-linux mailing list submissions to
>>         pas...@li...
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>> or, via email, send a message with subject or body 'help' to
>>         pas...@li...
>>
>> You can reach the person managing the list at
>>         pas...@li...
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Passwordsafe-linux digest..."
>>
>>
>> Today's Topics:
>>
>>    1. PasswordSafe Linux Beta release 1.07 (pwsafe.org)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 2 Jan 2019 17:29:58 +0200
>> From: "pwsafe.org" <ro...@pw...>
>> To: Pas...@li...
>> Cc: PasswordSafe Developers <pas...@li...>
>> Subject: [Passwordsafe-linux] PasswordSafe Linux Beta release 1.07
>> Message-ID:
>>         <CAKUoDdKYUvCPeqYftB5J+BeqaYuVSMbp+=
>> hkG...@ma...>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>>
>> PasswordSafe Linux 1.07 Beta is formally released.
>>
>> Packages for Debian, Ubuntu and Fedora may be downloaded from
>> https://github.com/pwsafe/pwsafe/releases/tag/1.07BETA
>> or
>> https://sourceforge.net/projects/passwordsafe/files/Linux-BETA/1.07BETA/
>>
>> Let me know if you need a build for another distro, and I'll see what I
>> can
>> do.
>>
>> Thanks to Rafael, Sauravg, pm_kan, and dskrvk for their contributions, and
>> to all who submitted bug reports, suggestions and the occasional donation.
>>
>> Happy 2019 to all.
>>
>> Rony
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Passwordsafe-linux mailing list
>> Pas...@li...
>> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>>
>>
>> ------------------------------
>>
>> End of Passwordsafe-linux Digest, Vol 15, Issue 1
>> *************************************************
>>
>
>
> --
> Thanks,
> Loren Wilson
> 13073 N Hohokam Rd
> Florence, AZ 85132
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>


-- 
Ubi dubium, ibi libertas (where there is doubt, there is freedom)

Re: [Passwordsafe-linux] Passwordsafe-linux Digest, Vol 15, Issue 1

[Loren W. <net...@gm...>]

More information about the missing libcurl.so.4.
System running Linux Mint 18.3 KDE 64-bit, with Linux 4.15.0-42-generic
installs and runs fine.
System running Linux Mint 18.3 Cinnamon 64-bit, with Linux
4.15.0-42-generic fails to install correctly and then fails with the error
about the missing libcurl.so.4
I have to revert clear back to PasswordSafe Linux 1.03 Beta to get a
running install on the Cinnamon system.
Sorry, gmail does not give the option of changing the subject line.

On Thu, Jan 3, 2019 at 5:00 AM <
pas...@li...> wrote:

> Send Passwordsafe-linux mailing list submissions to
>         pas...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
> or, via email, send a message with subject or body 'help' to
>         pas...@li...
>
> You can reach the person managing the list at
>         pas...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Passwordsafe-linux digest..."
>
>
> Today's Topics:
>
>    1. PasswordSafe Linux Beta release 1.07 (pwsafe.org)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 2 Jan 2019 17:29:58 +0200
> From: "pwsafe.org" <ro...@pw...>
> To: Pas...@li...
> Cc: PasswordSafe Developers <pas...@li...>
> Subject: [Passwordsafe-linux] PasswordSafe Linux Beta release 1.07
> Message-ID:
>         <CAKUoDdKYUvCPeqYftB5J+BeqaYuVSMbp+=
> hkG...@ma...>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> PasswordSafe Linux 1.07 Beta is formally released.
>
> Packages for Debian, Ubuntu and Fedora may be downloaded from
> https://github.com/pwsafe/pwsafe/releases/tag/1.07BETA
> or
> https://sourceforge.net/projects/passwordsafe/files/Linux-BETA/1.07BETA/
>
> Let me know if you need a build for another distro, and I'll see what I can
> do.
>
> Thanks to Rafael, Sauravg, pm_kan, and dskrvk for their contributions, and
> to all who submitted bug reports, suggestions and the occasional donation.
>
> Happy 2019 to all.
>
> Rony
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Passwordsafe-linux mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-linux
>
>
> ------------------------------
>
> End of Passwordsafe-linux Digest, Vol 15, Issue 1
> *************************************************
>


-- 
Thanks,
Loren Wilson
13073 N Hohokam Rd
Florence, AZ 85132