public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: redhat does not answer ...
Date: Wed, 20 Dec 2006 17:36:00 -0000	[thread overview]
Message-ID: <20061220173417.GB8345@calimero.vinschen.de> (raw)
In-Reply-To: <45896F58.5010908@capdata.fr>

Hi Emmanuel,

On Dec 20 18:14, Emmanuel Torre wrote:
> Thanks you for your attention.
> 
> we have no usual contact at RedHat company.
> As we are in France, we mailed a few days ago to germany@redhat.com & 
> europe@redhat.com, as mentioned on the RH site.

I'm sorry to hear that.  Thanks for the information.

> Precedently, some years ago, we used to deliver bash scripts to our 
> clients so no compilation at all.
> Now we use an utility (SHC) that generates a C program (one per bash 
> script) that contains the encrypted bash script. The C program decrypts 
> the bash and execute it on the fly.
> 
> These C programs are compiled with gcc in a Cygwin environment and needs 
> the cygwin1.dll to be able to execute (else you get the cygwin1.dll not 
> found when double-clicking on the .exe) : so we can say it is linked 
> against the cygwin1.dll.
> 
> Can you give me the price of such a license ?

Sorry, but I'm not the right person to talk about our pricing.

I'll forward all information I got from you to my manager and somebody
will contact you about this very soon.


Thanks again,
Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

      reply	other threads:[~2006-12-20 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 15:57 Emmanuel Torre
2006-12-20 16:43 ` Corinna Vinschen
2006-12-20 17:22   ` Emmanuel Torre
2006-12-20 17:36     ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061220173417.GB8345@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-licensing@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).