You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(9) |
Mar
(4) |
Apr
(5) |
May
(27) |
Jun
(3) |
Jul
(5) |
Aug
(3) |
Sep
(25) |
Oct
(21) |
Nov
(2) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(3) |
Feb
|
Mar
(3) |
Apr
(9) |
May
(2) |
Jun
(20) |
Jul
(9) |
Aug
(2) |
Sep
(5) |
Oct
|
Nov
(8) |
Dec
(3) |
| 2002 |
Jan
(3) |
Feb
(6) |
Mar
(13) |
Apr
(20) |
May
(10) |
Jun
(6) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
(10) |
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(12) |
Nov
(1) |
Dec
(5) |
| 2004 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
(6) |
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2005 |
Jan
(9) |
Feb
(8) |
Mar
(12) |
Apr
(8) |
May
|
Jun
(6) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2006 |
Jan
(3) |
Feb
(3) |
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(1) |
Nov
(2) |
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(9) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Jochen H. <Hoe...@In...> - 2003-10-27 19:31:52
|
On Friday 24 October 2003 03:46, Martin Pool wrote: > On 23 Oct 2003, Florin Andrei <fl...@sg...> wrote: > > (*) - Much more important seems to be the master password on the Keyring > > application. If that's too weak, the database is easily crackable. >=20 > I think this is the limiting factor. I think most people would not > have the patience to write a passphrase of more than about 5-8 > characters. >=20 > Since an astute attacker can try to decode it on a PC, they can cycle > through combinations much faster than somebody could write them. Yes, this is the biggest problem. I have added a figure at http://gnukeyring.sf.net/crypto.html to demonstrate the importance of a good password. > Of course there might also be bugs. This was the first real crypto > program I wrote (quite a few years ago now), though other people and > especially Jochen have checked it later. There was a bug in 1.0 (cached encryption key was never removed), so anyone who is still using that version should upgrade immediately. There was even an exploit for this bug. I don't know of any other serious bugs in the crypto algorithms, but a few weaknesses are described on the page mentioned above, e.g. one can see from the encrypted database which records have the same password or account. Also the database is not tamper-proof, but that isn't really important as an attacker with write access to the palm would most likely tamper the keyring binary not the database. Jochen =2D-=20 Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany Email: hoe...@in... Tel: +49 441 798 3124 |
|
From: anders t. <li...@th...> - 2003-10-26 13:08:30
|
> There will also be a minor bug fix release 1.2.3 (dirty flag isn't set on > changed records), but that has no new features. I've noticed a small display bug. One can enter accounts and passwords that are longer then the lines, but things that drop out of the screen is never displayed. What are the differences between Keyring and 995Safe? -- anders thoresson |
|
From: Martin P. <mb...@sa...> - 2003-10-25 20:28:51
|
On 23 Oct 2003, Florin Andrei <fl...@sg...> wrote: > On Thu, 2003-10-23 at 10:58, Jochen Hoenicke wrote: > > > No, the development hasn't stopped. I'm preparing a new version with > > a new crypto algorithms and it takes some time, especially as I can only > > work on weekends. I hope to have a test release, soon. > > Awesome! > > Jochen, can i ask a few "hard" questions? > What's the actual strength of the encryption algorithms on a device > running PalmOS? Applications running on Unix clones make use of various > network- and system-events to feed some pseudo-random numbers > generators. Is there anything like that on PalmOS? Yes, Jochen added a randomness pool based on the Linux /dev/random. Graffiti input is a good (low baud) source of input that is hard for an attacker to precisely predict. > I guess what i'm asking is, are there any inherent weaknesses in an > application that runs on PalmOS and uses strong encryption, just because > it runs on PalmOS? > > I'm quite aware that the encryption algo might not be the weakest link > in the chain, so perhaps there's no point in worrying too much about > that (*) but i thought i should ask anyway. > > (*) - Much more important seems to be the master password on the Keyring > application. If that's too weak, the database is easily crackable. I think this is the limiting factor. I think most people would not have the patience to write a passphrase of more than about 5-8 characters. Since an astute attacker can try to decode it on a PC, they can cycle through combinations much faster than somebody could write them. Of course there might also be bugs. This was the first real crypto program I wrote (quite a few years ago now), though other people and especially Jochen have checked it later. > Also, a resourceful group might read micro-scratches on the Grafitti > area and deduce often-used string patterns. Probably only a problem if a large fraction of your writing is the passphrase. This might happen if Keyring is the only app you use and you rarely add new information. But I would expect most people would write in other information at least sometimes. What I would really like to see is all of the data across all applications strongly encrypted. (Like mounting an encrypted volume on unix.) Doing so would probably require hairy PalmOS hacking, and is certainly out of the scope of Keyring. > Finally, if the application "leaks" information into the palmtop's > memory, that could be used as well to do some guessing. > > In any case, a palmtop is never to be considered totally secure, but i > feel that, if the encryption stuff doesn't have any inherent flaws, the > security of the hardware should be better than that of the PCs (it's a > lot harder to install "keystroke loggers", it's a lot harder to snoop on > the RF fields generated by the display and by the input device, > etc.). Yes, I think so. In particular it's pretty hard for somebody to remotely compromise a palmtop, but probably more than 1% of Windows or Linux machines in the world are compromised at any time. -- Martin |
|
From: Jochen H. <Hoe...@In...> - 2003-10-25 09:12:19
|
Hello Florin On Thursday 23 October 2003 20:47, Florin Andrei wrote: > Jochen, can i ask a few "hard" questions? > What's the actual strength of the encryption algorithms on a device > running PalmOS? Applications running on Unix clones make use of various > network- and system-events to feed some pseudo-random numbers > generators. Is there anything like that on PalmOS? Keyring has it's own strong random pool that is fed as long as keyring is running by all events including pen stroke events. The algorithm used for the pool is the same as for the linux /dev/urandom device. This involves a SHA-1 hash (md5 for keyring-1.2) so even if no randomness is added it is intractable (as long as you don't get direct access to the pool). > I guess what i'm asking is, are there any inherent weaknesses in an > application that runs on PalmOS and uses strong encryption, just because > it runs on PalmOS? I don't think so, except for computing intensive algorithms. For example f= or key generation from the master password I had to use a smaller number of iterations of SHA-1 sums than recommended by the standard. These=20 iterations make brute-force attacks more difficult if the master password=20 is too simple. [This applies to the not yet finished version, all previous versions including 1.2.3 use a single MD5 sum] > In any case, a palmtop is never to be considered totally secure, but i > feel that, if the encryption stuff doesn't have any inherent flaws, the > security of the hardware should be better than that of the PCs (it's a > lot harder to install "keystroke loggers", it's a lot harder to snoop on > the RF fields generated by the display and by the input device, etc.). It's probably as easy to build a keystroke logger for a Palm as is for a PC. There is no memory protection on the Palm and a program can=20 patch the OS kernel. On the other hand you don't install new programs from unknown sources as often on your Handheld as you do on your PC=20 and the PC is often used by more than one person. Also the PCs are more often on the internet than Palms are and as they are more complicated they have more security holes. > > There will also be a minor bug fix release 1.2.3 (dirty flag isn't set = on > > changed records), but that has no new features. >=20 > An upgrade from 1.1 should be straightforward, right? Yes, there should be no problems. Jochen =2D-=20 Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany Email: hoe...@in... Tel: +49 441 798 3124 |
|
From: Martin P. <mb...@sa...> - 2003-10-24 18:21:14
|
Ironically enough, my Palm was stolen the other day. :-( Good thing the most important stuff was encrypted. -- Martin |
|
From: Florin A. <fl...@sg...> - 2003-10-24 01:29:17
|
On Thu, 2003-10-23 at 10:58, Jochen Hoenicke wrote: > No, the development hasn't stopped. I'm preparing a new version with > a new crypto algorithms and it takes some time, especially as I can only > work on weekends. I hope to have a test release, soon. Awesome! Jochen, can i ask a few "hard" questions? What's the actual strength of the encryption algorithms on a device running PalmOS? Applications running on Unix clones make use of various network- and system-events to feed some pseudo-random numbers generators. Is there anything like that on PalmOS? I guess what i'm asking is, are there any inherent weaknesses in an application that runs on PalmOS and uses strong encryption, just because it runs on PalmOS? I'm quite aware that the encryption algo might not be the weakest link in the chain, so perhaps there's no point in worrying too much about that (*) but i thought i should ask anyway. (*) - Much more important seems to be the master password on the Keyring application. If that's too weak, the database is easily crackable. Also, a resourceful group might read micro-scratches on the Grafitti area and deduce often-used string patterns. Finally, if the application "leaks" information into the palmtop's memory, that could be used as well to do some guessing. In any case, a palmtop is never to be considered totally secure, but i feel that, if the encryption stuff doesn't have any inherent flaws, the security of the hardware should be better than that of the PCs (it's a lot harder to install "keystroke loggers", it's a lot harder to snoop on the RF fields generated by the display and by the input device, etc.). > There will also be a minor bug fix release 1.2.3 (dirty flag isn't set on > changed records), but that has no new features. An upgrade from 1.1 should be straightforward, right? -- Florin Andrei http://florin.myip.org/ |
|
From: Jochen H. <Hoe...@In...> - 2003-10-23 18:21:13
|
On Tuesday 21 October 2003 22:03, anders thoresson wrote: > Hi, >=20 > I've just had my first looks at Keyring. And I like it. Just curious: H= as=20 > development stopped? This list isn't that crowed with messages. :) No, the development hasn't stopped. I'm preparing a new version with a new crypto algorithms and it takes some time, especially as I can only work on weekends. I hope to have a test release, soon. There will also be a minor bug fix release 1.2.3 (dirty flag isn't set on changed records), but that has no new features. Jochen =2D-=20 Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany Email: hoe...@in... Tel: +49 441 798 3124 |
|
From: Martin P. <mb...@sa...> - 2003-10-22 07:19:41
|
On 21 Oct 2003, anders thoresson <li...@th...> wrote: > Hi, > > I've just had my first looks at Keyring. And I like it. Just curious: Has > development stopped? This list isn't that crowed with messages. :) I have stopped working on it. Jochen Hoenicke may still be interested but I have not seen any changes recently. If you would like to add further features please feel free. -- Martin |
|
From: anders t. <li...@th...> - 2003-10-22 06:42:04
|
Hi, I've just had my first looks at Keyring. And I like it. Just curious: Has development stopped? This list isn't that crowed with messages. :) -- anders thoresson |
|
From: Retracile <ret...@ea...> - 2003-08-06 03:07:26
|
All, I need to transfer my data from gnukeyring for palmos to keyring on open=20 zaurus. Is there a way to do that without exporting each of my passwords= =20 individually? I'm willing to do the conversion on a Linux PC if there is= =20 software that will do it. Barring that, if there is a concise descriptio= n of=20 the data format that maybe I could parse...?? Any ideas/pointers/etc. would be greatly appreciated. Eli |
|
From: <sp...@ea...> - 2003-07-11 22:34:25
|
<!-- This plain text message area is for recipients who have email programs that do not support html emails (almost every modern email client software program can accept html emails). If you want to add an alternate plain text message for those who cannot receive html emails, enter it here. //--> <HTML><HEAD><META NAME="GENERATOR" Content="Microsoft DHTML Editing Control"><TITLE></TITLE><BASE href='file://C:\Program Files\ProspectMailer\'></HEAD><BODY link=#0000ff bgColor=#000080 aLink=#0000ff><P align=center><A href="http://www.tscrefundrecoveryservices.com"><FONT style="BACKGROUND-COLOR: #ffff00"><FONT color=#0000ff size =6 ><STRONG>WE WILL GET YOUR REFUND</STRONG></FONT> </FONT> </A><STRONG><FONT style="BACKGROUND-COLOR: #ffff00" size=6>!</FONT></STRONG></P><P align=center><FONT size=5><FONT face="Times New Roman"><FONT color=#000000><IMG style="WIDTH: 180px; HEIGHT: 210px" height =137 alt="" hspace=0 src="cid:LogoCrisp-2.jpg" width=116 align=baseline border=0 ></FONT></FONT></FONT></P><P align=center><STRONG><FONT style="BACKGROUND-COLOR: #ffff00">Click below for more info</FONT></STRONG></P><P align=center><A href="http://www.tscrefundrecoveryservices.com"><FONT style="BACKGROUND-COLOR: #ffff00">http://www.tscrefundrecoveryservices.com</FONT></A></P></BODY></HTML> |
|
From: Artur P. <art...@no...> - 2003-07-07 17:53:51
|
looks great, good work. Artur Alexandre Roberto Zia wrote: > Hello > > I've made a client for windows to open my keyRing database. > It can be downloaded here. > http://www.zia.com.br/keyringwin.html > It is a new code, and only tested in my computer. If anyone face > problems with it, please email-me. > Thanks, > > |
|
From: Alexandre R. Z. <ale...@zi...> - 2003-07-07 14:51:21
|
Hello
I've made a client for windows to open my keyRing database.
It can be downloaded here.
http://www.zia.com.br/keyringwin.html
It is a new code, and only tested in my computer. If anyone face problems with it, please email-me.
Thanks,
|
|
From: Martin P. <mb...@sa...> - 2003-06-13 01:21:02
|
On 30 May 2003, Benjamin Esham <bd...@in...> wrote: > On Friday, May 30, 2003, at 01:04 PM, Forrest Aldrich wrote: > > >It would be useful to have a Unix/BSD port of this. Curses based > >would work, or web-based. > > Web-based sounds good. Why not write it in PHP -- then it can be used > on *nix, Mac OS X, and Windows? Both the API and user interface would be so different that I doubt it could be a "port" in any meaningful sense. It's probably better to write a new application, based on the ideas you like in Keyring. Perhaps if it was written in some kind of database scripting language then you could just move it across, but it's not so that's by the by. Personally I would feel less confident in storing confidential information on a web server. One of the nice things about keeping it on a Palm is that there are fairly few ways for people to attack it. -- Martin |
|
From: Benjamin E. <bd...@in...> - 2003-05-30 19:54:48
|
On Friday, May 30, 2003, at 01:04 PM, Forrest Aldrich wrote:
> It would be useful to have a Unix/BSD port of this. Curses based
> would work, or web-based.
Web-based sounds good. Why not write it in PHP -- then it can be used
on *nix, Mac OS X, and Windows?
--
Benjamin D. Esham { http://bdesham.net
bd...@in... } AIM: bdesham 1 2 8
|
|
From: Forrest A. <fo...@fo...> - 2003-05-30 17:05:10
|
It would be useful to have a Unix/BSD port of this. Curses based would work, or web-based. |
|
From: Douglas C. R. <itt...@ya...> - 2003-03-29 18:46:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I am using the "conduit" for the first time. BTW, a very nice add-on. I like to keep a paper copy of my passwords, just in case! I noticed that when I launch the program there are a couple of duplicate entries on the screen. Only one show's an entry when I click on it. Just an oddity I may have caused when I deleted the first entry I had made in the KeyRing program. Would I need to edit the registry to remove these? If so, which entry(s)? Very cool program though! I use daily. Doug R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) - GPGshell v2.70 iD8DBQE+hemL22A9KYmE/ZcRAtLrAJ4i4f5WgAo95fLZvOz+j1pWfofFcwCfSNKU AUTsYvk0JJFzpOEUNd+bDXI= =Dd+K -----END PGP SIGNATURE----- __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com |
|
From: Jochen H. <Hoe...@In...> - 2003-03-18 15:35:45
|
A new bug fix release for Keyring 1.2 is out: Keyring for PalmOS 1.2.2 Copyright 1999-2003 The GNU Keyring Sourceforge Team http://gnukeyring.sourceforge.net/download.html Changes from 1.2.1: * Fixed selecting an entry from the search form under Palm OS 5.0. Changes from 1.2: * Fixed the "freeze on installation" bug. MD5 checksums (binary mode): 910c53d827536157f5126c0069e7d681 keyring-1.2.2-en.prc b3561ffa8485f84518ff7a51e3c444b8 keyring-1.2.2-da.prc a85b8f3f62bbd5f21210f5f11ab36235 keyring-1.2.2-de.prc dae0436238296ef8ebd2a41026e82918 keyring-1.2.2-es.prc 0d33369b1b7a3d75e36ee1bab8291072 keyring-1.2.2-fr.prc 13b3fcb0a5274939a80a56e7f2ab584b keyring-1.2.2-it.prc 088d4d52ab44e9d6d75e2414f3dd6b49 keyring-1.2.2-ja.prc 52493bb317bc6bb479ffc3c6f077e6d5 keyring-1.2.2-nl.prc 690d3b4790d948fb751c725910ebde64 keyring-1.2.2-nb.prc 56c40c5345856044b00ff6dc08297c9c keyring-1.2.2-nn.prc b20b5b72996d46d9385cb96cfa75e5ef keyring-1.2.2-pt.prc 727e140ecb896111e2da1d887b9af406 keyring-1.2.2-sv.prc 93a5ec88e28befb47d203f11d9f30f84 keyring-1.2.2.tar.gz 055d04553778d21e9626b84291005a64 pilotSSLeay/shlib/DESLib.prc 49a1b026bdc6da3699b91b6ca3473814 pilotSSLeay/shlib/MDLib.prc |
|
From: Martin P. <mb...@sa...> - 2003-01-30 06:59:15
|
On 29 Jan 2003, Vinc Duran <vi...@fr...> wrote: > Hello, > Is the right place to put enhancement requests Yes. It's an even better place to send patches :-) -- Martin |
|
From: Vinc D. <vi...@fr...> - 2003-01-30 06:08:18
|
Hello, Is the right place to put enhancement requests http://sourceforge.net/projects/gnukeyring/ and then "Feature Requests"? I added one about WEP keys and haven't seen any comments. I'm mostly wondering if you guys see the request (and if you think it can be done). Thanks, Vinc Duran |
|
From: Douglas P. M. <dba...@ha...> - 2003-01-23 21:32:11
|
Aloha, I just wanted to say thanks to Jochen for your hard work on Keyring. I use a Visor Deluxe, OS v. 3.1H3 and have not had any trouble. Nice work. I glad I found this. Mahalo- Douglas |
|
From: Jochen H. <Hoe...@In...> - 2003-01-23 14:21:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new bug fix release for Keyring 1.2 is out: Keyring for PalmOS 1.2.1 Copyright 1999-2003 The GNU Keyring Sourceforge Team http://gnukeyring.sourceforge.net/download.html Changes from 1.2: * Fixed the "freeze on installation" bug. MD5 checksums (binary mode): 13e39d2d9edce16cd2471a3312cd5b08 keyring-1.2.1-en.prc b1298a376c7e0096012e385320925d11 keyring-1.2.1-da.prc 7f52134a392eda5671411aa25c48a15b keyring-1.2.1-de.prc 661688ebb27c3f1391e1778c6a4e67cd keyring-1.2.1-es.prc 606a149bbe1ec88ec5ff6e8dd8afa5bf keyring-1.2.1-fr.prc 16e2eea2c201a5730594220b6c01209d keyring-1.2.1-it.prc c10717c9c6322ab4870753be9935c23d keyring-1.2.1-ja.prc 53536e2325ca396a57b6750bac199ab4 keyring-1.2.1-nl.prc 1fc36e0c652a7de8a879eeb9d3568884 keyring-1.2.1-nb.prc bc98f52b0e2d3f35dce1ff27eda9c288 keyring-1.2.1-nn.prc 9ff559ca621bf604592146a579b7f4f5 keyring-1.2.1-pt.prc f4c3cd784cc3b6b9d9e0c5e273fa5329 keyring-1.2.1-sv.prc 48d1704449b96ed7042efd50ec13026e keyring-1.2.1.tar.gz 055d04553778d21e9626b84291005a64 pilotSSLeay/shlib/DESLib.prc 49a1b026bdc6da3699b91b6ca3473814 pilotSSLeay/shlib/MDLib.prc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+L/pOsTEv/cIwu2QRArjGAJ0fI/g/w706KiMjUCoJVb9CjaqpxgCfYFLQ SsRIsYDNbE2LOvJbtnjxxwg= =N9nt -----END PGP SIGNATURE----- |
|
From: Jochen H. <Hoe...@In...> - 2003-01-22 12:35:07
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, This is from the gnukeyring bugs forum. On Tuesday 21 January 2003 16:57, Michael Braginsky wrote: > > Initial Comment: > If only keyring.prc is being installed, the system displays a > message that DESLib is needed and freezes. Soft reset > doesn't help, only the hard reset clears the problem. This > is ridiculous. > > >Comment By: Jochen Hoenicke (hoenicke) > > Date: 2003-01-21 10:27 > > > > I can't reproduce this. I tried several different ROM versions > > under pose > > and it never freezed. It just quits keyring as expected. > > > > I probably was not quite clear about the problem. It happens during the > installation, not on an attempt to use keyring. I am surprised that it > checks for DESLib.prc during the installation or right after it at all. > > I have PalmVx, OS 3.5.3 > During HotSync the program surprisingly produced a message that DESLib.prc > was not present and froze on this message window. After a soft reset, the > system gets to the same message or crashes (I tried several soft resets > before going to a hard reset). > I tried this twice. Happened both times. I am not really willing to > experiment with this more since the condition is cured only by a > HardReset. Yes, this makes sense now. This also explains why I couldn't reproduce it with pose; I don't install it via HotSync there. I agree this is a serious bug. I have put a warning on the download page and hided the release on the sourceforge file page. I will fix this and release 1.2.1 soon. Jochen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Lo/tsTEv/cIwu2QRAgtPAJ9oCY6u95Big9ULZ9EFEGmV8K8aKwCfTpRT /lS1awltVvoO61B3Z55Fc6M= =aMck -----END PGP SIGNATURE----- |
|
From: Florin A. <fl...@sg...> - 2003-01-21 18:41:26
|
On Mon, 2003-01-20 at 04:25, Jochen Hoenicke wrote: > > A new stable version of Keyring is out: > Keyring for PalmOS 1.2 Excellent! > * Use pilotSSLeay for encryption, which is a bit faster than > the PalmOS builtin encryption. The binaries from > pilotSSLeay are included. Is this library also used by the PalmOS ssh client (top gun ssh)? If true, that means i don't have to install the SSLeay lib if i already installed a recent version of tgssh? I think i've heard some discussions before about enhancing the entropy generator in gnukeyring. Was that change included in 1.2? -- Florin Andrei "I'm only arguing against stupid people who think they need a revolution to improve - most real improvements are evolutionary." - Linus Torvalds |
|
From: Jochen H. <Hoe...@In...> - 2003-01-20 12:25:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new stable version of Keyring is out: Keyring for PalmOS 1.2 Copyright 1999-2002 The GNU Keyring Sourceforge Team http://gnukeyring.sourceforge.net/download.html Changes from 1.1: * Support PalmOS global Find. * Support pronounceable passwords conforming to the FIPS 181 Automated Password Generator Standard * Support interactive search for a key name on list form. * Keyedit form is left on auto off if the timeout has also expired. Code works for all supported PalmOS versions. * Use pilotSSLeay for encryption, which is a bit faster than the PalmOS builtin encryption. The binaries from pilotSSLeay are included. * The last-modified-date is back again. * Support larger notes, up to 32000 characters. Files may be downloaded from: https://sourceforge.net/project/showfiles.php?group_id=306 MD5 checksums (binary mode): ed13d7dcc5f8dea5efbd23ac85fa346b keyring-1.2-en.prc (english) 465355fd93051c82688bae2f33a3f59b keyring-1.2-da.prc (danish) 0171e16732931a7e0da992f261067213 keyring-1.2-de.prc (german) fee7cb6a88a58ed4cdb58f3afeabdefb keyring-1.2-es.prc (spanish) 475a76ce16ff7c6d37a9dcb24574f9d2 keyring-1.2-fr.prc (french) 2ca57a08ef821973b1d2c381f28c6d51 keyring-1.2-it.prc (italian) f57e2d6585799ef66d6352a3f65933d5 keyring-1.2-ja.prc (japanese) 99df78d2223f8870a16812823641b2eb keyring-1.2-nl.prc (dutch) 32969e3b77d209a472382011137a3a1c keyring-1.2-nb.prc (norwegian bokmål) 6b78ce3277bbaa5ef706e361a841f3c2 keyring-1.2-nn.prc (nynorsk) aab130f3773982115e84f89fcffce1e2 keyring-1.2-pt.prc (portuguese) ca630e129b68acbc3427cff97c13a2f5 keyring-1.2-sv.prc (swedish) b82d2313401717d12aa81c0b4d9060b0 keyring-1.2.tar.gz 055d04553778d21e9626b84291005a64 pilotSSLeay/shlib/DESLib.prc 49a1b026bdc6da3699b91b6ca3473814 pilotSSLeay/shlib/MDLib.prc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+K+rFsTEv/cIwu2QRAoiYAJ9kZOVIucw6GBrpYFAcYPzmpMiL1ACffion mcf5nngrRiWRcxpFJgM28g8= =zAa6 -----END PGP SIGNATURE----- |