On Wed, Dec 23, 2009 at 12:15:21PM -0800, Collin Monahan wrote:
>I tried to upgrade to the 1.7.1-1 version on Windows 7 Home 64bit. Toward the
>end of the process I had to click through several modal dialogs which say:
>
>The procedure entry point stpcpy could not be located in the dynamic link
>
On 10/27/2009 06:18 PM, Jason Schamp wrote:
If I launch from the command line WITHOUT the -q switch, it requires me
to hit enter a few times, but doesn't go into this infinite loop. Any
ideas?
I was going to recommend trying a different mirror before you mentioned
about the '-q' switch. Maybe
Dave Korn wrote:
Here's my key.
[...] but you'll find it's been used to sign that signing key,
i.e., after creating an .asc file from it and imported (gpg --import <
asc_file), is it possible to verify pubring.asc? If Yes, How?
(pubring.asc hasn't a .sig file!)
...the forthcoming gcc-4
Lee wrote on 08 August 2008 13:50:
>
> umm. right! The key was included in the announcement msg. dunno
> how I missed it,
Prolly because it was an insanely long post!
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/m
On 8/8/08, Dave Korn <[EMAIL PROTECTED]> wrote:
> Lee wrote on 08 August 2008 05:51:
>
>> It's late, so I'm not going to try to figure out how to import the
>> public key they give the link to. It seems a bit pointless
>> anyway.. if someone is able to change the setup.exe offered for
>> down
Angelo Graziosi wrote on 08 August 2008 13:08:
> gpg: Signature made Tue Aug [...]
> gpg: Good signature from "Cygwin "
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the
> owner.
Here's my key. You have
Corinna Vinschen wrote:
You didn't read`Dave's mail:
The key was in the announcement; run "gpg --import" at the command-line
and cut'n'paste it into stdin (or redirect it from a file).
^^
Dave Korn wrote:
With the pubring.asc, yo
Angelo Graziosi wrote on 08 August 2008 11:31:
> Dave Korn wrote:
>
>> Press Ctrl-D. It's the same as cat or anything else that reads stdin.
>
> $ gpg --import
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
>
> Ctrl-D
>
> gpg: no va
On Aug 8 12:30, Angelo Graziosi wrote:
> Dave Korn wrote:
>
>> Press Ctrl-D. It's the same as cat or anything else that reads stdin.
>
> $ gpg --import
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnupg.org/faq.html for more information
>
> Ctrl-D
>
> gpg: no valid OpenPGP
Dave Korn wrote:
Press Ctrl-D. It's the same as cat or anything else that reads stdin.
$ gpg --import
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
Ctrl-D
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
With the 'p
Angelo Graziosi wrote on 08 August 2008 10:58:
> Dave Korn wrote:
>
>> The key was in the announcement; run "gpg --import" at the command-line
>> and cut'n'paste it into stdin (or redirect it from a file).
>
> $ gpg --import
> gpg: WARNING: using insecure memory!
> gpg: please see http://www.gnu
Dave Korn wrote:
The key was in the announcement; run "gpg --import" at the command-line
and cut'n'paste it into stdin (or redirect it from a file).
$ gpg --import
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
I have waited several mi
Lee wrote on 08 August 2008 05:51:
> It's late, so I'm not going to try to figure out how to import the
> public key they give the link to. It seems a bit pointless
> anyway.. if someone is able to change the setup.exe offered for
> downloading I don't see why they couldn't also change the p
Angelo Graziosi wrote on 08 August 2008 01:44:
> gpg: Can't check signature: public key not found
The key was in the announcement; run "gpg --import" at the command-line
and cut'n'paste it into stdin (or redirect it from a file).
cheers,
DaveK
--
Can't think of a witty .sigline tod
On 8/7/08, Angelo Graziosi <[EMAIL PROTECTED]> wrote:
> Dave Korn wrote:
>
>> Also, we're going to add a link to the setup.exe gpg .sig file on the main
>> page; then the simple rule will be "If it has a gpg signature, it's the
>> new
>> version".
>
> The main page now says:
>
> "The signature for
Dave Korn wrote:
Also, we're going to add a link to the setup.exe gpg .sig file on the main
page; then the simple rule will be "If it has a gpg signature, it's the new
version".
The main page now says:
"The signature for setup.exe can be used to verify the validity of this
binary using this
Eric Blake wrote on 05 August 2008 02:29:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Mike Cappella on 8/4/2008 2:33 PM:
>> With the recent CVE security announcement regarding setup.exe:
>>
>>http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-3323
>>
>> I'm wondering if per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Cappella on 8/4/2008 2:33 PM:
| With the recent CVE security announcement regarding setup.exe:
|
|http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-3323
|
| I'm wondering if perhaps it make sense to include the version number of
| set
On Tue, Mar 19, 2002 at 03:46:28PM +0100, Rene wrote:
>the setup-version line is missing from the setup.ini file (on
>mirrors.rcn.net) so the old setup.exe does not indicate that there is a
>new setup.exe.
Should be fixed now.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simp
19 matches
Mail list logo
