Re: [ITA] rubygems 3.4.12
I had saved the ssh key because I had already used it to update other packages. Perhaps it was because the connection environment was different than usual. Thanks for the advice. On Tue, Apr 18, 2023 at 1:23 AM Brian Inglis via Cygwin-apps wrote: > > On 2023-04-17 05:29, Daisuke Fujimura via Cygwin-apps wrote: > > I tried again and succeeded. > > It seems it was a temporary problem. > > Thanks for the advice. > > > On Mon, Apr 17, 2023 at 7:40 PM Jon Turney > > wrote: > >> On 17/04/2023 11:28, Daisuke Fujimura via Cygwin-apps wrote: > I changed maintainer-ship to you > > >>> I can't push on git, is there anything else I should do? > >>> I confirmed that my name is mentioned in the rubygems section of > >>> cygwin-pkg-maint. > >>> > >>> ``` > >>> $ git remote -v > >>> origin > >>> ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git > >>> (fetch) > >>> origin > >>> ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git > >>> (push) > >>> $ git push origin master > >>> kex_exchange_identification: Connection closed by remote host > >>> Connection closed by 8.43.85.97 port 22 > > >> This just looks like problem establishing the ssh connection. > >> If it's not a transient problem, you can try 'ssh cyg...@cygwin.com > >> alive', and then maybe adding '-vvv' may give some hints as to what's > >> going wrong... > > >>> fatal: Could not read from remote repository. > >>> Please make sure you have the correct access rights > >>> and the repository exists. > >>> ``` > > Don't you have to make one ssh connection to save your host key, any time your > host or ssh key changes, before other operations will work? > > -- > Take care. Thanks, Brian Inglis Calgary, Alberta, Canada > > La perfection est atteinte Perfection is achieved > non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add > mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut > -- Antoine de Saint-Exupéry
Re: Build machines
Achim Gratz via Cygwin-apps writes: > The original plan was to make this my new Linux desktop and replace the > 9 year old Haswell I'm using right now and wait until the 16-core > Phoenix processors are finally available, but I'll probably have to > re-think that. I misremembered the code names. The direct successor to the 7735HS (Rembrandt Refresh) are the 7840HS / 7940HS (Phoenix-H at 8 cores and upgraded to 4nm Zen4/RDNA3 and about 15% better performance per Watt); the upcoming 16 core is the 7945HX (Dragon Range, 5nm Zen4/RDNA2). Anyway, I just ordered another of one these to become my new Linux desktop, the first one will stay with Win11 Pro and Cygwin and become my new build box in the coming weeks. I added a 4TB SSD for archival storage last weekend, for now I'll keep the 500GB NVMe it came with for OS and builds as it seems to not limit anything in any meaningful way for now. If it turns out later that it does I'll just switch to a speedy 2TB NVMe later on (I already had one, but that will go into #2 as system / home drive as per the original plan). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
[PATCH v2] peflags: add support for IMAGE_DLLCHARACTERISTICS_GUARD_CF
This allows for setting, clearing, and displaying the value of the
"control flow guard" dll characteristics flag.
The flag for MSVC is called "/guard:cf" and the macro ends with "GUARD_CF".
To keep things consistent, it would make sense to name the option "guard-cf".
However, there's already "-c"/"control-flow-guard" in genpeimg for this flag,
and genpeimg shares all other options with peflags so far.
So, follow genpeimg and go with "-c" and "--control-flow-guard".
This is motivated by mingw-w64 and llvm v16 gaining support for
CFG (Control Flow Guard).
---
Renamed the option from -g/--guard-cf to -c/--control-flow-guard
peflags.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/peflags.c b/peflags.c
index b1cd7a8..93eaa0b 100644
--- a/peflags.c
+++ b/peflags.c
@@ -121,7 +121,7 @@ static const symbolic_flags_t pe_symbolic_flags[] = {
CF(0x0800, no-bind),
/*CF(0x1000, reserved_0x1000),*/
CF(0x2000, wdmdriver),
-/*CF(0x4000, reserved_0x4000),*/
+ CF(0x4000, control-flow-guard),
CF(0x8000, tsaware),
{0, 0, 0}
};
@@ -182,6 +182,7 @@ sizeof_values_t sizeof_vals[5] = {
static struct option long_options[] = {
{"dynamicbase", optional_argument, NULL, 'd'},
{"high-entropy-va", optional_argument, NULL, 'e'},
+ {"control-flow-guard", optional_argument, NULL, 'c'},
{"forceinteg", optional_argument, NULL, 'f'},
{"nxcompat", optional_argument, NULL, 'n'},
{"no-isolation", optional_argument, NULL, 'i'},
@@ -204,7 +205,7 @@ static struct option long_options[] = {
{NULL, no_argument, NULL, 0}
};
static const char *short_options
- = "d::e::f::n::i::s::b::W::t::w::l::S::x::X::y::Y::z::T:vhV";
+ = "d::e::c::f::n::i::s::b::W::t::w::l::S::x::X::y::Y::z::T:vhV";
static void short_usage (FILE *f);
static void help (FILE *f);
@@ -706,6 +707,11 @@ parse_args (int argc, char *argv[])
optarg,
IMAGE_DLLCHARACTERISTICS_HIGH_ENTROPY_VA);
break;
+ case 'c':
+ handle_pe_flag_option (long_options[option_index].name,
+optarg,
+IMAGE_DLLCHARACTERISTICS_GUARD_CF);
+ break;
case 'n':
handle_pe_flag_option (long_options[option_index].name,
optarg,
@@ -1079,6 +1085,8 @@ help (FILE *f)
" -e,\n"
" --high-entropy-va [BOOL] Image is compatible with 64-bit address space\n"
" layout randomization (ASLR).\n"
+" -c,\n"
+" --control-flow-guard [BOOL] Image supports Control Flow Guard.\n"
" -f, --forceinteg [BOOL] Code integrity checks are enforced.\n"
" -n, --nxcompat [BOOL] Image is compatible with data execution\n"
" prevention (DEP).\n"
--
2.40.0
Re: [ITA] rubygems 3.4.12
On 2023-04-17 05:29, Daisuke Fujimura via Cygwin-apps wrote: I tried again and succeeded. It seems it was a temporary problem. Thanks for the advice. On Mon, Apr 17, 2023 at 7:40 PM Jon Turney wrote: On 17/04/2023 11:28, Daisuke Fujimura via Cygwin-apps wrote: I changed maintainer-ship to you I can't push on git, is there anything else I should do? I confirmed that my name is mentioned in the rubygems section of cygwin-pkg-maint. ``` $ git remote -v origin ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git (fetch) origin ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git (push) $ git push origin master kex_exchange_identification: Connection closed by remote host Connection closed by 8.43.85.97 port 22 This just looks like problem establishing the ssh connection. If it's not a transient problem, you can try 'ssh cyg...@cygwin.com alive', and then maybe adding '-vvv' may give some hints as to what's going wrong... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` Don't you have to make one ssh connection to save your host key, any time your host or ssh key changes, before other operations will work? -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
Re: [ITA] rubygems 3.4.12
I tried again and succeeded. It seems it was a temporary problem. Thanks for the advice. On Mon, Apr 17, 2023 at 7:40 PM Jon Turney wrote: > > On 17/04/2023 11:28, Daisuke Fujimura via Cygwin-apps wrote: > >> I changed maintainer-ship to you > > > > I can't push on git, is there anything else I should do? > > > > I confirmed that my name is mentioned in the rubygems section of > > cygwin-pkg-maint. > > > > ``` > > $ git remote -v > > origin > > ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git > > (fetch) > > origin > > ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git > > (push) > > > > $ git push origin master > > kex_exchange_identification: Connection closed by remote host > > Connection closed by 8.43.85.97 port 22 > > This just looks like problem establishing the ssh connection. > > If it's not a transient problem, you can try 'ssh cyg...@cygwin.com > alive', and then maybe adding '-vvv' may give some hints as to what's > going wrong... > > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > ``` >
Re: [ITA] rubygems 3.4.12
On 17/04/2023 11:28, Daisuke Fujimura via Cygwin-apps wrote: I changed maintainer-ship to you I can't push on git, is there anything else I should do? I confirmed that my name is mentioned in the rubygems section of cygwin-pkg-maint. ``` $ git remote -v origin ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git (fetch) origin ssh://cygwin-rdbxbdvo6bxqt0dzr+a...@public.gmane.org/git/cygwin-packages/rubygems.git (push) $ git push origin master kex_exchange_identification: Connection closed by remote host Connection closed by 8.43.85.97 port 22 This just looks like problem establishing the ssh connection. If it's not a transient problem, you can try 'ssh cyg...@cygwin.com alive', and then maybe adding '-vvv' may give some hints as to what's going wrong... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ```
Re: [ITA] rubygems 3.4.12
> I changed maintainer-ship to you
I can't push on git, is there anything else I should do?
I confirmed that my name is mentioned in the rubygems section of
cygwin-pkg-maint.
```
$ git remote -v
origin ssh://cyg...@cygwin.com/git/cygwin-packages/rubygems.git (fetch)
origin ssh://cyg...@cygwin.com/git/cygwin-packages/rubygems.git (push)
$ git push origin master
kex_exchange_identification: Connection closed by remote host
Connection closed by 8.43.85.97 port 22
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
```
On Sun, Apr 16, 2023 at 10:30 AM Daisuke Fujimura
wrote:
>
> Thank you for your review.
>
> As you indicated, we have decided that it is preferable to download
> the file from the official site.
>
> I confirmed that there are no differences in the packages.
>
> On Sun, Apr 16, 2023 at 3:20 AM Jon Turney
> wrote:
> >
> > On 14/04/2023 13:55, Daisuke Fujimura via Cygwin-apps wrote:
> > > Hello,
> > >
> > >
> > >
> > > Cygportfile:
> > > -
> > > https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=tree;h=refs/heads/rubygems;hb=refs/heads/rubygems
> >
> > Would it make more sense to use:
> >
> > SRC_URI="https://rubygems.org/rubygems/rubygems-${VERSION}.tgz;
> >
> > ?
> >
> >
Re: [PATCH] peflags: add support for IMAGE_DLLCHARACTERISTICS_GUARD_CF
Hi Christoph, your patch looks good and I'm happy to merge it into peflags, but... On Apr 17 09:48, Christoph Reiter via Cygwin-apps wrote: > Jeremy noted that an option already exists in genpeimage [0] but with > a different name, which I wasn't aware of: -c/control-flow-guard, > instead of -g/guard-cf which I used here. I'm open to making them > match. yeah, given that peflags and genpeimg use the same single char flags, it might be a good idea to follow suit. Thanks, Corinna
Re: [PATCH] peflags: add support for IMAGE_DLLCHARACTERISTICS_GUARD_CF
Jeremy noted that an option already exists in genpeimage [0] but with a different name, which I wasn't aware of: -c/control-flow-guard, instead of -g/guard-cf which I used here. I'm open to making them match. [0] https://github.com/mingw-w64/mingw-w64/blob/70ec1e0de44f3cbed2064c08e1620ff0a7916cd1/mingw-w64-tools/genpeimg/src/genpeimg.c#L84
