passwordsafe-devel Mailing List for Password Safe
Popular easy-to-use and secure password manager
Brought to you by:
ronys
You can subscribe to this list here.
| 2002 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
|
May
(18) |
Jun
(11) |
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(67) |
May
(96) |
Jun
(16) |
Jul
(26) |
Aug
(9) |
Sep
(7) |
Oct
(11) |
Nov
|
Dec
(19) |
| 2004 |
Jan
(13) |
Feb
(27) |
Mar
(20) |
Apr
(9) |
May
|
Jun
(1) |
Jul
(5) |
Aug
(47) |
Sep
(12) |
Oct
(2) |
Nov
(5) |
Dec
(21) |
| 2005 |
Jan
(27) |
Feb
(5) |
Mar
(3) |
Apr
(10) |
May
(12) |
Jun
(8) |
Jul
(22) |
Aug
(4) |
Sep
(1) |
Oct
(2) |
Nov
(41) |
Dec
(15) |
| 2006 |
Jan
(17) |
Feb
(15) |
Mar
(14) |
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
(5) |
Aug
|
Sep
(2) |
Oct
(12) |
Nov
(12) |
Dec
(3) |
| 2007 |
Jan
(1) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(35) |
Jun
(4) |
Jul
(4) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
(2) |
Dec
|
| 2008 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
(1) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(14) |
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(8) |
Jul
(3) |
Aug
|
Sep
(3) |
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(2) |
May
|
Jun
(4) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(2) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
(4) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(5) |
| 2015 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
(1) |
Dec
(2) |
| 2016 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2018 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(9) |
Nov
|
Dec
(2) |
| 2020 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
|
| 2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2026 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(2) |
2
|
|
3
|
4
|
5
|
6
|
7
|
8
(2) |
9
|
|
10
|
11
(2) |
12
|
13
|
14
|
15
|
16
|
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
|
24
|
25
|
26
(1) |
27
(1) |
28
|
29
|
30
(1) |
|
31
|
|
|
|
|
|
|
|
From: Rony S. <ro...@gm...> - 2003-08-30 05:51:20
|
Hi Wren, Very odd - the lib file appears to be the same I'm using. Are you sure that you've set the project settings correctly to actually link against the library? In the Link tab, category Input: it should be listed in Object/library modules, and the Additional library path: should have the directory under which you've saved it (in my case, C:\local\vc98\HTML Help Workshop\lib). If this doesn't help, you might want to enable "Print progress messages" (under Link in the Customize category), to get a better idea of what the linker is actually doing. Hope this, er, helps.... Rony > -----Original Message----- > From: pas...@li... > [mailto:pas...@li...]On Behalf > Of J. Wren Hunt > Sent: Tuesday, August 26, 2003 5:53 PM > To: pas...@li... > Subject: [Passwordsafe-devel] HTMLHelp > > > Hi! I know I'm doing something incredibly stupid and brain-dead, > but I can't figure out how to get > rid of the linker errors I get when linking the PasswordSafe > files which call HtmlHelp(). > > I get 9 errors like: > > PasskeyEntry.obj : error LNK2001: unresolved external symbol > "void __cdecl > HtmlHelp(int,char *,int,int)" (?HtmlHelp@@YAXHPADHH@Z) > > > I read the HOWTO article on MSDN "186907 - HOWTO: Set Up Visual > C++ to Use the HTML Help API" > > and here's the details of the library I'm linking against: > HTMLHELP LIB 34,904 05-24-00 9:24a > > And the prototype for HtmlHelp looks like: > > void HtmlHelp(int, char*, int, int); > > Is this the correct date/size of the library? Help! (Pun > Intended!) Thanks in advance! > > Wren > |
|
From: <Aj...@ao...> - 2003-08-27 06:09:23
|
Hi Thanks for the brilliant work you are doing! I have a question related to the creation date for specific passwords using version 1.7 of the password safe. I errantly saved the passwords in multiple databases and have somehow have gotten many old passwords and new passwords all mixed up in different databases. I go to a site, copy what I think to be the newest password, only to find that the password is incorrect (it's probably in one of the other databases) Is there a way with either 1.7 or 1.92 to sort out the old and the new with a creation date, for a user either by combining all the databases into one and without replacing ones with the same name? Are they dated? Can they be dated? Can the program warn me with a popup that "THIS IS NOT THE MOST RECENT DATABASE"? Can I view or print out the lists of users/passwords so as to compare them? My only option right now is to got to each site and try one database after another until I find the correct one. I know it's my fault for mixing up the databases I saved one on my hard drive, and the same one on my floppy, but did not update both backups at the same time. So when I looked for a database to open sometimes I opened and used the outdated database. however this is where I have to start from. If I had to do it all over again, I would not keep databases without being able to access and control them. Thanks, I hope you can help me. Also, I know the program is meant to remain a simple program but I felt like tossing some questions and ideas up in the air. I know it would make the program more complicated but it could make the program simpler, to use. Thanks, Andy Lapinski |
|
From: J. W. H. <wre...@ne...> - 2003-08-26 15:53:13
|
Hi! I know I'm doing something incredibly stupid and brain-dead, but I can't figure out how to get
rid of the linker errors I get when linking the PasswordSafe files which call HtmlHelp().
I get 9 errors like:
PasskeyEntry.obj : error LNK2001: unresolved external symbol "void __cdecl
HtmlHelp(int,char *,int,int)" (?HtmlHelp@@YAXHPADHH@Z)
I read the HOWTO article on MSDN "186907 - HOWTO: Set Up Visual C++ to Use the HTML Help API"
and here's the details of the library I'm linking against:
HTMLHELP LIB 34,904 05-24-00 9:24a
And the prototype for HtmlHelp looks like:
void HtmlHelp(int, char*, int, int);
Is this the correct date/size of the library? Help! (Pun Intended!) Thanks in advance!
Wren
|
|
From: Rony S. <ro...@gm...> - 2003-08-11 05:56:13
|
Hi Simon, Thanks for your kind words. We write the software to scratch our own itch, but it's always nice to know that others find it useful as well. Cheers, Rony > -----Original Message----- > From: LEMIRE, SIMON [mailto:sim...@be...] > Sent: Sun, 10 Aug 2003 21:45 > To: ro...@us... > Subject: Great work on password safe > > > Hi there! > I just wanted to congratulate you on your work with Password Safe, it's > a great piece of software that I use very often. I'm still trying to > convince my coworkers to use Password Safe instead of writing password > on pieces of paper though... ;) > > l8er! > > |
|
From: Rony S. <ro...@gm...> - 2003-08-11 04:26:09
|
Hi, Release 1.92c is available for download. This is a maintenance release, fixing a few minor annoyances: Bugfix [783314] Clearing the clipboard now properly trashes the password in process memory, as well as emptying the clipboard. Bugfix [760656] Passing a filename that contains spaces via the command line now works correctly. Previously, the quotation marks confused PasswordSafe. Bugfix [777367] The Edit/View Item dialog box's Help button now works correctly. RFE [772212] Pressing Cancel when prompted for the password when unminimizing the application no longer exits the program. (Would happen only if "Lock password database on minimize" is set) Bugfix [769820] Pressing Cancel in the Clear Clipboard dialog box will now prevent the passowrd from being copied to the clipboard. Previously, it was equivalent to pressing OK. (Would happen only if "Confirm item copy to clipboard" was selected) RFE [768870] Added a manifest file for native Windows XP theme support. RFE [754790] The option "Clear the clipboard when minimized" has been changed to "Clear clipboard upon minimize or exit". Previously, the clipboard was unconditionally cleared upon exit. This allows the user to change the behaviour. The PocketPC release incorporates the fixes of the Windows release. In addition, the endianness of devices built around the SH3 CPU is now correct. Thanks to Gregg and Karlo for their work fixing the bugs, and to Kevin for building the PocketPC versions. Link to files: https://sourceforge.net/project/showfiles.php?group_id=41019&release_id=1770 38 md5sums: 49b87547f2a09178d2b50bfd4bc72283 pwsafe-1.9.2c-bin.zip 7f00423b03db942422a933039d73fb21 pwsafe-1.9.2c-ppc-bin.zip bb25d7ab1f0d9bcaf4133b7c311e24c8 pwsafe-1.9.2c-src.zip Enjoy, Rony mailto:ro...@us... |
|
From: DK <dk...@ds...> - 2003-08-08 16:43:30
|
Brook,
Although I am the "DK" who modified 1.92 for this function (which I have =
used), another member of this list suggested using the "standard" =
version and adding multiple entries. For example, using your names...
"user1" "pswd1" - default "login function"
"user1 - access" "pswd2"
"user1 - modify" "pswd3"
etc.
In this manner, a) the standard form is used and b) the passwords you =
want are in order in the PasswordSafe display ("user1", "user1 - =
access", "user1 - modify"....) and close to the base entry.
There was always a problem with my version in that "Is 3 passwords =
enough?" What if you needed 5 or 6 or 10?
I still think that the internal use of lists is useful but, if not many =
people want this function and the "standard" version could provide a =
similar function, than I suppose (reluctantly), the modification is not =
worth the maintenance overhead.
Regards,
David
----- Original Message -----=20
From: "Brook Harty" <ha...@ir...>
To: <pas...@li...>
Sent: Friday, August 08, 2003 5:19 PM
Subject: [Passwordsafe-devel] 1.92-DK
> Wanted to say, how the 1.92-DK version has been nice to track multiple =
> passwords on systems. Working in the telco enviroment, we have =
multiple=20
> layers of passwords, one to login, one for access, one for =
modification,=20
> etc..
> Also used it for password aging, Could use the comments, but its nice =
to=20
> have it encrypted on standard view incase I have someone watching over =
> my shoulder.
>=20
> Thinking of upgrading our users from 1.7 to 192-dk, used it for a =
couple=20
> months, no problems.
>=20
> Any thoughts?
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> =
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/=
01
> _______________________________________________
> Passwordsafe-devel mailing list
> Pas...@li...
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel |
|
From: Brook H. <ha...@ir...> - 2003-08-08 16:19:28
|
Wanted to say, how the 1.92-DK version has been nice to track multiple passwords on systems. Working in the telco enviroment, we have multiple layers of passwords, one to login, one for access, one for modification, etc.. Also used it for password aging, Could use the comments, but its nice to have it encrypted on standard view incase I have someone watching over my shoulder. Thinking of upgrading our users from 1.7 to 192-dk, used it for a couple months, no problems. Any thoughts? |
|
From: Rony S. <ro...@gm...> - 2003-08-01 04:19:58
|
Hi, I haven't downloaded the expat parser yet, but here's what I'd like to do: The first record on disk will be a pre-2.0 record, with the warning "!!! format 2.x database - please upgrade !!!" as the title. As we've dscussed, this is to provide a reasonable failure mode for 1.x applications. Following that will be the actual records, as follows: First a block (*) with the length of the record, as currently done. Following that, blocks with the actual XML formatted record encrypted. Using Graham's schema, here's the actual string that will be encrypted: <Item> <Title>first record</Title> <Username>david</Username> <Password>ad;sflja</Password> <Extra/> <Notes>first note</Notes> </Item> My idea is to tweak the parser stream, adding the preamble/postamble (<PWSafe> <PWList> ... </PWList> </PWSafe>) and even possible <Item> and </Item> programatically, but this isn't strictly necessary. Does this seem reasonable, or at least sane? Question: How is the XML data written? Does expat support this, or do we have to write the XML format manually? If the latter, how is encoding of Unicode and dates handled? Rony (*) encryption is done in blocks of 8 bytes. > From: pas...@li... > [mailto:pas...@li...]On Behalf Of Graham > Ullrich > Sent: Thu, 31 Jul 2003 18:30 > To: PasswordSafe Developers > Subject: RE: [Passwordsafe-devel] why binary format for v2? > > > Maurice, > > > Regarding #4, the main issue is to only have a single password in clear > > text at a time, right? Because as far as the other data is concerned > > (title, username, notes), we need all of that in the clear to present > > the main list view anyway, no? > > I'm not sure the issue is as simple as that. In an earlier post I believe > Rony objected to revealing the record structure because that might make > cracking the encryption easier. I'll let Rony address that issue - > encryption security is not my area of expertise. > > > About the database size growth, you're talking about the on-disk size? > > Could we compress it prior to encryption? > > Sure, although we should remember that some PWSafe options mandate saving > the database to disk after any change or addition. > > > With the slow-down in the searches, how bad was it? Was it actually a > > noticeable delay? How many records did you have? What is the max. size > > database we want to target, BTW? A few hundred records? > > I'm going to backpedal a bit here. My database contained around > 250 records, > which might be fairly typical of the maximum. Yes, in my code there was a > noticeable delay - a second or two to show the password after clicking on > the list. However, the delay may have been the result of some > other part of > my code. I didn't spend time verifying the slowdown came from the > XML but it > did occur immediately after adding that functionality. In other words, I'm > pretty sure it was the XML but not 100% sure. I used a different > XML parser > in any case... we should run tests with whatever parser we want to use. > > Graham > > > |
|
From: Rony S. <ro...@gm...> - 2003-08-01 04:07:56
|
Hi, DK is absolutely correct. PasswordSafe reads the encrpted database from the disk exactly once, and after that all the data resides in memory, in a linked list of CItemData. The datum, that is, the data members of the CItemData objects, are kept encrypted in memory as a security measure. (*) Remember that Windows uses a swap file, hence all memory may be written to the disk. It is unacceptable to have all the entries, including the passwords, on disk in cleartext (unencrypted). Also, if/when PasswordSafe will be ported to a Unix variant (Linus, *BSD, etc.), a malicous user with root priveleges can scan the physical memory as well. Currently, ony the titles and names are kept in cleartext for display (there's an option to display the password in the list as well, which I really dislike). The master password is currently in memory, yes. This is a nasty weakness in the system, that will be addressed in 2.0. (not a perfect solution, but still an improvement, I think - a random "session password" will be generated upon startup, and used to encrypt (a) the memory-resident data, and (b) the master password, which need be decrypted only to write the database to disk.) To summarize, The encryption of the database and the encryption in memory are unrelated. XML is only relevant for the persistent database. Rony (*) Currently, this is what's slowing up the search function, as all the fields of every record need to be decrypted. Perhaps some speedup can be gained by reading the title/name directly from the displayed list. > -----Original Message----- > From: pas...@li... > [mailto:pas...@li...]On Behalf > Of Maurice Aubrey > Sent: Friday, August 01, 2003 12:27 AM > To: DK > Cc: PasswordSafe Developers > Subject: Re: [Passwordsafe-devel] why binary format for v2? > > > DK wrote: > > Maybe I missing something but..... > > > > surely the database only has to be in XML format on disk! > > > > That is: processed by the XML parser on open and on save. > Meanwhile for use > > and searches etc. - why can't it be fully and safely encrypted > in memory? > > > > As to unencrypted data, this can be performed on the in memory copy and > > steps taken to limit the amount of unencrypted data present at any time. > > > > Given the size of hard disks these days, what does it matter if > the database > > is over large on disk - it gets used from memory. > > Yes, I was thinking along similar lines -- that if the search is too > slow, etc., we could transform the XML into an in-memory format that's > more suitable. > > But I'm not clear on why it needs to be kept encrypted in memory. > The passwords I understand, but the main list view shows all the > titles, usernames, and notes. So that data must be available to the > widget, which means there's a clear text copy of it somewhere, right > (or else it's being decrypted for every redraw)? > > And keeping the passwords encrypted is just an attempt to make hacking > it a little more difficult, correct? I mean, the master password is in > memory, so if you can find that, then the game is lost anyway. > > I thought the on-disk size might matter for very small devices, but > looking at the record sizes, I doubt that will be a concern. > > Maurice > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072 303_01/01 _______________________________________________ Passwordsafe-devel mailing list Pas...@li... https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel |