[Translators-l] Re: Ready for translation: Tech News #04 (2024)

[Nick Wilson (Quiddity)]

On Thu, Jan 18, 2024 at 5:41 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2024/04
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F04=page
>

The text of the newsletter is now final.

Nothing has changed since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: Help optimize D solution to phone encoding problem: extremely slow performace.

[Jordan Wilson via Digitalmars-d-learn]

On Friday, 19 January 2024 at 08:57:40 UTC, Renato wrote:
Do you know why the whole thread seems to have disappeared?? 
There's a lot of good stuff in the thread, it would be a huge 
shame to lose all that!


I agree! Thanks for posting your benchmarks, I thought your whole 
benching setup was pretty good, and learnt alot from your code 
and the resulting contributions in the thread and others.


Jordan

Re: Impressed again

[mike wilson]

I had the luck to be loaned one for about 9 months by Denis Klimovich.  Made 
some of my (technically) best pictures with it.  Considering the use it got 
(-25degreesC, covered in snow then condensation, lugged around various crowded 
venues, etc) it's pretty robust as well.

> On 19/01/2024 01:38 GMT Mark Roberts  wrote:
> 
>  
> During our recent trip to Amsterdam and Bruges (got home on Monday) I
> used just one lens the whole time: The old FA*28-70 f/2.8 (on the
> K-1). And having looked through most of the images I'm stunned once
> again at how good a lens that is.
>
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Ready for translation: Tech News #04 (2024)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2024/04

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F04=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: CCADB Self-Assessment - Version 1.3 Released

[Ben Wilson]

Hello Antti,
That was a typo.  Thank you for spotting that for us. It has been corrected
to 1.7.
Thanks again,
Ben

On Wed, Jan 17, 2024 at 10:26 PM 'Antti Backman' via CCADB Public <
public@ccadb.org> wrote:

> Where can we obtain the NCSSR v1.8 which is referenced by the new
> Self-Assessment v 1.3? Could not find it from cabforum.org?
>
> BR, Antti
>
> keskiviikko 17. tammikuuta 2024 klo 20.39.38 UTC+2 Ben Wilson kirjoitti:
>
>> Greetings all,
>>
>>
>> The CCADB Steering Committee has updated the CCADB Self-Assessment to Version
>> 1.3
>> <https://docs.google.com/spreadsheets/d/1Kx9bwMdEnFG5INBpJJLjP2RAsFYyx055zCRfL6ClkcI>.
>> Additionally, CCADB.org has been updated
>> <https://www.ccadb.org/cas/self-assessment> to include version history
>> for the CCADB Self-Assessment.
>>
>>
>> This version of the Self Assessment includes updates for:
>>
>>
>>-
>>
>>Instructions for Cover Sheet (pointing to CCADB's "CA Hierarchy"
>>report that can be used to enumerate CAs covered by this Self-Assessment.)
>>-
>>
>>Mozilla Compliance Self-Assessment (now reflects MRSP Version 2.9
>>requirements)
>>-
>>
>>Chrome Root Program Policy v. 1.5 Self-Assessment (from Version 1.4)
>>-
>>
>>CCADB policy v 1.3 Self-Assessment (from Version 1.2.1)
>>-
>>
>>TLS BRs v 2.0.2 (from Version 2.0.0)
>>
>>
>> Thank you,
>>
>> Ben Wilson, on behalf of the CCADB Steering Committee
>>
> --
> You received this message because you are subscribed to the Google Groups
> "CCADB Public" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to public+unsubscr...@ccadb.org.
> To view this discussion on the web visit
> https://groups.google.com/a/ccadb.org/d/msgid/public/4875c15d-6ac9-4fb4-8251-d07cfbef5fe3n%40ccadb.org
> <https://groups.google.com/a/ccadb.org/d/msgid/public/4875c15d-6ac9-4fb4-8251-d07cfbef5fe3n%40ccadb.org?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtabPuDOSBf2E95acRVvgJcJoxep%3D_GMy-Y6Gm23xHyHrUA%40mail.gmail.com.

[llvm] [clang-tools-extra] [clang] [X86] Use RORX over SHR imm (PR #77964)

[Bryce Wilson via cfe-commits]

https://github.com/Bryce-MW updated 
https://github.com/llvm/llvm-project/pull/77964

>From d4c312b9dbf447d0a53dda0e6cdc482bd908430b Mon Sep 17 00:00:00 2001
From: Bryce Wilson 
Date: Fri, 12 Jan 2024 16:01:32 -0600
Subject: [PATCH 1/8] [X86] Use RORX over SHR imm

---
 llvm/lib/Target/X86/X86InstrShiftRotate.td |  78 ++
 llvm/test/CodeGen/X86/atomic-unordered.ll  |   3 +-
 llvm/test/CodeGen/X86/bmi2.ll  |   6 +-
 llvm/test/CodeGen/X86/cmp-shiftX-maskX.ll  |   3 +-
 llvm/test/CodeGen/X86/pr35636.ll   |   4 +-
 llvm/test/CodeGen/X86/vector-trunc-ssat.ll | 116 ++---
 6 files changed, 143 insertions(+), 67 deletions(-)

diff --git a/llvm/lib/Target/X86/X86InstrShiftRotate.td 
b/llvm/lib/Target/X86/X86InstrShiftRotate.td
index f951894db1890c..238e8e9b6e97f3 100644
--- a/llvm/lib/Target/X86/X86InstrShiftRotate.td
+++ b/llvm/lib/Target/X86/X86InstrShiftRotate.td
@@ -879,6 +879,26 @@ let Predicates = [HasBMI2, HasEGPR, In64BitMode] in {
   defm SHLX64 : bmi_shift<"shlx{q}", GR64, i64mem, "_EVEX">, T8, PD, REX_W, 
EVEX;
 }
 
+
+def immle16_8 : ImmLeaf;
+def immle32_8 : ImmLeaf;
+def immle64_8 : ImmLeaf;
+def immle32_16 : ImmLeaf;
+def immle64_16 : ImmLeaf;
+def immle64_32 : ImmLeaf;
+
 let Predicates = [HasBMI2] in {
   // Prefer RORX which is non-destructive and doesn't update EFLAGS.
   let AddedComplexity = 10 in {
@@ -891,6 +911,64 @@ let Predicates = [HasBMI2] in {
   (RORX32ri GR32:$src, (ROT32L2R_imm8 imm:$shamt))>;
 def : Pat<(rotl GR64:$src, (i8 imm:$shamt)),
   (RORX64ri GR64:$src, (ROT64L2R_imm8 imm:$shamt))>;
+
+// A right shift by less than a smaller register size that is then
+// truncated to that register size can be replaced by RORX to
+// preserve flags with the same execution cost
+
+def : Pat<(i8 (trunc (srl GR16:$src, (i8 immle16_8:$shamt,
+  (EXTRACT_SUBREG (RORX32ri (INSERT_SUBREG (i32 (IMPLICIT_DEF)), 
GR16:$src, sub_16bit), imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (sra GR16:$src, (i8 immle16_8:$shamt,
+  (EXTRACT_SUBREG (RORX32ri (INSERT_SUBREG (i32 (IMPLICIT_DEF)), 
GR16:$src, sub_16bit), imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (srl GR32:$src, (i8 immle32_8:$shamt,
+  (EXTRACT_SUBREG (RORX32ri GR32:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (sra GR32:$src, (i8 immle32_8:$shamt,
+  (EXTRACT_SUBREG (RORX32ri GR32:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (srl GR64:$src, (i8 immle64_8:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (sra GR64:$src, (i8 immle64_8:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_8bit)>;
+
+
+def : Pat<(i16 (trunc (srl GR32:$src, (i8 immle32_16:$shamt,
+  (EXTRACT_SUBREG (RORX32ri GR32:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (sra GR32:$src, (i8 immle32_16:$shamt,
+  (EXTRACT_SUBREG (RORX32ri GR32:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (srl GR64:$src, (i8 immle64_16:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (sra GR64:$src, (i8 immle64_16:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_16bit)>;
+
+def : Pat<(i32 (trunc (srl GR64:$src, (i8 immle64_32:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_32bit)>;
+def : Pat<(i32 (trunc (sra GR64:$src, (i8 immle64_32:$shamt,
+  (EXTRACT_SUBREG (RORX64ri GR64:$src, imm:$shamt), sub_32bit)>;
+
+
+// Can't expand the load
+def : Pat<(i8 (trunc (srl (loadi32 addr:$src), (i8 immle32_8:$shamt,
+  (EXTRACT_SUBREG (RORX32mi addr:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (sra (loadi32 addr:$src), (i8 immle32_8:$shamt,
+  (EXTRACT_SUBREG (RORX32mi addr:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (srl (loadi64 addr:$src), (i8 immle64_8:$shamt,
+  (EXTRACT_SUBREG (RORX64mi addr:$src, imm:$shamt), sub_8bit)>;
+def : Pat<(i8 (trunc (sra (loadi64 addr:$src), (i8 immle64_8:$shamt,
+  (EXTRACT_SUBREG (RORX64mi addr:$src, imm:$shamt), sub_8bit)>;
+
+
+def : Pat<(i16 (trunc (srl (loadi32 addr:$src), (i8 immle32_16:$shamt,
+  (EXTRACT_SUBREG (RORX32mi addr:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (sra (loadi32 addr:$src), (i8 immle32_16:$shamt,
+  (EXTRACT_SUBREG (RORX32mi addr:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (srl (loadi64 addr:$src), (i8 immle64_16:$shamt,
+  (EXTRACT_SUBREG (RORX64mi addr:$src, imm:$shamt), sub_16bit)>;
+def : Pat<(i16 (trunc (sra (loa

CCADB Self-Assessment - Version 1.3 Released

[Ben Wilson]

Greetings all,


The CCADB Steering Committee has updated the CCADB Self-Assessment to Version
1.3
<https://docs.google.com/spreadsheets/d/1Kx9bwMdEnFG5INBpJJLjP2RAsFYyx055zCRfL6ClkcI>.
Additionally, CCADB.org has been updated
<https://www.ccadb.org/cas/self-assessment> to include version history for
the CCADB Self-Assessment.


This version of the Self Assessment includes updates for:


   -

   Instructions for Cover Sheet (pointing to CCADB's "CA Hierarchy" report
   that can be used to enumerate CAs covered by this Self-Assessment.)
   -

   Mozilla Compliance Self-Assessment (now reflects MRSP Version 2.9
   requirements)
   -

   Chrome Root Program Policy v. 1.5 Self-Assessment (from Version 1.4)
   -

   CCADB policy v 1.3 Self-Assessment (from Version 1.2.1)
   -

   TLS BRs v 2.0.2 (from Version 2.0.0)


Thank you,

Ben Wilson, on behalf of the CCADB Steering Committee

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaZ%3Dop7Tx1iKrDKidyrGcNP2M-JXZPGXO9XmkQJTjmA2%2Bg%40mail.gmail.com.

Re: [Smcwg-public] Voting period begins for SMC-05: Adoption of CAA for S/MIME

[Ben Wilson via Smcwg-public]

Mozilla votes "yes" on Ballot SMC-005.

On Wed, Jan 10, 2024 at 4:32 PM Corey Bonnell via Smcwg-public <
smcwg-public@cabforum.org> wrote:

> *Ballot SMC05: Adoption of CAA for S/MIME*
>
>
>
> *Purpose of Ballot:*
>
>
>
> The ballot proposes changes to the S/MIME Baseline Requirements to
> introduce the use of Certification Authority Authorization (CAA) Processing
> for Email Addresses as defined in RFC 9495. It also includes minor
> typographic corrections.
>
>
>
> The following motion has been proposed by Corey Bonnell of DigiCert and
> endorsed by Dimitris Zacharopoulos of HARICA and Ben Wilson of Mozilla.
>
>
>
> *— MOTION BEGINS —*
>
>
>
> This ballot modifies Version 1.0.2 of the “Baseline Requirements for the
> Issuance and Management of Publicly-Trusted S/MIME Certificates” (“S/MIME
> Baseline Requirements”) resulting in Version 1.0.3.
>
>
>
> The proposed modifications to the S/MIME Baseline Requirements may be
> found at
> https://github.com/cabforum/smime/compare/5fb2a7ee94d1c5684d5f32af11572e8c10cd2f8c...1fbbdc8f908e6eba779b4ea0de1cbfd20e156c3a
> <https://url.avanan.click/v2/___https:/github.com/cabforum/smime/compare/5fb2a7ee94d1c5684d5f32af11572e8c10cd2f8c...1fbbdc8f908e6eba779b4ea0de1cbfd20e156c3a___.YXAzOmRpZ2ljZXJ0OmE6bzowYjJjZTA4YzA2Mjg2MTNmZDY2ZDc0ZjE4YjZlMzY5NDo2OmE4NGY6MDAyNmY1Nzc0ZWY2MjBjNzhmYjM4MDc2MGE3MjE5ZDEzMGRkODY5Y2U1NTEzYmY5MTc3NDc5OTRlZjdjZTNjOTpoOkY>
>
>
>
> The SMCWG Chair or Vice-Chair is permitted to update the Relevant Dates
> and Version Number of the S/MIME Baseline Requirements to reflect final
> dates.
>
>
>
> *— MOTION ENDS —*
>
>
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
>
>
>
> Discussion (7 days)
>
> Start Time: Wednesday January 3, 2024 18:00 UTC
>
> End Time: Wednesday January 10, 2024 23:30 UTC
>
>
>
> Vote for approval (7 days)
>
> Start Time: January 10, 2024 23:30 UTC
>
> End Time: January 17, 2024 23:30 UTC
>
>
>
> IPR Review (30 days)
>
>
> ___
> Smcwg-public mailing list
> Smcwg-public@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/smcwg-public
>
___
Smcwg-public mailing list
Smcwg-public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/smcwg-public

Re: [Smcwg-public] Voting period begins for SMC-05: Adoption of CAA for S/MIME

[Clint Wilson via Smcwg-public]

Apple votes YES on Ballot SMC-05.

> On Jan 10, 2024, at 3:32 PM, Corey Bonnell via Smcwg-public 
>  wrote:
> 
> Ballot SMC05: Adoption of CAA for S/MIME
>  
> Purpose of Ballot:
>  
> The ballot proposes changes to the S/MIME Baseline Requirements to introduce 
> the use of Certification Authority Authorization (CAA) Processing for Email 
> Addresses as defined in RFC 9495. It also includes minor typographic 
> corrections.
>  
> The following motion has been proposed by Corey Bonnell of DigiCert and 
> endorsed by Dimitris Zacharopoulos of HARICA and Ben Wilson of Mozilla.
>  
> — MOTION BEGINS —
>  
> This ballot modifies Version 1.0.2 of the “Baseline Requirements for the 
> Issuance and Management of Publicly-Trusted S/MIME Certificates” (“S/MIME 
> Baseline Requirements”) resulting in Version 1.0.3.
>  
> The proposed modifications to the S/MIME Baseline Requirements may be found 
> at 
> https://github.com/cabforum/smime/compare/5fb2a7ee94d1c5684d5f32af11572e8c10cd2f8c...1fbbdc8f908e6eba779b4ea0de1cbfd20e156c3a
>  
> <https://url.avanan.click/v2/___https:/github.com/cabforum/smime/compare/5fb2a7ee94d1c5684d5f32af11572e8c10cd2f8c...1fbbdc8f908e6eba779b4ea0de1cbfd20e156c3a___.YXAzOmRpZ2ljZXJ0OmE6bzowYjJjZTA4YzA2Mjg2MTNmZDY2ZDc0ZjE4YjZlMzY5NDo2OmE4NGY6MDAyNmY1Nzc0ZWY2MjBjNzhmYjM4MDc2MGE3MjE5ZDEzMGRkODY5Y2U1NTEzYmY5MTc3NDc5OTRlZjdjZTNjOTpoOkY>
>  
> The SMCWG Chair or Vice-Chair is permitted to update the Relevant Dates and 
> Version Number of the S/MIME Baseline Requirements to reflect final dates.
>  
> — MOTION ENDS —
>  
> This ballot proposes a Final Maintenance Guideline. The procedure for 
> approval of this ballot is as follows:
>  
> Discussion (7 days)
> Start Time: Wednesday January 3, 2024 18:00 UTC
> End Time: Wednesday January 10, 2024 23:30 UTC
>  
> Vote for approval (7 days)
> Start Time: January 10, 2024 23:30 UTC
> End Time: January 17, 2024 23:30 UTC
>  
> IPR Review (30 days)
> 
>  
> ___
> Smcwg-public mailing list
> Smcwg-public@cabforum.org <mailto:Smcwg-public@cabforum.org>
> https://lists.cabforum.org/mailman/listinfo/smcwg-public



smime.p7s
Description: S/MIME cryptographic signature
___
Smcwg-public mailing list
Smcwg-public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/smcwg-public

Re: [Smcwg-public] Certificate Template Information extension and SBR allowance

[Clint Wilson via Smcwg-public]

While I think I agree with the intent of Tim’s statement (especially in the 
context of this discussion and its applicability thereto), taken literally I 
believe it is stating something with broader impact than intended. 
What I mean is that it’s important to carry the complete context of an OID 
over, including the requirements and/or prerequisites outlined for the use of 
an OID (to the extent specified or stipulated by the governing SDO). The 
“right” exists, but so to do obligations coinciding with the use of many (all?) 
OIDs. I believe everyone here’s suitably aware of this, but just wanted to 
state it explicitly so that too much nuance isn’t lost with any potential 
changes made to the text.

Cheers,
-Clint

> On Jan 16, 2024, at 11:27 AM, Martijn Katerbarg via Smcwg-public 
>  wrote:
> 
> > Absolutely. Any OID that comes from a Standards Development Organization is 
> > intended for use by other organizations, and everyone has the “right” to 
> > use them.
> 
>  
> 
> I’d like to be able to read it this way, but I am concerned that the current 
> language is too limiting in this regard.
> 
> Tim, since you also mentioned not liking the language, I’ll see if I can come 
> up with an alternative to make this clear, and also make the implied 
> allowance a stated fact.
> 
>  
> 
> Regards,
> 
> Martijn
> 
> 
> From: Tim Hollebeek 
> Sent: Wednesday, January 10, 2024 10:58:58 pm
> To: Dimitris Zacharopoulos ; SMIME Certificate Working 
> Group 
> Cc: Martijn Katerbarg 
> Subject: RE: [Smcwg-public] Certificate Template Information extension and 
> SBR allowance
> 
> Absolutely.  Any OID that comes from a Standards Development Organization is 
> intended for use by other organizations, and everyone has the “right” to use 
> them.
>  
> -Tim
>  
> From: Dimitris Zacharopoulos  
> Sent: Wednesday, January 10, 2024 12:48 PM
> To: Tim Hollebeek ; SMIME Certificate Working 
> Group 
> Cc: Martijn Katerbarg 
> Subject: Re: [Smcwg-public] Certificate Template Information extension and 
> SBR allowance
>  
> I also believe that any publicly supported and documented X.509 extension 
> (e.g. defined by IETF or ITU-T) are allowed for use by CAs, as long as they 
> are documented in the CA's CPS. 
> 
> Is there anything that prevents it in the current CA/B Forum documents? 
> 
> 
> Thanks,
> DZ.
> 
> Jan 10, 2024 20:38:19 Tim Hollebeek via Smcwg-public 
> mailto:smcwg-public@cabforum.org>>:
> 
> You don’t need a contract to have a right to use someone else’s extension.
> I would say that if Microsoft has public documentation that says or implies 
> that the extension can and should be used by other organizations, then other 
> organizations “have the right” to use that extension.
> That said, I have never liked this language, which comes from the TLS BRs.  I 
> would support making it more clear as to what is and isn’t allowed, and even 
> maybe clarifying what problem is being solved with these requirements.
> -Tim
> From: Smcwg-public  > On Behalf Of Martijn Katerbarg 
> via Smcwg-public
> Sent: Wednesday, January 10, 2024 5:54 AM
> To: SMIME Certificate Working Group  >
> Subject: [Smcwg-public] Certificate Template Information extension and SBR 
> allowance
> Hi all,
> There’s been a request within the S/MIME working group to bring forward 
> issues that have arisen since the adoption of the SBRs. While we’ve not seen 
> a whole lot of issues, we believe we may have discovered one now.
> We offer support for Windows’s own auto-enrollment features. In the past we 
> used to include the “Certificate Template Information” extension (OID 
> 1.3.6.1.4.1.311.21.7) for this purpose. Since we started issuing SBR 
> compliant certificates prior to September 1st, we removed support for this 
> extension on publicly trusted S/MIME certificates.
> As we now have noticed, this has led to a partial breakdown of the 
> auto-enrollment system. From what we understand, the auto-enrollment 
> mechanism is specifically looking for this extension in certificates, if a 
> certificate for a particular required Certificate Template (as specified 
> through AD) is not found, auto-enrollment will “do its job”, and request a 
> new certificate. This can lead to multiple new certificates being installed 
> in a single day, all because the extension is missing.
> We’ve investigated bringing back support for the extension, and are led to 
> the conclusion that no, this extension would not be allowed per the current 
> language. A breakdown:
> Section 7.1.2.4 
> (https://github.com/cabforum/smime/blob/main/SBR.md#7124-all-certificates 
> 
>  ) states:
> “All fields and extensions SHALL be 

Re: Audit Reminder Email Summary - Intermediate Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of January 2024 Outdated Audit Statements for Intermediate 
Certs
Date: Tue, 16 Jan 2024 13:00:09 + (GMT)

CA Owner: Government of The Netherlands, PKIoverheid (Logius)
   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Services 
CA - 2023
SHA-256 Fingerprint: 
6E25C0044C7EBB30D01A4CC3D5733D734D06CD296A6823E63527F4182D528351
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Burger CA - 2023
SHA-256 Fingerprint: 
66388EE649CBE920FD949FA9B77E2AA45B5DEC4120B8FFAB371B0C9C5E38C1C1
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Persoon CA 
- 2023
SHA-256 Fingerprint: 
C8C77ECF368D73214D50D88384464339E6F8E59F34B47E39E7965F4E5787CF1D
Standard Audit Period End Date (mm/dd/): 05/31/2022

Mozilla Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1843265




-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/f2f25f3a-d69c-4062-b845-94288d87ed5an%40mozilla.org.

Re: Audit Reminder Email Summary - Root Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of January 2024 Audit Reminder Emails
Date: Tue, 16 Jan 2024 13:00:28 + (GMT)

Mozilla: Audit Reminder
CA Owner: Buypass
Root Certificates:
   Buypass Class 3 Root CA
   Buypass Class 2 Root CA
Standard Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
Standard Audit Period End Date: 2022-10-31
Standard Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_018.pdf
Standard Audit Period End Date: 2022-10-31
BR Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
BR Audit Period End Date: 2022-10-31
BR Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_018.pdf
BR Audit Period End Date: 2022-10-31
EV Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
EV Audit Period End Date: 2022-10-31
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Government of Hong Kong (SAR), Hongkong Post, Certizen
Root Certificates:
   Hongkong Post Root CA 3
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=9d4d307f-6c97-42aa-8ba2-58555d3d8da0
Standard Audit Period End Date: 2022-12-31
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=c029a511-1e8a-4161-8ebb-2cce40e9fbc0
BR Audit Period End Date: 2022-12-31
EV Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=a2ec0cb5-788f-42d2-9635-ce74b510fbef
EV Audit Period End Date: 2022-11-30
CA Comments: null




-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/5362f2f7-1ca1-4250-bf64-99cf09ee8b72n%40mozilla.org.

[Wikitech-ambassadors] Tech News 2024, week 03

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2024/03. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Ghanaian
Pidgin , Tiếng Việt
, Tyap
, español
, français
, italiano
, norsk bokmål
, polski
, português
, português do Brasil
, suomi
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, বাংলা
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - Pages that use the JSON contentmodel
   
   will now use tabs instead of spaces for auto-indentation. This will
   significantly reduce the page size. [1]
   
   - Gadgets
   
   and personal user scripts may now use JavaScript syntax introduced in ES6
   (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source
   code to protect other site functionality from syntax errors, and to ensure
   scripts are valid in all supported browsers
   .
   Previously, Gadgets could use the requiresES6 option. This option is no
   longer needed and will be removed in the future. [2]
   
   - Bot passwords
   
   and owner-only OAuth consumers
   

   can now be restricted to allow editing only specific pages. [3]
   
   - You can now thank
   
   edits made by bots. [4] 
   - An update on the status of the Community Wishlist Survey for 2024 has
   been published
   
.
   Please read and give your feedback.

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 16 January. It
   will be on non-Wikipedia wikis and some Wikipedias from 17 January. It will
   be on all wikis from 18 January (calendar
   ). [5]
   [6]
   
   - Starting on January 17, it will not be possible to login to Wikimedia
   wikis from some specific old versions of the Chrome browser (versions
   51–66, released between 2016 and 2018). Additionally, users of iOS 12, or
   Safari on Mac OS 10.14, may need to login to each wiki separately. [7]
   
   - The jquery.cookie module was deprecated and replaced with the
   mediawiki.cookie module last year. A script has now been run to replace
   any remaining 

[Translators-l] Re: Ready for translation: Tech News #03 (2024)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 22 languages) to 1,109 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: Help optimize D solution to phone encoding problem: extremely slow performace.

[Jordan Wilson via Digitalmars-d-learn]

On Saturday, 13 January 2024 at 11:03:42 UTC, Renato wrote:
I like to use a phone encoding problem to determine the 
strenghtness and weaknesses of programming languages because 
this problem is easy enough I can write solutions in any 
language in a few hours, but complex enough to exercise lots of 
interesting parts of the language.


[...]


Hello Renato,

This seems to be quite a lot of calls:
```
 Timer frequency unknown, Times are in Megaticks 

  Num  TreeFuncPer
  CallsTimeTimeCall

1920496437613756   0 pure nothrow ref 
@trusted immutable(char)[][] 
core.internal.array.appending._d_arrayappendcTX!(immutable(char)[][], immutable(char)[])._d_arrayappendcTX(scope return ref immutable(char)[][], ulong)


1920492489573474   0 @safe void 
dencoder.printTranslations(immutable(char)[][][dencoder.Key], 
dencoder.ISolutionHandler, immutable(char)[], immutable(char)[], 
immutable(char)[][])

```

This is when using the `words-quarter.txt` input (the 
`dictionary.txt` input seems to finish much faster, although 
still slower than `java`/`rust`).


I also used only 100 phone numbers as input.

My final observation is that `words-quarter.txt` contains some 
1-letter inputs, (for example, `i` or `m`)...this may result in a 
large number of encoding permutations, which may explain the high 
number of recursion calls?


Jordan

Re: [tor-dev] Timers in Arti?

[Holmes Wilson]

Michael, what kind of reduction in battery impact would you expect if you were 
able to make these changes?

Also, is anyone aware of any work that has been done within this community or 
in academia to consider from first principles what Tor would look like if built 
for mobile first? (e.g. built to only run when an app is in the foreground, or 
when a notification wakes up the app.) This seems like a discussion worth 
having once Arti settles and it's easier to build new things again!

On Wed Jan 10, 2024, 11:26 AM GMT, Michael Rogers 
 wrote:
> On 10/01/2024 01:46, Nick Mathewson wrote:
>> On Tue, Jan 9, 2024 at 12:58 PM Micah Elizabeth Scott
>>  wrote:
>>>
>>> Ah. If you want to run an onion service you'll need to keep at least a
>>> couple circuits open continuously for the introduction points. I'm not
>>> sure where you would meaningfully find time to deep sleep in that
>>> scenario. There will be ongoing obligations from the wifi/wan and tcp
>>> stacks. You need a continuous TCP connection to the guard, and multiple
>>> circuits that are not discarded as idle. Incoming traffic on those
>>> circuits need to be addressed quickly or clients won't be able to connect.
>>>
>>> If we were really optimizing for a low power mobile onion service
>>> platform we'd have a different way to facilitate introductions without a
>>> continuously open set of circuits, but that would also be much more
>>> abuse-prone.
>>>
>>> -beth
>>
>> Hm. Do you know, is it possible to make network-driven wakeup events
>> relatively prompt? (Like, within a second or so if a TCP stream we're
>> waiting on wakes up). If so, then onion services have a decent chance
>> of being made to work.
>
> Fantastic! Yes, the response to network events should be reasonably
> prompt. I'll try to get some measurements.
>> As for the original question about timers, it would be good to know if
>> the variance between scheduled wakeup and actual wakeup can be
>> bounded, or if there's any way to mark a timer as high-priority vs
>> low-priority or something.
>
> This is unfortunately one of those things that's constantly changing on
> Android and varies between manufacturers. In theory we should be able to
> set a periodic alarm that fires within fifteen minutes of the last
> firing, although not all manufacturers honour this.
>
> When the alarm fires the device will come out of suspension and the app
> will be able to grab a temporary wake lock, which we can hold for some
> amount of time (say a minute, for the sake of argument) to let Tor do
> whatever it needs to do.
>
> As far as I know these alarms can only be scheduled via a Java API, so
> Tor would either need to signal to the controller that an alarm was
> needed, or the controller could just assume this whenever hidden
> services were published, and wake the device every fifteen minutes
> without explicitly communicating with Tor about alarms.
>
> Cheers,
> Michael
>> ___
>> tor-dev mailing list
>> tor-dev@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> ___
> tor-dev mailing list
> tor-dev@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

[Translators-l] Re: Ready for translation: Tech News #03 (2024)

[Nick Wilson (Quiddity)]

On Thu, Jan 11, 2024 at 5:03 PM Nick Wilson (Quiddity) <
nwil...@wikimedia.org> wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2024/03
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F03=page
>

The text of the newsletter is now final.

*Four items have been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Bug 2049217] [NEW] requestsync fails with ModuleNotFoundError: No module named 'keyring' error

[Neil Wilson]

Public bug reported:

Ubuntu Noble

requestsync has started failing on this version of Ubuntu

$ requestsync mkosi
Traceback (most recent call last):
  File "/usr/bin/requestsync", line 402, in 
main()
  File "/usr/bin/requestsync", line 187, in main
Launchpad.login(service=args.lpinstance, api_version="devel")
  File "/usr/lib/python3/dist-packages/ubuntutools/lp/lpapicache.py", line 84, 
in login
self.__lp = LP.login_with("ubuntu-dev-tools", service, version=api_version)
^^^
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 700, in 
login_with
return cls._authorize_token_and_login(
   ^^^
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 445, in 
_authorize_token_and_login
cached_credentials = credential_store.load(
 ^^
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 345, 
in load
return self.do_load(unique_key)
   
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 423, 
in do_load
self._ensure_keyring_imported()
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 388, 
in _ensure_keyring_imported
import keyring
ModuleNotFoundError: No module named 'keyring'

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-dev-tools 0.197
ProcVersionSignature: User Name 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: brightbox
CloudName: brightbox
CloudPlatform: ec2
CloudRegion: gb1s-
CloudSerial: 20240104
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Fri Jan 12 16:18:42 2024
PackageArchitecture: all
SourcePackage: ubuntu-dev-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-dev-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cloud-image noble

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049217

Title:
  requestsync fails with ModuleNotFoundError: No module named 'keyring'
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2049217/+subscriptions


-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

[Translators-l] Ready for translation: Tech News #03 (2024)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2024/03

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F03=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Bug#1060431: mkosi: nspawn settings are no longer copied into place

[Neil Wilson]

Package: mkosi
Version: 20-1
Severity: normal
Tags: upstream patch
X-Debbugs-Cc: n...@aldur.co.uk

Dear Maintainer,

v20 erroneously removed the copy nspawn settings functionality even
though it continues to be used by 'machinectl pull-tar'. This has been
reversed upstream, and I would if you could backport the patch to the
packaged version.

The upstream bug is at https://github.com/systemd/mkosi/issues/2264

and the patch commit is at 
https://github.com/systemd/mkosi/pull/2265/commits/3aeccca0539194fc931fcd6a32375505ddd43ad3


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.9-cloud-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mkosi depends on:
ii  bubblewrap 0.8.0-2
ii  fdisk  2.39.3-6
ii  python33.11.6-1
ii  systemd255.2-4
ii  systemd-container  255.2-4
ii  util-linux 2.39.3-6

Versions of packages mkosi recommends:
ii  archlinux-keyring0~20231222-1
ii  btrfs-progs  6.6.3-1
ii  cryptsetup-bin   2:2.6.1-6+b1
ii  debian-archive-keyring   2023.4
ii  dnf  4.14.0-4.1
ii  dosfstools   4.2-1
ii  e2fsprogs1.47.0-2+b1
ii  erofs-utils  1.7.1-1
ii  gnupg2.2.40-1.1
ii  openssh-client   1:9.6p1-2
ii  ovmf 2023.11-4
ii  pacman-package-manager   6.0.2-4
ii  python3-cryptography 41.0.7-2
ii  python3-pefile   2023.2.7-3
ii  squashfs-tools   1:4.6.1-1
ii  systemd-timesyncd255.2-4
ii  ubuntu-archive-keyring   2023.11.28.1-0.2
ii  ubuntu-keyring [ubuntu-archive-keyring]  2023.11.28.1-0.2
ii  xz-utils 5.4.5-0.3
ii  zstd 1.5.5+dfsg2-2
ii  zypper   1.14.68-1

mkosi suggests no packages.

-- no debconf information

Bug#1060431: mkosi: nspawn settings are no longer copied into place

[Neil Wilson]

Package: mkosi
Version: 20-1
Severity: normal
Tags: upstream patch
X-Debbugs-Cc: n...@aldur.co.uk

Dear Maintainer,

v20 erroneously removed the copy nspawn settings functionality even
though it continues to be used by 'machinectl pull-tar'. This has been
reversed upstream, and I would if you could backport the patch to the
packaged version.

The upstream bug is at https://github.com/systemd/mkosi/issues/2264

and the patch commit is at 
https://github.com/systemd/mkosi/pull/2265/commits/3aeccca0539194fc931fcd6a32375505ddd43ad3


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.9-cloud-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mkosi depends on:
ii  bubblewrap 0.8.0-2
ii  fdisk  2.39.3-6
ii  python33.11.6-1
ii  systemd255.2-4
ii  systemd-container  255.2-4
ii  util-linux 2.39.3-6

Versions of packages mkosi recommends:
ii  archlinux-keyring0~20231222-1
ii  btrfs-progs  6.6.3-1
ii  cryptsetup-bin   2:2.6.1-6+b1
ii  debian-archive-keyring   2023.4
ii  dnf  4.14.0-4.1
ii  dosfstools   4.2-1
ii  e2fsprogs1.47.0-2+b1
ii  erofs-utils  1.7.1-1
ii  gnupg2.2.40-1.1
ii  openssh-client   1:9.6p1-2
ii  ovmf 2023.11-4
ii  pacman-package-manager   6.0.2-4
ii  python3-cryptography 41.0.7-2
ii  python3-pefile   2023.2.7-3
ii  squashfs-tools   1:4.6.1-1
ii  systemd-timesyncd255.2-4
ii  ubuntu-archive-keyring   2023.11.28.1-0.2
ii  ubuntu-keyring [ubuntu-archive-keyring]  2023.11.28.1-0.2
ii  xz-utils 5.4.5-0.3
ii  zstd 1.5.5+dfsg2-2
ii  zypper   1.14.68-1

mkosi suggests no packages.

-- no debconf information

Re: [go-cd] Are optional artifacts possible ?

[Chad Wilson]

It's a reasonable question. Possible different way of thinking about this:

When you have varying numbers of artifacts that are related to one another,
put them in a directory together and artifact the whole directory as a
single artifact (on the upload side). That way it is not dependent on any
individual log, result etc. Either use scripting to collect them together
post build (pre artifact) or change build scripting to ensure things all go
into "one place".

If I recall correctly, you can still pull sub-paths of a given artifact in
dependent pipelines rather than the "whole thing", in a way that the
dependent job will fail if the artifact didn't include a given file/folder.
(if I am wrong on this, this is not a great suggestion) This would allow to
weaken some of the "contract" mentioned below?

-Chad


On Thu, Jan 11, 2024 at 12:29 PM 'Alexey Savchkov' via go-cd <
go-cd@googlegroups.com> wrote:

> Can we come back to this point in 2024? Optional artifacts is a valid and
> natural case and are common in other CI systems. For example, when running
> tests I want to collect core dumps if they occur. Another example is a job
> which depending on its input parameters produces a varying number of
> artifacts (optional debug files, logs, reports or similar). The necessity
> to make dummy artifacts in all such cases only to satisfy GoCD internal
> logic is troublesome and disturbing. Could you please consider adding an
> "optional" attribute of the artifact element?
>
> четверг, 25 июня 2015 г. в 20:10:09 UTC+6, Aravind SV:
>
>> On Thu, Jun 25, 2015 at 7:19 AM, Pat McGrath  wrote:
>>
>>> So it seems unless you generate content the job will fail, is it
>>> possible to indicate that the artifact is optional ?
>>>
>>
>> No. :( The artifact declaration is a contract, something the downstream
>> pipelines can depend on.
>>
>> You can have a final task which creates dummy files, I suppose. But, that
>> feels like cheating. If a downstream pipeline uses it, then it will need to
>> validate that it is not a dummy file.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/aa2762ac-18e9-4fff-a7bc-37a7a92be694n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH8hmiS8%3DDidFVTqjAERs6-tG%3Dnmed_O5%2B5cuY%3DPzj0%2BpQ%40mail.gmail.com.

Re: Seeking the public discussion of Algerian Root CA

[Ben Wilson]

Dear Peter,

It appears that there is a root CA certificate inclusion case open in the
CCADB, with information viewable here:
https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1010

As you can see, some of the required information has not been populated
yet.

However, there is an "Add/Update Root Request" case open, too, Case #1444,
last edited in July 2023, but the information in that case is not complete
either and needs to be updated, and that case has not been submitted yet
for review and synchronization with the CCADB.

As stated in the Bugzilla bug you referenced, here is some guidance on the
root inclusion process used by Mozilla:
https://wiki.mozilla.org/CA/Application_Process.  Each root store has its
own separate inclusion process.

For assistance on a variety of topics related to Mozilla's CA program,
visit this web page:  https://wiki.mozilla.org/CA.

Sincerely yours,
Ben Wilson



On Wed, Jan 10, 2024 at 8:29 AM Peter Mate Erdosi  wrote:

> Hello all,
>
> thank you for being here.
>
> I seek the details of the public discussion of Algerian Root CA inclusion.
>
> I found only this: https://bugzilla.mozilla.org/show_bug.cgi?id=1736904
>
> Could somebody help me where can I find the details of this inclusion
> process if exists?
>
> Thank you in advance!
>
> Best Regards,
> Peter
>
> --
> You received this message because you are subscribed to the Google Groups
> "CCADB Public" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to public+unsubscr...@ccadb.org.
> To view this discussion on the web visit
> https://groups.google.com/a/ccadb.org/d/msgid/public/CADuWVBXsFqjXA6g-2gkDf%3D520eWRNB57OCVWWrx9cAwjAc%3DqRg%40mail.gmail.com
> <https://groups.google.com/a/ccadb.org/d/msgid/public/CADuWVBXsFqjXA6g-2gkDf%3D520eWRNB57OCVWWrx9cAwjAc%3DqRg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtaav7VWy7MFLWTFqo-%3DQXkh7%3DRhrbJGJGLECRreXZqJF-A%40mail.gmail.com.

Re: [ovs-dev] [PATCH 20/22] ovsdb-server: Allow user-provided config files.

[Terry Wilson]

On Mon, Jan 8, 2024 at 8:17 AM Ilya Maximets  wrote:
>
> On 1/5/24 21:26, Terry Wilson wrote:
> > On Wed, Dec 13, 2023 at 7:05 PM Ilya Maximets  wrote:
> >
> >> -/* Clears and replaces 'remotes' and 'dbnames' by a configuration read 
> >> from
> >> - * 'config_file', which must have been previously written by 
> >> save_config(). */
> >> -static void
> >> +/* Clears and replaces 'remotes' and 'db_conf' by a configuration read 
> >> from
> >> + * 'config_file', which must have been previously written by save_config()
> >> + * or provided by the user with --config-file.
> >> + * Returns 'true', if parsing was successful, 'false' otherwise. */
> >> +static bool
> >>  load_config(FILE *config_file, struct shash *remotes,
> >>  struct shash *db_conf, char **sync_from,
> >>  char **sync_exclude, bool *is_backup)
> >> @@ -2890,17 +3117,34 @@ load_config(FILE *config_file, struct shash 
> >> *remotes,
> >>  struct json *json;
> >
> > I'm wondering if having an argument for everything we parse out of a
> > config file might get a little unwieldy down the road. Say we add
> > configuration of SSL stuff, etc. Maybe it's something we could modify
> > as it becomes an issue, but it might be nice to have something for
> > config options that is similar to what we have for registering unixctl
> > commands or struct ctl_command_syntax. Documentation could be added as
> > part of the registration/definition of the config option, there could
> > be a .get() that parses the values out of the json, and a .run() that
> > gets called after all of the parsing is shown to succeed.
> >
> > Terry
> >
>
> Hi, Terry.  Yes, I agree that the current interface is far from being
> ideal, and I actually tried to rework it multiple times while working
> on this patch set.  That's one of the reasons it took so long. :)
> Unfortunately it ended up with a huge amount of refactoring every time.
> The main reason for that, I think, is the fact that the same function
> is used for loading the legacy internal configuration file and the new
> user-provided file.  And the code around legacy internal configuration
> is not easy to adapt.
>
> I think, it would be much easier to do this kind of refactoring once
> we deprecate and remove all the appctl commands that can change the
> server configuration.  For now I decided to keep the interface as it is
> without this patch set to avoid making the patch set even bigger.
> I hope that makes sense.
>
> The idea of registering the options with a common parsing logic sounds
> interesting though and definitely worth exploring in the future.
>
> Best regards, Ilya Maximets.

Yeah, I'm all for merging as-is and prettying up as needed.

In case you have entirely too much free time on your hands (ha!),
here's an ini-style config loading/reloading framework I wrote many
many years ago (Warning: I'd only been programming professionally for
~3 years or so at that point). Asterisk was very modular and had over
100 different config files, and many of them used ini files in
completely different ways so it's definitely more generic and overkill
for what we are needing, but there may be some useful ideas [1-5] if
you ignore all of the macro/varargs magic. ;)

The general idea was a per-module `aco_info` structure that defined
the information that was obtained from configs, `aco_type` structures
that defined what parts of the config file matched up to what fields
of the `aco_info` struc, and aco_option_register() which would define
the specific options set under each [category], how they were matched,
what fields in a struct they set, etc. aco_option_register_custom()
just used custom callback functions to handle setting things up.
aco_process_config() would be called on load/reload and would parse
the config file and create an internal 'pending' representation of the
user-defined aco_info and then if parsing succeeded would then
atomically swap the pending and live aco_info pointers. There were
also pre_apply and post_apply callbacks so modules could do special
things if needed during reloads, etc. Prior to the patch modules would
often just modify their internal structures as the config file was
being processed, so if there was a parse error things would just be
left in a state where configs were partially applied.

Anyway, it may or may not be interesting and certainly isn't something
we need to worry about right now. Just food for thought.

Terry

[1] 
https://github.com/asterisk/asterisk/blob/master/include/asterisk/config_options.h
[2] https://github.com/asterisk/asterisk/blob/master/main/config_options.c
[3] 
https://github.com/asterisk/asterisk/blob/master/configs/samples/app_ske

Re: known bad certs blocklist

[Ben Wilson]

Hello Jan,
This OneCRL list might be what you are looking for -
https://crt.sh/mozilla-onecrl.
Ben

On Tue, Jan 9, 2024 at 9:17 AM 'Jan Schaumann' via
dev-security-policy@mozilla.org  wrote:

> Hello,
>
> Is there a community-shared blocklist of known bad
> certs (keys)?
>
> Chrome has
>
> https://chromium.googlesource.com/chromium/src/+/master/net/data/ssl/blocklist/README.md
>
> Apple / Safari has
> https://support.apple.com/en-us/103255
>
> I don't recall if Firefox has a list?
>
> Either way, it would be useful to have a community
> shared list of known compromised keys or otherwise
> revoked roots or intermediates.  Does that already
> exist?
>
> -Jan
>
> --
> You received this message because you are subscribed to the Google Groups "
> dev-security-policy@mozilla.org" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dev-security-policy+unsubscr...@mozilla.org.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/ZZ1xe9_3hGFovkqT%40netmeister.org
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabK%2B4988jZU9Z_Hsjjitr-NyinTrYUWOjUf4HDWBKAN5w%40mail.gmail.com.

OT Not quite astro stuff

[mike wilson]

I'm wondering why the EV/screen failed...
 
https://youtu.be/SxkA82wORtw?si=QqvpvOW8eOgOi9XX
 
 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Re: Ready for translation: Tech News #02 (2024)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 18 languages) to 1,107 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2024, week 02

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2024/02. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Ghanaian
Pidgin , Nederlands
, Tiếng Việt
, español
, français
, italiano
, norsk bokmål
, polski
, suomi
, svenska
, čeština
, українська
, עברית
, हिन्दी
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - mediawiki2latex  is a tool that
   converts wiki content into the formats of LaTeX, PDF, ODT, and EPUB. The
   code now runs many times faster due to recent improvements. There is also
   an optional Docker container you can install
   

   on your local machine.
   - The way that Random pages are selected has been updated. This will
   slowly reduce the problem of some pages having a lower chance of appearing.
   [1] 

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 9 January. It
   will be on non-Wikipedia wikis and some Wikipedias from 10 January. It will
   be on all wikis from 11 January (calendar
   ). [2]
   [3]
   

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- wikitech-ambassadors@lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-le...@lists.wikimedia.org

Re: [go-cd] Mac agent unable to connect to server

[Chad Wilson]

There's no error shown in that log file, which just means that the
bootstrapper/launcher is starting OK - but doesn't tell us much else.

You need to look at the other agent logs to see why it is failing to
register with the server. Look in the logs directory for the others (for
most problems you want to look at go-agent.log rather than
go-agent-bootstrapper.log or go-agent-launcher.log).

-Chad

On Sat, Jan 6, 2024 at 6:47 AM Manojsai katakam 
wrote:

> Hi all,
>
> We have an issue to Mac agent connecting to the gocd server.
> Go-server version: 20.5.0
> Go-agent version: 20.5.0
>
> Logs :
>
> *$hostname:Go Agent di$ ./bin/go-agent console*
> Running go-agent...
> wrapper  | --> Wrapper Started as Console
> wrapper  | Java Service Wrapper Standard Edition 64-bit 3.5.41
> wrapper  |   Copyright (C) 1999-2019 Tanuki Software, Ltd. All Rights
> Reserved.
> wrapper  | http://wrapper.tanukisoftware.com
> wrapper  |   Licensed to ThoughtWorks for GoCD Agent
> wrapper  |
> wrapper  | Launching a JVM...
> jvm 1| WrapperManager: Initializing...
> jvm 1| [Fri Jan 05 16:31:18 CST 2024] Starting process:
> jvm 1| [Fri Jan 05 16:31:18 CST 2024]   Working directory:
> /path/to/Go Agent
> jvm 1| [Fri Jan 05 16:31:18 CST 2024]   Application arguments:
> [-serverUrl, http://192.168.60.122:8154/go]
> jvm 1| [Fri Jan 05 16:31:18 CST 2024]GoCD Version:
> 20.5.0-11820
> jvm 1| [Fri Jan 05 16:31:18 CST 2024]Java Version: 11.0.21
> jvm 1| [Fri Jan 05 16:31:18 CST 2024]Operating System: Mac OS
> X(13.3.1)
> jvm 1| Could not find file `config/agent-bootstrapper-logback.xml'.
> Attempting to load from classpath.
> jvm 1| Using classpath resource
> `jar:onejar:lib/agent-bootstrapper-20.5.0-11820-classes.jar!/config/agent-bootstrapper-logback.xml'.
> jvm 1| SLF4J: Class path contains multiple SLF4J bindings.
> jvm 1| SLF4J: Found binding in
> [jar:onejar:lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> jvm 1| SLF4J: Found binding in
> [jar:file://path/to/Go%20Agent/data/deps-5225b8a899113f2c-agent-launcher.jar/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> jvm 1| SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings
> for an explanation.
> jvm 1| SLF4J: Actual binding is of type
> [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> jvm 1| Could not find file `config/agent-launcher-logback.xml'.
> Attempting to load from classpath.
> jvm 1| Using classpath resource
> `jar:file:/path/to/Go%20Agent/data/deps-5225b8a899113f2c-agent-launcher.jar/agent-launcher-20.5.0-11820-classes.jar!/config/agent-launcher-logback.xml
>
> Thanks & Regards,
> Manoj K
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CAEbMZ9sfq0GnY0n-1wDTLyjoinK4E89j2SNohkRqEuFNZuk7nA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH-Q5xYx3UMczrwDQzYhEgjiAJ0NkW1B26QYeU8%3DNpXQ1Q%40mail.gmail.com.

[Translators-l] Re: Ready for translation: Tech News #02 (2024)

[Nick Wilson (Quiddity)]

On Thu, Jan 4, 2024 at 6:51 PM Nick Wilson (Quiddity) 
wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2024/02
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F02=page
>

The text of the newsletter is now final.
*One item has been added* since yesterday.
There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [ovs-dev] [PATCH 20/22] ovsdb-server: Allow user-provided config files.

[Terry Wilson]

On Wed, Dec 13, 2023 at 7:05 PM Ilya Maximets  wrote:

> -/* Clears and replaces 'remotes' and 'dbnames' by a configuration read from
> - * 'config_file', which must have been previously written by save_config(). 
> */
> -static void
> +/* Clears and replaces 'remotes' and 'db_conf' by a configuration read from
> + * 'config_file', which must have been previously written by save_config()
> + * or provided by the user with --config-file.
> + * Returns 'true', if parsing was successful, 'false' otherwise. */
> +static bool
>  load_config(FILE *config_file, struct shash *remotes,
>  struct shash *db_conf, char **sync_from,
>  char **sync_exclude, bool *is_backup)
> @@ -2890,17 +3117,34 @@ load_config(FILE *config_file, struct shash *remotes,
>  struct json *json;

I'm wondering if having an argument for everything we parse out of a
config file might get a little unwieldy down the road. Say we add
configuration of SSL stuff, etc. Maybe it's something we could modify
as it becomes an issue, but it might be nice to have something for
config options that is similar to what we have for registering unixctl
commands or struct ctl_command_syntax. Documentation could be added as
part of the registration/definition of the config option, there could
be a .get() that parses the values out of the json, and a .run() that
gets called after all of the parsing is shown to succeed.

Terry

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] python: idl: Handle monitor_canceled

[Terry Wilson]

On Fri, Jan 5, 2024 at 9:56 AM Simon Horman  wrote:
>
> On Mon, Dec 18, 2023 at 05:31:24PM -0600, Terry Wilson wrote:
> > Currently python-ovs claims to be "db change aware" but does not
> > parse the "monitor_canceled" notification. Transactions can continue
> > being made, but the monitor updates will not be sent. This handles
> > monitor_cancel similarly to how ovsdb-cs currently does.
> >
> > Signed-off-by: Terry Wilson 
>
> Hi Terry,
>
> is it possible to add a test to tests/ovsdb-idl.at for this feature?

It might be, but it seems like it'd be a bit of work and I'm not sure
if I'll have the time to look at it for a while. I'm just trying to
bring the functionality up to what the C IDL has and from what I can
tell this feature isn't tested in the C IDL either. What I'm doing to
manually test is to run this:

import logging
import ovs

import ovsdbapp.schema.ovn_northbound.impl_idl as nb_idl
from ovsdbapp.backend.ovs_idl import connection, vlog

print(f"Using OVS {ovs.__file__}")
logging.basicConfig(level=logging.DEBUG)
vlog.use_python_logger()
LOG = logging.getLogger(__name__)

remote = "unix:///home/twilson/src/ovn/tutorial/sandbox/nb1.ovsdb"

def get_idl():
   """Connection getter."""

   idl = connection.OvsdbIdl.from_server(remote, "OVN_Northbound",
 leader_only=False)
   return nb_idl.OvnNbApiIdlImpl(connection.Connection(idl, 100))

idl = get_idl()
LOG.info(f"monitor_id: {str(idl.idl.uuid)}")
LOG.info(f"server_monitor_id: {str(idl.idl.server_monitor_uuid)}")
input(" Press Enter ")
idl.ls_add("test").execute(check_error=True)

and then in another window running:
ovsdb-client convert
unix:/home/twilson/src/ovn/tutorial/sandbox/nb1.ovsdb
/home/twilson/src/ovn/ovn-nb.ovsschema

and then pressing enter in the original window. Without the patch,
after running the ovsdb-client convert, you get:
DEBUG:ovsdbapp.backend.ovs_idl.vlog:unix:///home/twilson/src/ovn/tutorial/sandbox/nb1.ovsdb:
received unexpected notification message
and then ovsdbapp starts throwing exceptions. With the patch, things
work as one would expect.

The problem with testing is that the client connection needs to be
active during the monitor_canceled that happens when ovsdb-client
convert is called. The tests in ovsdb-idl.at use ovsdb-client transact
for doing everything, so it's not easy to do the convert between
connection and transaction execution.

Maybe something could be added test test-ovsdb.py stuff.

Terry




Terry

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[Translators-l] Ready for translation: Tech News #02 (2024)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2024/02

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2024%2F02=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

Re: [cobirds] Question on abbreviation

[Tyler Wilson]

Low estimate.

Tyler Wilson
Adams County

On Jan 4, 2024, at 2:42 PM, Lesley Brown  wrote:

I've seen an abbreviation " LE" used several times on eBird that has me 
puzzled.  It's found underneath the bird seen, such as Bald Eagle or Canada 
Goose.  What does LE stand for?  All I know is Law Enforcement, lol!  I've 
looked all over but can't find it mentioned on any abbreviation list.

Happy New Year and thanks for the help!

Lesley Brown
Highlands Ranch
Douglas County

--
--
You received this message because you are subscribed to the Google
Groups "Colorado Birds" group.
To post to this group, send email to cobirds@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cobirds?hl=en?hl=en
* All posts should be signed with the poster's full name and city. Include bird 
species and location in the subject line when appropriate
* Join Colorado Field Ornithologists https://cobirds.org/CFO/Membership/
---
You received this message because you are subscribed to the Google Groups 
"Colorado Birds" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
cobirds+unsubscr...@googlegroups.com<mailto:cobirds+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/cobirds/1fb55f1e-526d-40ef-bc90-3136efafc2edn%40googlegroups.com<https://groups.google.com/d/msgid/cobirds/1fb55f1e-526d-40ef-bc90-3136efafc2edn%40googlegroups.com?utm_medium=email_source=footer>.

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Colorado Birds" group.
To post to this group, send email to cobirds@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cobirds?hl=en?hl=en
* All posts should be signed with the poster's full name and city. Include bird 
species and location in the subject line when appropriate
* Join Colorado Field Ornithologists https://cobirds.org/CFO/Membership/
--- 
You received this message because you are subscribed to the Google Groups 
"Colorado Birds" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cobirds+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/cobirds/SJ0PR06MB7359067079114C37D4D1E06ECF672%40SJ0PR06MB7359.namprd06.prod.outlook.com.

Re: Improvements to Vulnerability Disclosure wiki page

[Ben Wilson]

Thanks, Roman

I have added "Email Address / Group Distribution List" as a clarification.
However, additional contact information such as a phone number might be
needed in exceptional cases, but we can request that if needed.

Ben

On Wed, Nov 22, 2023 at 11:07 PM Roman Fischer 
wrote:

> Dear Ben,
>
>
>
> Thanks for the effort you put into this and especially to align the
> markdown template to the regular incident reporting template as much as
> possible.
>
>
>
> Regarding the “Contact Information”: What is Mozilla’s expectation here?
> An e-mail address (personal or group mailbox), phone number (plus timezone
> so that people aren’t called in the middle of “their” night)? Or… ?
>
>
>
> As for the other details in such a report: They look plausible and I guess
> they are the result of previous incidents and details that were missing in
> the initial communication.
>
>
>
> Kind regards
> Roman
>
>
>
> *From:* dev-security-policy@mozilla.org  *On
> Behalf Of *Ben Wilson
> *Sent:* Mittwoch, 22. November 2023 20:35
> *To:* dev-secur...@mozilla.org 
> *Subject:* Re: Improvements to Vulnerability Disclosure wiki page
>
>
>
> All,
>
> For your review and comment, today I reorganized the security incident and
> vulnerability disclosure report's expected contents
> <https://wiki.mozilla.org/CA/Vulnerability_Disclosure#Reportable_Vulnerability.2FIncident_Disclosure_Contents>
> and added a markdown template
> <https://wiki.mozilla.org/CA/Vulnerability_Disclosure#Markdown_Template>
> that can be used in Bugzilla.
>
> Ben
>
>
>
> On Wed, Sep 27, 2023 at 11:47 AM Ben Wilson  wrote:
>
> All,
>
> As mentioned in a previous email, I am soliciting feedback regarding the 
> Vulnerability
> Disclosure wiki page
> <https://wiki.mozilla.org/CA/Vulnerability_Disclosure>. If you have any
> specific suggestions that we can use to enhance clarity or to make the page
> more complete, please don't hesitate to share them, either here or directly
> with me. Your feedback is instrumental in our commitment to maintain a safe
> and secure online environment.
>
> Thanks,
>
> Ben
>
> --
> You received this message because you are subscribed to the Google Groups "
> dev-security-policy@mozilla.org" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dev-security-policy+unsubscr...@mozilla.org.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabbqDu6N7yPnU9uL0RZQXPiMquHh-1FxTmPbQSeOj8T5w%40mail.gmail.com
> <https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabbqDu6N7yPnU9uL0RZQXPiMquHh-1FxTmPbQSeOj8T5w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabhgCGjyeX_OtC9iT177XihXpCLHXgQvNgyrGh0rLCMMA%40mail.gmail.com.

Re: [cabfpub] Voting Period begins: Ballot FORUM-020 v2 - Amend Code Signing Certificate Working Group Charter

[Ben Wilson via Public]

Mozilla votes "Yes" on Ballot FORUM-020 v.2.

On Thu, Jan 4, 2024 at 1:02 PM Martijn Katerbarg via Public <
public@cabforum.org> wrote:

> *Ballot FORUM-020 **v2 - Amend Code Signing Certificate Working Group
> Charter*
>
>
>
> *Purpose of Ballot*
>
> This ballot proposes to amend the Code Signing Certificate Working Group
> (CSCWG) Charter with the following changes:
>
>- Bump the Charter version.
>- Add a limited scope for timestamp certificates.
>- Remove the version reference of the bylaws that we follow.
>- During a ballot, count only members that are in a voting class,
>disregarding associate members and interested parties.
>- Align Quorum definition as half the average, as the Bylaws have it
>set.
>
>
>
> The following motion has been proposed by Martijn Katerbarg of Sectigo and
> endorsed by Bruce Morton of Entrust and Dimitris Zacharopoulos of HARICA.
>
>
>
> - Motion Begins -
>
>
>
> MODIFY the Charter of the Code Signing Certificate Working Group as
> specified in the following redline:
>
> https://github.com/cabforum/forum/compare/59185f16917cc7f5b83564fe5fddff32cf84c8ce...b80c98b80ee132e2a3adf09bfa8ba7448084d11d
> 
>
>
>
> - Motion Ends -
>
>
>
> This ballot does not propose a Final Guideline or Final Maintenance
> Guideline.
>
>
>
> The procedure for approval of this ballot is as follows:
>
>
>
> Discussion Period (7+ days)
>
> Start Time: 2023-12-14 – 16:00 UTC
>
> End Time: 2024-01-04 – 20:00 UTC
>
>
>
> Vote for approval (7 days)
>
> Start Time: 2024-01-04 – 20:00 UTC
>
> End Time:  2024-01-11 – 20:00 UTC
>
>
>
>
>
>
>
>
> ___
> Public mailing list
> Public@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/public
>
___
Public mailing list
Public@cabforum.org
https://lists.cabforum.org/mailman/listinfo/public

Re: [Infrastructure] cabforum.org website with more automation

[Ben Wilson via Infrastructure]

This looks very good and very promising.  Thanks, Paul.
Ben

On Thu, Jan 4, 2024 at 1:29 PM Paul van Brouwershaven via Infrastructure <
infrastructure@cabforum.org> wrote:

> I started to convert the cabforum.org website to Hugo to give us more
> automation, you can see a preview here:
> https://cabforum.github.io/cabforum.org/
>
>
>- The homepage needs some work, currently just listing the latest
>posts.
>   - The homepage is currently always blue as GitHub does not publish
>   at the root "/" of the domain.
>- The latest documents are automatically included from GitHub
>(example,
>https://cabforum.github.io/cabforum.org/working-groups/smime/latest/)
>- The document release information is automatically downloaded and
>included in the sidebar, currently not working as of rate limiting, need to
>set a GitHub API key, also not all repositories create releases.
>- The post URLs need to be corrected; this should be a simple config.
>- I did not copy the dropdown menu's for now, this is quite
>complicated with pure bootstrap (like you can't have a hover that is also
>clickable) and want to keep things simple now. This is why I moved the sub
>menu to the right, only three levels are currently shown in the right menu,
>I need to make this recursive as we also have four levels.
>- I re-organized the pages/urls a bit, but included an alias for the
>original URLs, might need to tune this a bit further and will run a script
>to update all the URLs in the contents.
>- Search index is automatically updated on publication.
>- I will add a query to automatically list all minutes (posts with tag
>minutes and working group id)
>- We need to review the site contents for any other errors.
>- When the member tools can expose information in JSON (i.e., API) we
>can automatically include that information as well (such as members), the
>same for ballots (or we can get that information from GitHub
>issues/pull-requests), we can also query the old Google Sheets.
>
>
> On the right bottom of each page you will find an edit button, which will
> bring you to the markdown contents on GitHub.
>
> Some quick instruction are included in the readme of the repository:
> https://github.com/cabforum/cabforum.org/tree/main
>
> Let me know if you see any issues not mentioned above or if you have any
> other suggestions, comments or concerns.
>
> Paul
>
>
> *Any email and files/attachments transmitted with it are intended solely
> for the use of the individual or entity to whom they are addressed. If this
> message has been sent to you in error, you must not copy, distribute or
> disclose of the information it contains. Please notify Entrust immediately
> and delete the message from your system.*
> ___
> Infrastructure mailing list
> Infrastructure@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/infrastructure
>
___
Infrastructure mailing list
Infrastructure@cabforum.org
https://lists.cabforum.org/mailman/listinfo/infrastructure

Re: [Servercert-wg] Section 7.1.5 as required by RFC 3647 is no longer in the TLS BRs

[Ben Wilson via Servercert-wg]

I think this is listed as an issue in GitHub -
https://github.com/cabforum/servercert/issues/444.

On Thu, Jan 4, 2024 at 4:54 AM Dimitris Zacharopoulos (HARICA) via
Servercert-wg  wrote:

> Dear Members,
>
> While taking another pass at reviewing the new certificate profiles
> introduced in ballot SC62, I realized that there is some deviation from the
> RFC 3647 structure that the BRs should maintain to help alignment of CA
> CP/CPS documents.
>
> This is the structure defined by RFC 3647 for section 7:
>
>7.  CERTIFICATE, CRL, AND OCSP PROFILES
>7.1  Certificate profile
>7.1.1  Version number(s)
>7.1.2  Certificate extensions
>7.1.3  Algorithm object identifiers
>7.1.4  Name forms
>7.1.5  Name constraints
>7.1.6  Certificate policy object identifier
>7.1.7  Usage of Policy Constraints extension
>7.1.8  Policy qualifiers syntax and semantics
>7.1.9  Processing semantics for the critical Certificate Policies
>
>
> Section 7.1.5 does not exist anymore. The BRs have the name constraints
> information in 7.1.2.5.2, 7.1.2.10.8. I believe that, at a minimum, we
> should re-introduce 7.1.5 and point to other subsections of 7.1.2 for
> consistency with RFC 3647.
>
> Thoughts?
> Dimitris.
>
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [go-cd] Is possible to run task parallel

[Chad Wilson]

Indeed, you need the ability to have multiple agents running in parallel to
be able to do multiple jobs in parallel. The best way to achieve this
depends on 1) your installation/deployment choice 2) your agent
requirements 3) whether you are experimenting or thinking about a
production deployment.

If you want to use "static" agents directly as processes at OS level, there
is
https://docs.gocd.org/current/advanced_usage/admin_install_multiple_agents.html

Otherwise you can use "elastic" (dynamically created) agents
 via a
plugin , e.g to run multiple
agents on a single host within Docker (here
), or if you
are familiar with Kubernetes running GoCD or its agents inside Kubernetes
(use either multiple static agents, or elastic agents - even for
experimenting locally).

-Chad

On Thu, Jan 4, 2024 at 5:40 PM Sriram Narayanan  wrote:

> No
>
> On Thu, 4 Jan 2024 at 3:02 PM, Vijay A  wrote:
>
>>
>> I have installed GoCD server. And Installed one GoCD Agent.
>>
>> Now i created a new pipeline : Pipeline1
>>
>> Created one stage : Stage1
>>
>> Now two jobs: Job1 and Job2
>>
>> As i am having one GoAgent, does these two jobs will be executed
>> parallely.is there any way to achieve this ?
>>
>> Yes, add a second good agent. Ensure that both the go agents and The job
> are marked as the same “resource”.
>
>
> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/b832fcba-6af7-4516-8420-3e97055bf486n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CANiY96aAwLpWERzOoeecEksG0NY1im3V4X6FQO9HReC%3DMXQYAA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH8QWsOFZ8SnevVkXScP01bCFKUt6g--vWpY5Q%2B9zXo%2BDg%40mail.gmail.com.

Deutsche Telekom Security's Root Inclusion Request

[Ben Wilson]

 All,

Public discussion began on the CCADB Public List on Nov. 1, 2023 (
https://groups.google.com/a/ccadb.org/g/public/c/yiJ-bkv-Ftg/m/JsbbxpZJBAAJ)
and concluded on Dec. 13 (
https://groups.google.com/a/ccadb.org/g/public/c/yiJ-bkv-Ftg/m/lxwjZDvhAAAJ)
regarding Deutsche Telekom Security's request to include
the following root CA certificates in NSS:

   -

   Telekom Security SMIME ECC Root 2021 (email trust bit)


   -

   Telekom Security TLS ECC Root 2020 (websites trust bit)
   -

   Telekom Security SMIME RSA Root 2023 (email trust bit)
   -

   Telekom Security TLS RSA Root 2023 (websites trust bit)

Additional details concerning this request may be found in the
above-referenced discussions, in Bugzilla #1820592
, and in

CCADB Case Number 1269

.

This is notice that I am recommending approval of this request.

This begins a 7-day “last call” period for any final objections.

Thanks,

Ben

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtaaOjQuJ_zhkkbn6UymdBGxfw9k1SW94ER6-21PoVa%2BYyg%40mail.gmail.com.

[protobuf] Protocol Buffers with Ruby

[Jay Wilson]

I am not a ruby person, but the project requires ruby. I have a 6 year old 
piece of code I am attempting to update. I have recompiled the protobuf 
files and protoc decodes a captured input stream correctly; however, the 
code no longer works.  I wrote a very simple ruby program to show the 
issue. The issue is how do I reference the 2nd level of  nested protobuf 
messages that use proto2 syntax.

My simple code:








*input_stream = STDIN.readsvkmh = TelemetryStream.decode(input_stream)puts 
"Device : #{svkmh.system_id}"svkmh_ent = svkmh.enterpriseputs "Level 1 : 
#{svkmh_ent}"svkmh_jn = svkmh.enterprise.juniperNetworksputs "Level 2 : 
#{svkmh_jn}"*
The output from it:




*Device : Q5Level 1 : ../test.rb:17:in 
`method_missing': undefined method `juniperNetworks' for 
:EnterpriseSensors (NoMethodError) from 
../test.rb:17:in `'*

In the origin 6 year old code, this line worked:


*svkmh_jn = svkmh.enterprise.juniperNetworks*
And yet, protoc decodes it correctly: 















*$ protoc --decode TelemetryStream telemetry_top.proto < ~/data.gpb | head 
-25system_id: "poc-qfx5110-31"component_id: 65535sub_component_id: 
0sensor_name: "jti_3_1:/system/:/system/:jsd"sequence_number: 
27420timestamp: 1703006625404version_major: 1version_minor: 0enterprise {  
[juniperNetworks] {210 {  151 {151 {*
The proto file

//
// Copyrights (c) 2015, 2016, Juniper Networks, Inc.
// All rights reserved.
//
//
// Licensed to the Apache Software Foundation (ASF) under one
// or more contributor license agreements.  See the NOTICE file
// distributed with this work for additional information
// regarding copyright ownership.  The ASF licenses this file
// to you under the Apache License, Version 2.0 (the
// "License"); you may not use this file except in compliance
// with the License.  You may obtain a copy of the License at
//
//   http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing,
// software distributed under the License is distributed on an
// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied.  See the License for the
// specific language governing permissions and limitations
// under the License.
//
syntax = "proto2";
import "google/protobuf/descriptor.proto";
extend google.protobuf.FieldOptions {
optional TelemetryFieldOptions telemetry_options = 1024;
}
message TelemetryFieldOptions {
optional bool is_key = 1;
optional bool is_timestamp   = 2;
optional bool is_counter = 3;
optional bool is_gauge   = 4;
optional bool is_instance= 5;
optional bool is_gauge_min   = 6;
optional bool is_gauge_max   = 7;
}
message TelemetryStream {
required string system_id= 1 [(telemetry_options).is_key = 
true];
optional uint32 component_id = 2 [(telemetry_options).is_key = 
true];
optional uint32 sub_component_id = 3 [(telemetry_options).is_key = 
true];
optional string sensor_name  = 4 [(telemetry_options).is_key = 
true];
optional uint32 sequence_number  = 5;
optional uint64 timestamp= 6 [(telemetry_options).is_timestamp 
= true];
optional uint32 version_major= 7;
optional uint32 version_minor= 8;
optional bool eom= 9;
optional IETFSensors ietf= 100;
optional EnterpriseSensors *enterprise* = 101;
}
message IETFSensors {
extensions 1 to max;
}
message EnterpriseSensors {
extensions 1 to max;
}
extend EnterpriseSensors {
// re-use IANA assigned numbers
optional JuniperNetworksSensors *juniperNetworks* = 2636;
}
message JuniperNetworksSensors {
extensions 1 to max;
}

Thank you for the assistance 

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/protobuf/45f3103d-5610-45fe-a41e-a5f81f7c0059n%40googlegroups.com.

Re: S/MIME BR Transition Wiki Page

[Ben Wilson]

All,

I am editing the S/MIME Baseline Requirements transition guidance wiki page
(https://wiki.mozilla.org/CA/Transition_SMIME_BRs) slightly to make it more
clear that existing CA operators are to submit their S/MIME BR audit
reports consistent with their existing audit cycles. Right now, the
language on the wiki page says, "For CA operators to maintain their current
annual audit cycles, new S/MIME BR audits should be provided when they
provide their other annual audits."  This seems pretty straightforward.
But then it says, "Any root CA certificate being considered for inclusion
after October 30, 2023, must be audited according to the S/MIME BRs if the
email trust bit is to be enabled, and the CA operator’s CP or CPS must
state that they follow the current version of the S/MIME BRs."

This latter sentence might be inferred to mean that an earlier,
out-of-cycle audit would be required for new root CA certificates created
by existing CAs. I am recommending that we change this to make it clear
that if an existing CA operator has an email-trust-bit-enabled CA
certificate in the root store, then it can submit its S/MIME BR audit (that
will include new, email-enabled root CAs) when it provides its other
regularly-scheduled, other audits. For example, if a CA operator in the
Mozilla root program usually submits their audits in July, and they are
requesting the inclusion of a new email-enabled root CA, then that S/MIME
BR audit can be submitted in July, too.

Here are my suggested revisions:

For CA operators *that already have ** an email-trust-bit-enabled CA
certificate in the root store* to *may* maintain their current annual audit
cycles *and provide*, *the* new S/MIME BR audits should be provided when
they provide their other annual audit *report*s*, even if they are in the
process of requesting inclusion of one or more new, email-trust-bit-enabled
root CA certificates*. *For instance, if a CA operator typically provides
audit reports in July 2024 and is requesting the inclusion of a new
email-bit-enabled root CA, the corresponding S/MIME BR audit encompassing
both existing and new * *email-trust-bit-enabled* *root CA certificates can
be submitted during the annual audit submission in July 2024.*

*For any new CA operator requesting inclusion of a* Any root CA
certificate being
considered for inclusion after October 30, 2023, *the root CA *must be
audited according to the S/MIME BRs if the email trust bit is to be enabled
*.*

*A* , and the CA operator’s CP or CPS must state that they follow the
current version of the S/MIME BRs.

Are there any comments or suggestions?

Thanks,

Ben



On Wed, Jul 19, 2023 at 11:01 AM Ben Wilson  wrote:

> All,
>
> I have created a wiki page (
> https://wiki.mozilla.org/CA/Transition_SMIME_BRs) to address
> miscellaneous issues that might arise for CAs in their transition toward
> compliance with the CA/Browser Forum’s Baseline Requirements for S/MIME
> Certificates (S/MIME BRs). (The wiki page is for items that are not
> directly explained in the upcoming version 2.9 of the Mozilla Root Store
> Policy.)
>
> The first issue addressed in the wiki page relates to the re-issuance of
> existing intermediate CAs used for issuing S/MIME certificates. Based on
> language provided by Corey Bonnell, the wiki page explains how Mozilla
> expects S/MIME CA re-issuance to occur.
>
> We may add explanations about other items of concern to the wiki page in
> the future, and if so, I’ll advise you accordingly.
>
> Thanks,
>
> Ben
>

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabGsE5N9mJeOWaROcu17dTKtKfZf8tpjLDGS7jA49jVzg%40mail.gmail.com.

Bug#1059874: output of dmesg when trying gqrx

[Wilson Costrino]

[17674.068551] gqrx[3226752]: segfault at f4 ip 7f5fee944cd6 sp
7f5f967f8870 error 4
[17674.068551] gqrx[3226753]: segfault at f4 ip 7f5fee944cd6 sp
7f5f95ff7870 error 4 in libuhd.so.4.6.0[7f5fee721000+a5e000]
[17674.068558]  in libuhd.so.4.6.0[7f5fee721000+a5e000]
[17674.068557] traps: gqrx[3226749] general protection fault
ip:7f5fee944cd6 sp:7f5f977fb7d0 error:0
[17674.068558] gqrx[3226751]: segfault at f4 ip 7f5fee944cd6 sp
7f5f96ff9870 error 4
[17674.068560]  likely on CPU 9 (core 1, socket 0)
[17674.068560]  likely on CPU 10 (core 2, socket 0)


[17674.068563]  in libuhd.so.4.6.0[7f5fee721000+a5e000]
[17674.068562] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0
80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00
<44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89
[17674.068563] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0
80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00
<44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89
[17674.068564]  in libuhd.so.4.6.0[7f5fee721000+a5e000]

[17674.068569] traps: gqrx[3226745] general protection fault
ip:7f5fee944cd6 sp:7f5fbe7f99d0 error:0
[17674.068571] gqrx[3226754]: segfault at f4 ip 7f5fee944cd6 sp
7f5f957f6870 error 4
[17674.068575]  in libuhd.so.4.6.0[7f5fee721000+a5e000]
[17674.068576]  in libuhd.so.4.6.0[7f5fee721000+a5e000]

[17674.068578]  likely on CPU 12 (core 4, socket 0)
[17674.068580]  likely on CPU 14 (core 6, socket 0)
[17674.068580] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0
80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00
<44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89

[17674.068583] Code: ec 78 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0
80 bf c0 00 00 00 00 0f 85 ed 00 00 00 48 8b 45 30 48 8b 9d d0 00 00 00
<44> 8b b8 f4 00 00 00 48 85 db 0f 84 3a 01 00 00 48 8b 43 18 48 89


Obrigado,

Wilson Costrino
Linux Senior Consultant

PY2335SWL @ GG66pl

Omnia mutantur, nihil interit

Bug#1059874: libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0

[wilson costrino]

Package: libuhd4.6.0
Version: 4.6.0.0+ds1-5+b1
Severity: important
X-Debbugs-Cc: wilsonc4+debian...@gmail.com

Dear Maintainer,


   * What led up to the situation?
when trying to run sdr related softwares, specially gqrx, the system goes 
segfault 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
just run gqrx

   * What was the outcome of this action?
dmesg output showing segfault and traps in gqrx due to libuhd.so.4.6.0

   * What outcome did you expect instead?
none, just the program gqrx running normally


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libuhd4.6.0 depends on:
ii  libboost-chrono1.83.0 1.83.0-2
ii  libboost-filesystem1.83.0 1.83.0-2
ii  libboost-serialization1.83.0  1.83.0-2
ii  libboost-thread1.83.0 1.83.0-2
ii  libc6 2.37-12
ii  libgcc-s1 13.2.0-7
ii  libpython3.11 3.11.7-2
ii  libstdc++613.2.0-7
ii  libusb-1.0-0  2:1.0.26-1

libuhd4.6.0 recommends no packages.

Versions of packages libuhd4.6.0 suggests:
pn  uhd-host  

-- no debconf information

Re: I'm back

[mike wilson]

And the same to you.  And everyone else.
> On 31/12/2023 17:08 GMT Ralf R Radermacher  wrote:
> 
>  
> Companies like GMX are fine while everything works, but heaven help us 
> if it doesn't. They're unreachable and if yousicceed in contacting the 
> they won't reply.
> 
> So, I've given up on them and I'm back with a new account. Just im time 
> to wish you alle the best for the new year.
>
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: [mailop] Gmail now deferring email which meets their published reqs

[Simon Wilson via mailop]

I've added a gmail.com-specific transport, with a recipient_limit set to 2 (so 
it does not become per-recipient instead of per-domain), a concurrency limit of 
1 and a 10s rate delay. For the amount of email we send this should not be 
problematic. I'll see if we can then build up a better rep for his domain.

Some good comments here from everyone - thanks all.

Simon



On Sunday, December 31, 2023 07:30 AEST, Michael Orlitzky via mailop 
 wrote:
 On Sat, 2023-12-30 at 12:48 -0800, Randolf Richardson, Postmaster via
mailop wrote:
> If that's what the problem is, then that can easily be set with the
> following Postfix setting without the need for customization scripts:
>
> default_destination_recipient_limit = 1
>
> It may also be helpful to adjust the delivery rate, which can also
> be set in Postfix's "default_destination_rate_delay" setting


This will work, but you probably don't want to make your entire MTA
inefficient just to appease Google. Those two parameters have per-
transport counterparts,

* _destination_concurrency_limit
* _destination_rate_delay

where  is the name of your transport. So, for example, you
could create a transport called "slow", and then set

* slow_destination_concurrency_limit = 1
* slow_destination_rate_delay = 2s

after which all you have to do is configure postfix to send to gmail
via the "slow" transport instead of the default one. Now gmail is slow,
but nobody else suffers.

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
-- 
Simon Wilson
M: 0400 121 116
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[jira] [Commented] (IGNITE-21170) Partition divergence on instable topology in replicated cahce

[Raymond Wilson (Jira)]

[ 
https://issues.apache.org/jira/browse/IGNITE-21170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801402#comment-17801402
 ] 

Raymond Wilson commented on IGNITE-21170:
-

Is it possible this issue is triggered by any topology change on the grid, not 
just changes to the nodes which are responsible for the replicated cache?

> Partition divergence on instable topology in replicated cahce
> -
>
> Key: IGNITE-21170
> URL: https://issues.apache.org/jira/browse/IGNITE-21170
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> The rebalancing topology for a replicated cache can be switched earlier on a 
> particular node before all nodes rebalance. If the topology is switched on by 
> the coordinator, it may send a full partition map with the topology, which is 
> not reached.  This finally leads to map invoke operations on a moving 
> partition and then divergence between replicas.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[SOGo] Spam reporting

["Simon Wilson"]

Can this block:

  SOGoMailJunkSettings = {
        vendor = "generic";
        junkEmailAddress = "s...@mydomaininhere.net";
        notJunkEmailAddress = "h...@mydomaininhere.net";
        limit = 10;
  };

Have multiple email addresses set for junkEmailAddress? I.e if I wanted to be 
training my own Bayes database but also sending to DNSWL?

Thanks

-- 
Simon Wilson
M: 0400 121 116

Re: [mailop] Gmail now deferring email which meets their published reqs

[Simon Wilson via mailop]

Thanks all. I'll answer comments here in one email.
I use a single mail host (mail.simonandkate.net) as MX for a range of family 
domains on a fixed/business IP address through a high quality ISP (not a 
variable IP, not in a dial-up block). I've had the same IP address for about 7 
years. It has a good reputation, sends < 1k emails per week, and I monitor 
blocklists. Neither the domain nor the IP are on spamhaus or other BLs. My 
parents' domain is howiesue.net, we've owned it for about 10 years. Its inbound 
MX and outbound SMTP host is mail.simonandkate.net, which has a valid PTR 
associated with the IP address noted above (again, which has been in place for 
many years). 

howiesue.net has a valid hard-fail/reject SPF policy for the IP mail host we 
use, we DKIM sign all outbound messages with a 1024-bit key, and valid DMARC is 
setup. I have the domain in Google Postmaster Tools, but is too low volume to 
generate any data.

I'll have a look at DNSWL.org - thank you Randolf for that suggestion.

The error message from Google is specifically:

421-4.7.28 Gmail has detected an unusual rate of unsolicited mail originating 
from your SPF domain [howiesue.net      35]. To protect our users from spam, 
mail sent from your domain has been temporarily rate limited. For more 
information, go to https://support.google.com/mail/?p=UnsolicitedRateLimitError 
to review our Bulk Email Senders Guidelines

Google search tells me this is NOT the message they use when the IP address is 
the issue, but that they are having some unknown issue with the domain.

I've checked my logs, and the domain is not compromised; he's sent a total of 
10 emails in the last week lol... This one that Gmail have decided to block is 
the first to Gmail this week, but he regularly sends to the people on that 
list. The email contains 15 Gmail recipients, and is still deferred 12 hours 
later. 

I've tested and they accept email from me to individuals on his list from the 
same mail host from my personal domain - reinforcing that we don't have an IP 
rep issue.

Randolf - I've reviewed the Google support doc on deferred email, and there is 
nothing in there that I need to change - we use TLS (with valid certs), have 
valid PTRs and other DNS records, have SPF (with hard fail / reject requested 
for non-authorised IPs) and DKIM, DMARC, and are not sending spam, it's 
personal email not bulk. There is no reason on that page which I can see which 
gives them reason to defer us.

When I follow their troubleshooter, it drops me to the contact form Randolf 
mentions, but I cannot achieve any progress because you *have* to include "To 
help us investigate a message that was rejected or blocked, please provide the 
full headers from a recent message (less than 12 days old)". That header has to 
be from the RECEIVED end, i.e. Gmail - which I cannot do because to do that I'd 
have to actually be able to get an email through from the domain. I tried 
sending log details of the deferral with info on our compliant setup, and the 
"ticket" is auto-closed because it doesn't include the headers they "need".

I think I'm just going to need to tell him to set up a different way to contact 
his friends instead of this list... 

If I've missed something, I'd love to hear it.

Simon


On Saturday, December 30, 2023 20:28 AEST, Eduardo Díaz Comellas via mailop 
 wrote:
  I've seen problems like this because of ISP listing large net locks as 
"dialup" and not supposed to send email directly.

Check spamhaus' PBL:

https://www.spamhaus.org/pbl/

Best regards El 30 de diciembre de 2023 7:40:59 CET, Simon Wilson via mailop 
 escribió:I know, I'm not alone in this... :( I like to 
think that it's still feasible to run one's own email. I have for many years, 
and currently manage about a dozen email domains for family and friends. Most 
of the time all good.  Then today my dad says to me "Why am I getting these 
bounce messages?"  I check, and Gmail are deferring an email he sends every 
week to a group of friends, 20 all up, 15 of them on Gmail, saying his SPF 
domain is a source of unsolicited email (421-4.7.28). Outlook and Hotmail 
accept OK.  This domain is old, not compromised, has SPF, DKIM (1024bit), 
DMARC, all valid. We send using TLS. We have correct PTR. His emails go out 
fully signed and pass checks. We don't send commercial emails, and that domain 
name is low volume and all emails individually written and sent through a 
webmail client, none of it is automated.  Are we wasting time even trying any 
more?  You can't even submit a request to them for help, because they ignore it 
unless you attach valid and current mis-classified headers from within gmail. 
Umm.. how can I do that when they're not accepting the email?  Simon WilsonM: 
0400 121 116
-- 
Simon Wilson
M: 0400 121 116
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[go-cd] Release Announcement - 23.5.0

[Chad Wilson]

Hello everyone,

A new release of GoCD  (23.5.0) is
out.

This release is another relatively minor maintenance release, fixing a
minor UX regression from 23.4.0 when interacting with job console logs
alongside a few other older issues. As always, please remember to take a
backup before upgrading.

To know more about the features and bug fixes in this release, see the release
notes  or head to the downloads page
 to try it. Feedback and ideas are always
welcome - we appreciate the discussion on issues you are having, and how we
can improve things.

Cheers,
Chad & Aravind

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAA1RwH_KHDo7bwSP8ebiygO0ow2D%3D9_Ct2xCb%3DU9kLx2rhcVrg%40mail.gmail.com.

[mailop] Gmail now deferring email which meets their published reqs

[Simon Wilson via mailop]

I know, I'm not alone in this... :(

I like to think that it's still feasible to run one's own email. I have for 
many years, and currently manage about a dozen email domains for family and 
friends. Most of the time all good. 

Then today my dad says to me "Why am I getting these bounce messages?" 

I check, and Gmail are deferring an email he sends every week to a group of 
friends, 20 all up, 15 of them on Gmail, saying his SPF domain is a source of 
unsolicited email (421-4.7.28). Outlook and Hotmail accept OK. 

This domain is old, not compromised, has SPF, DKIM (1024bit), DMARC, all valid. 
We send using TLS. We have correct PTR. His emails go out fully signed and pass 
checks. We don't send commercial emails, and that domain name is low volume and 
all emails individually written and sent through a webmail client, none of it 
is automated. 

Are we wasting time even trying any more? 

You can't even submit a request to them for help, because they ignore it unless 
you attach valid and current mis-classified headers from within gmail. Umm.. 
how can I do that when they're not accepting the email? 

Simon Wilson
M: 0400 121 116___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [nysbirds-l] location given for Townsends Warbler, Queens County NYC -Forest Park- 12/29

[Jennifer Wilson-Pines]

The bird was seen at 2 locations this morning, early by Jeff Ritter and Bob
Pronowich at  40.704486, -73.847447 along the bridal path, then about 10:30
at the pines along Forest Park Drive. There is easy parking along Myrtle
Ave near the Forest Park Dr bridge, where ther is a stair case up to the
trail head and drive

On Fri, Dec 29, 2023 at 1:20 PM Tom Fiore  wrote:

> Thanks to K. Mirth, a location of the lingering Townsends Warbler in
> Forest Park was - on Friday morning, 12/29 - at and around these
> coordinates-  40.702599, -73.845802  when seen by a small group of
> observers. This warbler may have been present in that park for many weeks
> by now. This sector of Forest Park is to the east of Woodhaven Blvd. -
> which is a major avenue that roughly bisects that park into two large
> sectors.
>
> good birds,
>
> Tom Fiore
> manhattan
>
> --
>
> (copy & paste any URL below, then modify any text "_DOT_" to a period ".")
>
> NYSbirds-L List Info:
> NortheastBirding_DOT_com/NYSbirdsWELCOME_DOT_htm
> NortheastBirding_DOT_com/NYSbirdsRULES_DOT_htm
> NortheastBirding_DOT_com/NYSbirdsSubscribeConfigurationLeave_DOT_htm
>
> ARCHIVES:
> 1) mail-archive_DOT_com/nysbirds-l@cornell_DOT_edu/maillist_DOT_html
> 2) surfbirds_DOT_com/birdingmail/Group/NYSBirds-L
> 3) birding_DOT_aba_DOT_org/maillist/NY01
>
> Please submit your observations to eBird:
> ebird_DOT_org/content/ebird/
>
> --
>
>

-- 
Jennifer Wilson-Pines

--

(copy & paste any URL below, then modify any text "_DOT_" to a period ".")

NYSbirds-L List Info:
NortheastBirding_DOT_com/NYSbirdsWELCOME_DOT_htm
NortheastBirding_DOT_com/NYSbirdsRULES_DOT_htm
NortheastBirding_DOT_com/NYSbirdsSubscribeConfigurationLeave_DOT_htm

ARCHIVES:
1) mail-archive_DOT_com/nysbirds-l@cornell_DOT_edu/maillist_DOT_html
2) surfbirds_DOT_com/birdingmail/Group/NYSBirds-L
3) birding_DOT_aba_DOT_org/maillist/NY01

Please submit your observations to eBird:
ebird_DOT_org/content/ebird/

--

[nysbirds-l] North Nassau Christmas Count

[Jennifer Wilson-Pines]

)
  - American pipit
  - Orange-crowned warbler
  - Pine warbler



Saves by sector number/name

   1. Port Washington - Peregrine falcon, Virginia rail, Marsh wren, Monk
   parakeet, Pine Siskin.
   2. Glenn Cove - Semipalmated plover
   3. Lattingtown - Red breasted nuthatch, Northern gannet, Lesser scaup
   4. Bayville -
   5. Mill Neck - Pink-footed goose
   6. Lloyd Harbor - Ruddy turnstone, Dunlin, Northern harrier, American
   pipit, Savannah sparrow, Snow goose, Common eider, King eider, Eastern
   Meadowlark
   7. Cold Spring Harbor -
   8. Old Brookville - Brown-headed cowbird
   9.
   10. Oyster Bay Cove - Northern Pintail
   11. Muttontown -
   12. Oyster Bay -
   13. Cove Neck - Horned grebe
   14. Woodburry - Orange crowned warbler
   15. Old Westburry/Syosset - Pine warbler, Chipping sparrow, Nashville
   warbler
   16. Feeders - Baltimore oriole



These species were missed 4 or 5 times in the last 10 years, but were seen
in multiple sectors in 2023:

   - Cackling goose (2 sectors), Ring-necked duck (3 sectors), Black scoter
   (3 sectors), Common merganser (3 sectors), Eastern phoebe (3 sectors)



11-year high count, among common species:

   - Green-winged teal (72)
   - Black scoter (45)
   - Common loon (72)
   - Eastern screech-owl (27)
   - Great horned owl (36)
   - Ruby-crowned kinglet (15)
   - Golden-crowned kinglet (41)
   - Winter wren (49)
   - Carolina wren (275)
   - Gray catbird (18)
   - Mockingbird (94)



11-year low count, among common species:

   - Herring gull (641)
   - Great black-backed gull (17)
   - Starling (701)
   - Dark-eyed junco (240)
   - Rusty blackbird (5)


Jennifer Wilson-Pines
Glenn Quinn
Brendan Fogarty
Stephane Perrault

--

(copy & paste any URL below, then modify any text "_DOT_" to a period ".")

NYSbirds-L List Info:
NortheastBirding_DOT_com/NYSbirdsWELCOME_DOT_htm
NortheastBirding_DOT_com/NYSbirdsRULES_DOT_htm
NortheastBirding_DOT_com/NYSbirdsSubscribeConfigurationLeave_DOT_htm

ARCHIVES:
1) mail-archive_DOT_com/nysbirds-l@cornell_DOT_edu/maillist_DOT_html
2) surfbirds_DOT_com/birdingmail/Group/NYSBirds-L
3) birding_DOT_aba_DOT_org/maillist/NY01

Please submit your observations to eBird:
ebird_DOT_org/content/ebird/

--

Re: [EXTERNAL] Need help with performance tuning pg12 on linux

[Wilson, Maria Louise (LARC-E301)[RSES]]

tent,range_date_times,0,beginning_date_time}'::text[]) > 
'2015-10-06T23:59:59+00:00'::text) OR ((properties #>> 
'{temporal_extent,single_date_times,0}

'::text[]) > '2015-10-06T23:59:59+00:00'::text) OR ((properties #>> 
'{temporal_extent,periodic_date_times,0,start_date}'::text[]) > 
'2015-10-06T23:59:59+00:00'::text)) AND (((properties #>> 
'{temporal_extent,range_date_times,0,end_date_time}'::text[]) < '

2015-10-09T00:00:00+00:00'::text) OR ((properties #>> 
'{temporal_extent,single_date_times,0}'::text[]) < 
'2015-10-09T00:00:00+00:00'::text) OR ((properties #>> 
'{temporal_extent,periodic_date_times,0,end_date}'::text[]) < 
'2015-10-09T00:00:00+00:00'::text

)))

   Rows Removed by Filter: 243

   Buffers: shared hit=989

   ->  Index Scan using collection_pkey on collection 
collection_1  (cost=0.28..6.14 rows=1 width=56) (actual time=0.008..0.008 
rows=1 loops=4)

 Index Cond: (id = granule.collection_id)

 Buffers: shared hit=12

 ->  Hash  (cost=1.52..1.52 rows=52 width=16) (actual time=0.045..0.045 
rows=52 loops=1)

   Buckets: 1024  Batches: 1  Memory Usage: 11kB

   Buffers: shared hit=1

   ->  Seq Scan on visibility visibility_1  (cost=0.00..1.52 
rows=52 width=16) (actual time=0.026..0.029 rows=52 loops=1)

 Buffers: shared hit=1

 Planning Time: 7.354 ms

 Execution Time: 64789.927 ms

(52 rows)


From: Ranier Vilela 
Date: Wednesday, December 27, 2023 at 12:23 PM
To: "Wilson, Maria Louise (LARC-E301)[RSES]" 
Cc: Matheus de Oliveira , Frits Hoogland 
, "pgsql-performance@lists.postgresql.org" 

Subject: Re: [EXTERNAL] Need help with performance tuning pg12 on linux

CAUTION: This email originated from outside of NASA.  Please take care when 
clicking links or opening attachments.  Use the "Report Message" button to 
report suspicious messages to the NASA SOC.


Em qua., 27 de dez. de 2023 às 14:11, Wilson, Maria Louise (LARC-E301)[RSES] 
mailto:m.l.wil...@nasa.gov>> escreveu:
Thanks for the reply!!  Having some issues due to nulls….  Any other thoughts?


i=# ALTER TABLE granule_file ADD PRIMARY KEY (granule_uuid, file_id);

ERROR:  column "granule_uuid" contains null values
Well, uuid is a bad datatype for primary keys.
If possible in the long run, consider replacing them with bigint.

Can you try a index:
CREATE INDEX granule_file_file_id_key ON granule_file USING btree(file_id);

Although granule_file has an index as a foreign key, it seems to me that it is 
not being considered.

My 2cents.

Best regards,
Ranier Vilela

Re: [EXTERNAL] Need help with performance tuning pg12 on linux

[Wilson, Maria Louise (LARC-E301)[RSES]]

Thanks for the reply!!  Having some issues due to nulls….  Any other thoughts?


i=# ALTER TABLE granule_file ADD PRIMARY KEY (granule_uuid, file_id);

ERROR:  column "granule_uuid" contains null values


From: Matheus de Oliveira 
Date: Wednesday, December 27, 2023 at 11:36 AM
To: "Wilson, Maria Louise (LARC-E301)[RSES]" 
Cc: Frits Hoogland , 
"pgsql-performance@lists.postgresql.org" 

Subject: Re: [EXTERNAL] Need help with performance tuning pg12 on linux

CAUTION: This email originated from outside of NASA.  Please take care when 
clicking links or opening attachments.  Use the "Report Message" button to 
report suspicious messages to the NASA SOC.


   ->  Hash Join  (cost=644250.54..10734700.30 rows=22333224 
width=223) (actual time=7864.023..44546.392 rows=22325462 loops=1)
 Hash Cond: (file_1.id<http://file_1.id/> = 
granule_file_1.file_id)
 Buffers: shared hit=780882 read=8345236
 ->  Seq Scan on file file_1  (cost=0.00..9205050.88 
rows=2206 width=207) (actual time=402.706..25222.525 rows=22057988 loops=1)
   Buffers: shared hit=639126 read=8345236
 ->  Hash  (cost=365085.24..365085.24 rows=22333224 
width=20) (actual time=7288.228..7288.235 rows=22325462 loops=1)
   Buckets: 33554432  Batches: 1  Memory Usage: 
1391822kB
   Buffers: shared hit=141753
   ->  Seq Scan on granule_file granule_file_1  
(cost=0.00..365085.24 rows=22333224 width=20) (actual time=0.030..2151.380 
rows=22325462 loops=1)
 Buffers: shared hit=141753

This part above is the most expensive so far, and taking a look at your 
`granule_file` table on the first message, it has no indexes nor constraints, 
which certainly looks like a mistake. I'd start optimizing this, you could add 
an index on it, but seems that you need a primary key on both columns of this 
(junction?) table:

ALTER TABLE granule_file ADD PRIMARY KEY (granule_uuid, file_id);

There are certainly more things to optimize on this query, but I prefer doing 
one thing at a time. Could you try with the PK and send the EXPLAIN ANALYZE of 
the query again after that?

Best regards,
Matheus de Oliveira

Re: [Frameworks] Peter Herwitz Contact Information

[Brian Wilson]

I’m sorry to hear of Peter’s passing as well. I never had the chance to meet him, but saw his films twenty years ago as a student. They were poetic and lovely and have stayed in my memory all these years since. Best,Brian WilsonSent from my iPhoneOn Dec 26, 2023, at 5:59 PM, Stephen Anker  wrote:Hi Paul,I'm sorry to say that Peter passed away last September after a protracted illness.To the best of my knowledge, his films aren't available at this time, although someone else on Frameworks might know otherwise.Peter was a profoundly gifted artist and human being, and his absence is being felt by all of us who knew him.I hope that his remarkable, uniquely textured poetical films will resurface soon for all of us to enjoy.My best, Steve AnkerOn Tue, Dec 26, 2023 at 11:30 AM Paul Attard  wrote:Hey hey Frameworks,Hope you're all doing well today! And I hope this message finds you all in good spirits. I'm reaching out today in the hopes that some of you may have information or leads regarding the contact details of experimental filmmaker Peter Herwitz. I've been unable to find contact information for him and have wanted to reach out for some time now regarding his 8mm films. If any members of this forum have insights into how I might be able to reach out to Mr. Herwitz, or if you have any suggestions on where I could find such information, I would be immensely grateful for your assistance. I understand the importance of privacy, so please feel free to share any information privately if that is more comfortable for you. Thank you all for your time and consideration. I look forward to any guidance or assistance you can provide.Best regards,Paul
-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org

-- Frameworks mailing listFrameworks@film-gallery.orghttps://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org

Need help with performance tuning pg12 on linux

[Wilson, Maria Louise (LARC-E301)[RSES]]

Foreign-key constraints:

"collection_processing_level_id_fkey" FOREIGN KEY (processing_level_id) 
REFERENCES processing_level(id)

"collection_project_id_fkey" FOREIGN KEY (project_id) REFERENCES project(id)

"collection_visibility_id_fkey" FOREIGN KEY (visibility_id) REFERENCES 
visibility(id)

Referenced by:

TABLE "collection_organization" CONSTRAINT 
"collection_organization_collection_id_fkey" FOREIGN KEY (collection_id) 
REFERENCES collection(id)

TABLE "collection_science_keyword" CONSTRAINT 
"collection_science_keyword_collection_id_fkey" FOREIGN KEY (collection_id) 
REFERENCES collection(id)

TABLE "collection_spatial_processing_hint" CONSTRAINT 
"collection_spatial_processing_hint_collection_id_fkey" FOREIGN KEY 
(collection_id) REFERENCES collection(id)

TABLE "granule" CONSTRAINT "granule_collection_id_fkey" FOREIGN KEY 
(collection_id) REFERENCES collection(id)

TABLE "granule_temporal_range" CONSTRAINT 
"granule_temporal_range_collection_id_fkey" FOREIGN KEY (collection_id) 
REFERENCES collection(id)


Granule_file:

 public | granule_file   | table | ims_api_writer | 1108 MB 
|


\d granule_file

   Table "public.granule_file"

Column|  Type   | Collation | Nullable | Default

--+-+---+--+-

 granule_uuid | uuid|   |  |

 file_id  | integer |   |  |

Foreign-key constraints:

"granule_file_file_id_fkey" FOREIGN KEY (file_id) REFERENCES file(id)

"granule_file_granule_uuid_fkey" FOREIGN KEY (granule_uuid) REFERENCES 
granule(uuid)



Visibility:

public | visibility | table | ims_api_writer | 40 kB   |


\d visibility

   Table "public.visibility"

 Column | Type  | Collation | Nullable |Default

+---+---+--+

 id | integer   |   | not null | 
nextval('visibility_id_seq'::regclass)

 name   | character varying(80) |   | not null |

 value  | integer   |   | not null |

Indexes:

"visibility_pkey" PRIMARY KEY, btree (id)

"visibility_name_key" UNIQUE CONSTRAINT, btree (name)

"visibility_value_key" UNIQUE CONSTRAINT, btree (value)

Referenced by:

TABLE "collection" CONSTRAINT "collection_visibility_id_fkey" FOREIGN KEY 
(visibility_id) REFERENCES visibility(id)

TABLE "granule" CONSTRAINT "granule_visibility_id_fkey" FOREIGN KEY 
(visibility_id) REFERENCES visibility(id)









Thanks for the help!



Maria Wilson

Nasa/Langley Research Center

Hampton, Virginia USA

m.l.wil...@nasa.gov

[Wikiapiary] Re: Wikiapiary maintenance

[Sam Wilson]

I'm not really sure if Cargo is the right option, but it's the simplest 
alternative I know of to SMW.


Perhaps categories would suffice, if the important stats can be 
expressed just as category counts. It sounds like it could get annoying 
though.


I do feel a bit like we'd be missing a win if, for the query-able data 
in a site about MediaWikis, we were forced to build a custom extension 
for doing the querying. It's the sort of thing that lots of wikis want 
to do! But maybe it's the best way to go.



On 27/12/23 17:16, Jesús Martínez wrote:

Hi,

Sam proposes switching to Cargo. However, from what I've heard (and I
haven't used Cargo myself), Cargo is another beast and comes with its
own problems as well. Someone with more experience with Cargo should
probably assess whether it would be a good idea or not to use Cargo
here. Maybe there's a way to do roughly the same queries by using
categories instead, and the help of one of the available
DynamicPageList extensions.

Best regards,

--
Jesús Martínez
Ciencia Al Poder

El mié, 27 dic 2023 a las 2:29, Sam Wilson () escribió:

My understanding is that the basic structure of Wikiapiary is firstly a
system of templates etc that stores data from the sites' pages into SMW
and then reads it out for various reports; and secondly the scripts that
populate the wikitext pages with data fetched from the sites (and
extensions etc). The really valuable bits to me are the fact of having a
categorized/tagged index to MediaWiki sites, and the extension
popularity info. The first part of that is most valuable as a
human-curated thing, so I think that'd make sense to get back online
even if it wasn't bot-updated. The extension and other site info is
silly to update by hand, but there isn't an absolute reason that the
bots doing the updating need to be part of the WikiApiary
infrastructure, so perhaps if WikiApiary was online, a new system of
fetching site info could be built.

Then, of course, is the separate issue of *how* to store the info on the
wiki. It's SMW at the moment, but it sounds like that hits some resource
issues given the number of queries being run and the amount of data.
Would Cargo be better? I feel like switching to that would be not an
insurmountable thing to do (compared to say moving to Wikibase to store
the data, which would be a bigger restructure). The individual sites'
pages mightn't even need to be changed (if all the storage/querying
logic is in templates and modules).

I vote for bringing it online again now, even if it's without SMW or the
bots, and updating it to the latest MediaWiki. If any of that's possible
of course.

Thank you for working on it! I'm not sure how much time I've got to
help, but I'd love to try.

—Sam


On 27/12/23 08:47, Mark A. Hershberger wrote:

Triple Camera  writes:


The database has been locked for half a year, Bots and editors are
waiting, and they are losing patience. I believe the most urgent thing
to do is to make WikiApiary back online as soon as possible.

If we brought WikiApiary back online right now without the bots, would
that be acceptable?

I'm trying to understand what you need from the site and how you've used
it, so any information you have would be useful.

If you or other users of the site can let us know how you would like to
use it, that well help us make sure we are able bring it back online in
as useful a way as possible.

Mark.


___
Wikiapiary mailing list -- wikiapiary@lists.wikimedia.org
To unsubscribe send an email to wikiapiary-le...@lists.wikimedia.org

___
Wikiapiary mailing list -- wikiapiary@lists.wikimedia.org
To unsubscribe send an email to wikiapiary-le...@lists.wikimedia.org

___
Wikiapiary mailing list -- wikiapiary@lists.wikimedia.org
To unsubscribe send an email to wikiapiary-le...@lists.wikimedia.org

[Wikiapiary] Re: Wikiapiary maintenance

[Sam Wilson]

My understanding is that the basic structure of Wikiapiary is firstly a 
system of templates etc that stores data from the sites' pages into SMW 
and then reads it out for various reports; and secondly the scripts that 
populate the wikitext pages with data fetched from the sites (and 
extensions etc). The really valuable bits to me are the fact of having a 
categorized/tagged index to MediaWiki sites, and the extension 
popularity info. The first part of that is most valuable as a 
human-curated thing, so I think that'd make sense to get back online 
even if it wasn't bot-updated. The extension and other site info is 
silly to update by hand, but there isn't an absolute reason that the 
bots doing the updating need to be part of the WikiApiary 
infrastructure, so perhaps if WikiApiary was online, a new system of 
fetching site info could be built.


Then, of course, is the separate issue of *how* to store the info on the 
wiki. It's SMW at the moment, but it sounds like that hits some resource 
issues given the number of queries being run and the amount of data. 
Would Cargo be better? I feel like switching to that would be not an 
insurmountable thing to do (compared to say moving to Wikibase to store 
the data, which would be a bigger restructure). The individual sites' 
pages mightn't even need to be changed (if all the storage/querying 
logic is in templates and modules).


I vote for bringing it online again now, even if it's without SMW or the 
bots, and updating it to the latest MediaWiki. If any of that's possible 
of course.


Thank you for working on it! I'm not sure how much time I've got to 
help, but I'd love to try.


—Sam


On 27/12/23 08:47, Mark A. Hershberger wrote:

Triple Camera  writes:


The database has been locked for half a year, Bots and editors are
waiting, and they are losing patience. I believe the most urgent thing
to do is to make WikiApiary back online as soon as possible.

If we brought WikiApiary back online right now without the bots, would
that be acceptable?

I'm trying to understand what you need from the site and how you've used
it, so any information you have would be useful.

If you or other users of the site can let us know how you would like to
use it, that well help us make sure we are able bring it back online in
as useful a way as possible.

Mark.


___
Wikiapiary mailing list -- wikiapiary@lists.wikimedia.org
To unsubscribe send an email to wikiapiary-le...@lists.wikimedia.org

[packer] Prodentim Reviews: Nurturing Healthy Smiles Every Day! {Consumer Warnings}

[Lyan Wilson]

*Click Here to Visit The Official Website Now* 

*Is The Use of ProDentim Safe?*

Each constituent of GMP-certified ProDentim has undergone scientific 
sanction and a third-party laboratory test. In addition, it has received 
authorization from an authorized official in the United States. This item 
has undergone numerous inspections and certifications in order to become 
one of the most exceptional oral gummies of our time. It operates with 
greater efficacy than any other product currently available in the market.

*Click Here to Visit The Official Website Now* 

*The cost of ProDentim*

ProDentim is a product that can be purchased exclusively through its 
official website. A hyperlink has been furnished herewith to facilitate 
your direct access to the authentic page.

• One 30-day supply of ProDentim per bottle costs $69

• Three bottles of 90-day supply ProDentim for $59 each

• Six bottles of 180-day supply ProDentim, each priced at $49

*In summary,*

ProDentim is the most economical and natural method for maintaining robust 
teeth and oral hygiene, in addition to being the simplest and most natural 
option. You need only consume two gummies daily, and you are not required 
to cleanse your teeth in the restroom at all times. At least once, you 
should attempt this exceptional product in order to achieve lustrous, 
beautiful teeth.

 The editorial and news departments of the Daily Democrat were not involved 
in the preparation of this article. This paid advertisement does not 
necessarily reflect the Daily Democrat, its employees, or subsidiaries' 
official policy or position.

*Click Here to Visit The Official Website Now* 

*The workings of ProDentim*

ProDentim is formulated with a variety of natural, tooth-beneficial 
constituents, including probiotics, protein, calcium, and others. 
Frequently, when we brush, we neglect to devote sufficient time and employ 
improper brushing technique. In addition, frequent snacking, particularly 
of sugary foods, causes severe damage to the interdental spaces of the 
teeth. Deposition of these minute particles in the interdental spaces and 
gums is a significant contributor to dental caries, tooth decay, poor 
breath, and other associated issues. As soon as we begin to chew ProDentim, 
its vital nutrients burst into our mouths and permeate every crevice of the 
mouth, delivering every last one of them. It rejuvenates oral health and 
imparts lustrous, robust, and aesthetically pleasing teeth.

Composition of the ProDentim Probiotic: Supplementary components of 
ProDentim include Lactobacillus reuteri, a vital microorganism that is 
commonly present in saliva and is crucial for the process of food 
digestion. It is a beneficial bacteria for the buccal cavity. Its depletion 
occurs with age, which is why it is utilized in this instance to prevent 
tooth caries and foul odor.

Omega-3 fatty acids are critical for maintaining healthy molars. It 
preserves the integrity of our teeth by preventing the deterioration of gum 
musculature. It effectively prevents tooth discomfort.

Folic Acid: Gum inflammation is an extremely prevalent condition among 
individuals. Most individuals experience persistent issues such as itching. 
This extraordinary component safeguards against tooth decay, poor breath, 
gum depletion, and more.

The following contain calcium and vitamins: A variety of calcium and 
vitamins, including a, c, and d, have been incorporated, resulting in 
exceptionally robust teeth. By eliminating harmful bacteria, these 
ingredients extend the life of dentition.

Advantages of ProDentim • It safeguards against plaque accumulation and gum 
depletion; • It imparts pleasant fruit flavors, such as strawberry and 
mint, that promote fresh breath; • It eliminates yellowing and restores 
luster to the teeth; • It fortifies the teeth from the root and protects 
the enamel; • It regulates saliva production to maintain oral hygiene by 
removing food particles; • It reduces tooth sensitivity.

A smile is the most effective means of expressing one's joy, and it can be 
displayed optimally with healthy, natural teeth. The enamel, which is the 
scientific term for the outermost layer of teeth, begins to erode as we 
accumulate age. When gums begin to deteriorate, problems such as tooth 
decay and cavities become extremely common. Have you ever observed that the 
majority of models and celebrities in advertisements are enticing due to 
their flawless teeth and attractive smiles? Is there any action that can be 
taken to safeguard one's smile and prevent the occurrence of dental 
problems such as inflammation, decay, bleeding, bad odor, redness, and 
itching? ProDentim is an exceptional gummy supplement that promotes oral 
health in general. This product addresses all oral health concerns with its 
all-natural and herbal constituents. It guarantees pristine skin by 
eliminating bacteria and addressing 

[packer] Prodentim Reviews: Elevating Your Dental Routine! Safe Supplement & Benefits?

[Lyan Wilson]

*Click Here to Visit The Official Website Now* 

*The workings of ProDentim*

ProDentim is formulated with a variety of natural, tooth-beneficial 
constituents, including probiotics, protein, calcium, and others. 
Frequently, when we brush, we neglect to devote sufficient time and employ 
improper brushing technique. In addition, frequent snacking, particularly 
of sugary foods, causes severe damage to the interdental spaces of the 
teeth. Deposition of these minute particles in the interdental spaces and 
gums is a significant contributor to dental caries, tooth decay, poor 
breath, and other associated issues. As soon as we begin to chew ProDentim, 
its vital nutrients burst into our mouths and permeate every crevice of the 
mouth, delivering every last one of them. It rejuvenates oral health and 
imparts lustrous, robust, and aesthetically pleasing teeth.

Composition of the ProDentim Probiotic: Supplementary components of 
ProDentim include Lactobacillus reuteri, a vital microorganism that is 
commonly present in saliva and is crucial for the process of food 
digestion. It is a beneficial bacteria for the buccal cavity. Its depletion 
occurs with age, which is why it is utilized in this instance to prevent 
tooth caries and foul odor.

Omega-3 fatty acids are critical for maintaining healthy molars. It 
preserves the integrity of our teeth by preventing the deterioration of gum 
musculature. It effectively prevents tooth discomfort.

Folic Acid: Gum inflammation is an extremely prevalent condition among 
individuals. Most individuals experience persistent issues such as itching. 
This extraordinary component safeguards against tooth decay, poor breath, 
gum depletion, and more.

The following contain calcium and vitamins: A variety of calcium and 
vitamins, including a, c, and d, have been incorporated, resulting in 
exceptionally robust teeth. By eliminating harmful bacteria, these 
ingredients extend the life of dentition.

Advantages of ProDentim • It safeguards against plaque accumulation and gum 
depletion; • It imparts pleasant fruit flavors, such as strawberry and 
mint, that promote fresh breath; • It eliminates yellowing and restores 
luster to the teeth; • It fortifies the teeth from the root and protects 
the enamel; • It regulates saliva production to maintain oral hygiene by 
removing food particles; • It reduces tooth sensitivity.

A smile is the most effective means of expressing one's joy, and it can be 
displayed optimally with healthy, natural teeth. The enamel, which is the 
scientific term for the outermost layer of teeth, begins to erode as we 
accumulate age. When gums begin to deteriorate, problems such as tooth 
decay and cavities become extremely common. Have you ever observed that the 
majority of models and celebrities in advertisements are enticing due to 
their flawless teeth and attractive smiles? Is there any action that can be 
taken to safeguard one's smile and prevent the occurrence of dental 
problems such as inflammation, decay, bleeding, bad odor, redness, and 
itching? ProDentim is an exceptional gummy supplement that promotes oral 
health in general. This product addresses all oral health concerns with its 
all-natural and herbal constituents. It guarantees pristine skin by 
eliminating bacteria and addressing dental concerns that may be affecting 
you.

*Aspects concerning ProDentim*

Gum disease and cavities affect individuals beyond the pediatric 
population. Each dentist recommends that patients clean their teeth twice 
daily. Avoid consuming saccharine foods and ensure that your mouth is 
thoroughly cleaned, especially after consuming such items, as they promote 
the development of cavities. However, it is a fact that the majority of 
individuals do not practice proper oral hygiene; as a result, hemorrhaging, 
foul odors, and discomfort in the gums are extremely common.

By utilizing natural ingredients and practicing good oral hygiene, which 
eliminates these harmful microorganisms from the mouth, it is possible to 
completely eliminate these issues. ProDentim is formulated with various 
components, including coenzymes, probiotics, and sodium chloride, which are 
designed to eliminate the detrimental bacteria that are accountable for 
tooth erosion and other associated complications.

However, you will not encounter any complications such as parched mouth, 
unpleasant taste, or anything similar. ProDentim is produced utilizing 
natural flavorings and ingredients, including mint and strawberry essence. 
Therefore, it is palatable, and simply by consuming these gummies, you will 
effectively eradicate numerous oral health concerns, such as bad odor.

*Click Here to Visit The Official Website Now* 

*Is The Use of ProDentim Safe?*

Each constituent of GMP-certified ProDentim has undergone scientific 
sanction and a third-party laboratory test. In addition, it has received 
authorization from an authorized 

[packer] PRODENTIM - [IS FAKE or REAL?] Read About 100% Natural Benefits For Teeth?

[Lyan Wilson]

*➲➲➲ Deals LIVE➲➲➲CHECK IT NOW ➲➲➲ Click Here To Order Now 
* 

A smile is the most effective means of expressing one's joy, and it can be 
displayed optimally with healthy, natural teeth. The enamel, which is the 
scientific term for the outermost layer of teeth, begins to erode as we 
accumulate age. When gums begin to deteriorate, problems such as tooth 
decay and cavities become extremely common. Have you ever observed that the 
majority of models and celebrities in advertisements are enticing due to 
their flawless teeth and attractive smiles? Is there any action that can be 
taken to safeguard one's smile and prevent the occurrence of dental 
problems such as inflammation, decay, bleeding, bad odor, redness, and 
itching? ProDentim is an exceptional gummy supplement that promotes oral 
health in general. This product addresses all oral health concerns with its 
all-natural and herbal constituents. It guarantees pristine skin by 
eliminating bacteria and addressing dental concerns that may be affecting 
you.

*Aspects concerning ProDentim*

Gum disease and cavities affect individuals beyond the pediatric 
population. Each dentist recommends that patients clean their teeth twice 
daily. Avoid consuming saccharine foods and ensure that your mouth is 
thoroughly cleaned, especially after consuming such items, as they promote 
the development of cavities. However, it is a fact that the majority of 
individuals do not practice proper oral hygiene; as a result, hemorrhaging, 
foul odors, and discomfort in the gums are extremely common.

By utilizing natural ingredients and practicing good oral hygiene, which 
eliminates these harmful microorganisms from the mouth, it is possible to 
completely eliminate these issues. ProDentim is formulated with various 
components, including coenzymes, probiotics, and sodium chloride, which are 
designed to eliminate the detrimental bacteria that are accountable for 
tooth erosion and other associated complications.

However, you will not encounter any complications such as parched mouth, 
unpleasant taste, or anything similar. ProDentim is produced utilizing 
natural flavorings and ingredients, including mint and strawberry essence. 
Therefore, it is palatable, and simply by consuming these gummies, you will 
effectively eradicate numerous oral health concerns, such as bad odor.

*➲➲➲ Deals LIVE➲➲➲CHECK IT NOW ➲➲➲ Click Here To Order Now 
* 

*The workings of ProDentim*

ProDentim is formulated with a variety of natural, tooth-beneficial 
constituents, including probiotics, protein, calcium, and others. 
Frequently, when we brush, we neglect to devote sufficient time and employ 
improper brushing technique. In addition, frequent snacking, particularly 
of sugary foods, causes severe damage to the interdental spaces of the 
teeth. Deposition of these minute particles in the interdental spaces and 
gums is a significant contributor to dental caries, tooth decay, poor 
breath, and other associated issues. As soon as we begin to chew ProDentim, 
its vital nutrients burst into our mouths and permeate every crevice of the 
mouth, delivering every last one of them. It rejuvenates oral health and 
imparts lustrous, robust, and aesthetically pleasing teeth.

Composition of the ProDentim Probiotic: Supplementary components of 
ProDentim include Lactobacillus reuteri, a vital microorganism that is 
commonly present in saliva and is crucial for the process of food 
digestion. It is a beneficial bacteria for the buccal cavity. Its depletion 
occurs with age, which is why it is utilized in this instance to prevent 
tooth caries and foul odor.

Omega-3 fatty acids are critical for maintaining healthy molars. It 
preserves the integrity of our teeth by preventing the deterioration of gum 
musculature. It effectively prevents tooth discomfort.

Folic Acid: Gum inflammation is an extremely prevalent condition among 
individuals. Most individuals experience persistent issues such as itching. 
This extraordinary component safeguards against tooth decay, poor breath, 
gum depletion, and more.

The following contain calcium and vitamins: A variety of calcium and 
vitamins, including a, c, and d, have been incorporated, resulting in 
exceptionally robust teeth. By eliminating harmful bacteria, these 
ingredients extend the life of dentition.

Advantages of ProDentim • It safeguards against plaque accumulation and gum 
depletion; • It imparts pleasant fruit flavors, such as strawberry and 
mint, that promote fresh breath; • It eliminates yellowing and restores 
luster to the teeth; • It fortifies the teeth from the root and protects 
the enamel; • It regulates saliva production to maintain oral hygiene by 
removing food particles; • It reduces tooth sensitivity.

*Is The Use of ProDentim Safe?*

Each constituent of GMP-certified ProDentim has undergone scientific 
sanction and a third-party laboratory test. In addition, it has received 

Re: Audit Reminder Email Summary - Intermediate Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of December 2023 Outdated Audit Statements for 
Intermediate Certs
Date: Tue, 19 Dec 2023 13:00:24 + (GMT)

CA Owner: Government of The Netherlands, PKIoverheid (Logius)
   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Services 
CA - 2023
SHA-256 Fingerprint: 
6E25C0044C7EBB30D01A4CC3D5733D734D06CD296A6823E63527F4182D528351
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Burger CA - 2023
SHA-256 Fingerprint: 
66388EE649CBE920FD949FA9B77E2AA45B5DEC4120B8FFAB371B0C9C5E38C1C1
Standard Audit Period End Date (mm/dd/): 05/31/2022

   - Certificate Name: DigiCert QuoVadis PKIoverheid Organisatie Persoon CA 
- 2023
SHA-256 Fingerprint: 
C8C77ECF368D73214D50D88384464339E6F8E59F34B47E39E7965F4E5787CF1D
Standard Audit Period End Date (mm/dd/): 05/31/2022


Mozilla Comment: https://bugzilla.mozilla.org/show_bug.cgi?id=1843265




-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/d82ae117-a29b-4828-9bb1-6370eef54e00n%40mozilla.org.

Re: Audit Reminder Email Summary - Root Certificates

[Kathleen Wilson]

 Forwarded Message 
Subject: Summary of December 2023 Audit Reminder Emails
Date: Tue, 19 Dec 2023 13:00:35 + (GMT)

Mozilla: Audit Reminder
CA Owner: Buypass
Root Certificates:
   Buypass Class 3 Root CA
   Buypass Class 2 Root CA
Standard Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
Standard Audit Period End Date: 2022-10-31
Standard Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_018.pdf
Standard Audit Period End Date: 2022-10-31
BR Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
BR Audit Period End Date: 2022-10-31
BR Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_018.pdf
BR Audit Period End Date: 2022-10-31
EV Audit: 
https://verifeyedirectoryprod.blob.core.windows.net/pas7000docs/buypas-0047417148-000/ecertificate_-_ets_053.pdf
EV Audit Period End Date: 2022-10-31
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Cybertrust Japan / JCSI
Root Certificates:
   SecureSign RootCA11
Standard Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=861a269b-8367-46fd-a227-b72800a41ad7
Standard Audit Period End Date: 2022-10-15
BR Audit: 
https://www.cpacanada.ca/GenericHandlers/CPACHandler.ashx?AttachmentID=4657c08b-4914-40ef-b905-4f21bca93b95
BR Audit Period End Date: 2022-10-15
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Izenpe S.A.
Root Certificates:
   Izenpe.com
Standard Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/AENOR-AAL_PSC2024-2022-IZENPE-v0.3.pdf
Standard Audit Period End Date: 2022-10-30
BR Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/AENOR-AAL_PSC2024-2022-IZENPE-v0.3.pdf
BR Audit Period End Date: 2022-10-30
EV Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/AENOR-AAL_PSC2024-2022-IZENPE-v0.3.pdf
EV Audit Period End Date: 2022-10-30
CA Comments: null



Mozilla: Audit Reminder
CA Owner: Viking Cloud, Inc.
Root Certificates:
   Trustwave Global ECC P256 Certification Authority
   Trustwave Global Certification Authority
   Trustwave Global ECC P384 Certification Authority
   Secure Global CA
   SecureTrust CA
   XRamp Global Certification Authority
Standard Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=8137867c-0799-43ef-bb97-5ef63a190001
Standard Audit Period End Date: 2022-09-30
BR Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=2b3dc01c-221d-40ed-abea-1c3d8145254f
BR Audit Period End Date: 2022-09-30
EV Audit: 
https://www.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=e3b67377-1419-46b9-b9ea-bc3849bf7ef6
EV Audit Period End Date: 2022-09-30
CA Comments: Changed CA Name from Trustwave to SecureTrust on February 1, 
2019.



Mozilla: Audit Reminder
CA Owner: D-Trust
Root Certificates:
   D-TRUST Root Class 3 CA 2 2009**
   D-TRUST Root Class 3 CA 2 EV 2009**
   D-TRUST Root CA 3 2013**
   D-TRUST EV Root CA 1 2020**
   D-TRUST BR Root CA 1 2020**

** Audit Case in the Common CA Database is under review for this root 
certificate.

Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121604_D-TRUST_Root_Class_3_CA_2_2009.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121605_D-TRUST_Root_Class_3_CA_2_EV_2009.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/en/AA2022121603_D-TRUST_Root_CA_3_2013.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121602_D-TRUST_EV_Root_CA_1_2020.pdf
Standard Audit Period End Date: 2022-10-07
Standard Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121601_D-TRUST_BR_Root_CA_1_2020.pdf
Standard Audit Period End Date: 2022-10-07
BR Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121604_D-TRUST_Root_Class_3_CA_2_2009.pdf
BR Audit Period End Date: 2022-10-07
BR Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121605_D-TRUST_Root_Class_3_CA_2_EV_2009.pdf
BR Audit Period End Date: 2022-10-07
BR Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/en/AA2022121603_D-TRUST_Root_CA_3_2013.pdf
BR Audit Period End Date: 2022-10-07
BR Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121602_D-TRUST_EV_Root_CA_1_2020.pdf
BR Audit Period End Date: 2022-10-07
BR Audit: 
https://www.tuvit.de/fileadmin/Content/TUV_IT/zertifikate/de/AA2022121601_D-TRUST_BR_Root_CA_1_2020.pdf
BR Audit Period End Date: 2022-10-07
EV Audit: 

[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent

[Sam Wilson]

https://bugs.kde.org/show_bug.cgi?id=477817

--- Comment #1 from Sam Wilson  ---
This would be great!

Especially as the username and password used should not be one's normal
password, but a bot password, and so is often more laborious to use.

https://www.mediawiki.org/wiki/Manual:Bot_passwords

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent

[Sam Wilson]

https://bugs.kde.org/show_bug.cgi?id=477817

Sam Wilson  changed:

   What|Removed |Added

 CC||s...@samwilson.id.au

-- 
You are receiving this mail because:
You are watching all bug changes.

D-Trust Inclusion Request (Email Trust Bit)

[Ben Wilson]

 All,

Public discussion concluded last Friday, Dec. 15, on the CCADB Public List,
for D-Trust's root inclusion request.
https://groups.google.com/a/ccadb.org/g/public/c/EPVczE_6oCc/m/jsZ0CsgdAAAJ

This is notice that I am recommending approval of D-Trust's request to
include the following root CA certificates in NSS with the email trust bit
enabled:

D-Trust SBR Root CA 1 2022.cer
   (CA Repository
, crt.sh

)
D-Trust SBR Root CA 2 2022.cer
(CA Repository
, crt.sh

)

This begins a 7-day “last call” period for any final objections.

Thanks,

Ben

-- 
You received this message because you are subscribed to the Google Groups 
"dev-security-policy@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dev-security-policy+unsubscr...@mozilla.org.
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/CA%2B1gtabh4uTWn%3DMoNF%2BBNz%2BzgghcBEEEz2U%3DHw6GwmX%2BXwab%3Dw%40mail.gmail.com.

Re: Public Discussion of D-Trust CA Inclusion Request

[Ben Wilson]

All,

On November 3, 2023, we began a six-week, public discussion[1] on the
following root CA certificates issued by D-Trust:

   1.

   D-Trust SBR Root CA 1 2022:
   -

  384-bit ECC
  -

  Certificate download links: (CA Repository
  <http://www.d-trust.net/cgi-bin/D-Trust_SBR_Root_CA_1_2022.crt>,
  crt.sh
  
<https://crt.sh/?sha256=D92C171F5CF890BA428019292927FE22F3207FD2B54449CB6F675AF4922146E2>
  )
  -

  Use cases served/EKUs:
  -

 Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
 -

 Client Authentication 1.3.6.1.5.5.7.3.2
 -

 Document Signing AATL 1.2.840.113583.1.1.5
 -

 Document Signing MS 1.3.6.1.4.1.311.10.3.12



   1.

   D-Trust SBR Root CA 2 2022:
   -

  4096-bit RSA
  -

  Certificate download links: (CA Repository
  <http://www.d-trust.net/cgi-bin/D-Trust_SBR_Root_CA_2_2022.crt>,
  crt.sh
  
<https://crt.sh/?sha256=DBA84DD7EF622D485463A90137EA4D574DF8550928F6AFA03B4D8B1141E636CC>
  )
  -

  Use cases served/EKUs:
  -

 Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
 -

 Client Authentication 1.3.6.1.5.5.7.3.2
 -

 Document Signing AATL 1.2.840.113583.1.1.5
 -

 Document Signing MS 1.3.6.1.4.1.311.10.3.12

The public discussion period ended last Friday, December 15, 2023.

We did not receive any objections or other questions or comments in
opposition to D-Trust’s request. We thank the community for its review and
consideration during this period. Root Store Programs will make final
inclusion decisions independently, on their own timelines, and based on
each Root Store Member’s inclusion criteria. Further discussion may take
place in the independently managed Root Store community forums (e.g. MDSP).

Thanks,

Ben Wilson

On behalf of the CCADB Steering Committee
[1]
https://groups.google.com/a/ccadb.org/g/public/c/EPVczE_6oCc/m/s90nO9-EBAAJ

On Fri, Dec 8, 2023 at 10:52 AM Ben Wilson  wrote:

> Greetings,
>
> This is a reminder that the public discussion period on the inclusion
> application of D-Trust will close next Friday, December 15, 2023.
>
> Thank you,
> Ben Wilson, on behalf of the CCADB Steering Committee
>
> On Mon, Nov 6, 2023 at 10:02 AM Ben Wilson  wrote:
>
>> All,
>>
>> Regarding the D-Trust Certification Practice Statement—instead of
>> referencing the D-Trust Root PKI CPS, it should have referenced the CPS of
>> the D-Trust CSM PKI, v.4.0, valid from 28-September-2023 (
>> https://www.d-trust.net/internet/files/D-TRUST_CSM_PKI_CPS.pdf) (from 19
>> July 2023, the CSM PKI CPS applies to certificates with policy levels
>> QEVCP-w, QNCP-w, EVCP, OVCP and LCP).
>>
>> Also, it didn’t mention the following Bugzilla bugs opened in the past 24
>> months:
>>
>> 1756122 <https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>
>>
>> D-TRUST: Wrong key usage (Key Agreement)
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>
>>
>> RESOLVED
>>
>> [dv-misissuance]
>>
>> 1793440 <https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>
>>
>> D-TRUST: CRL not DER-encoded
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>
>>
>> RESOLVED
>>
>> [crl-failure]
>>
>> 1861069 <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>
>>
>> D-Trust: Issuance of 15 DV certificates containing ‘serialNumber’ field
>> within subject <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>
>>
>> OPEN
>>
>> [dv-misissuance]
>>
>> 1862082 <https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>
>>
>> D-Trust: Delay beyond 5 days in revoking misissued certificate
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>
>>
>> OPEN
>>
>> [leaf-revocation-delay]
>>
>>
>>
>> Ben
>>
>> On Fri, Nov 3, 2023 at 9:39 AM Ben Wilson  wrote:
>>
>>> All,
>>>
>>> This email commences a six-week public discussion of D-Trust’s request
>>> to include the following CA certificates as publicly trusted root
>>> certificates in one or more CCADB Root Store Member’s program. This
>>> discussion period is scheduled to close on December 15, 2023.
>>>
>>> The purpose of this public discussion process is to promote openness and
>>> transparency. However, each Root Store makes its inclusion decisions
>>> independently, on its own timelines, and based on its own inclusion
>>> criteria. Successful completion of this public discussion process does not
>>> guarantee any favorable action by any root store.
>>>
>>>

[African Wikimedians] [Wiki Loves Africa] Annonce des ambassadeurs de Wiki Loves Africa

[Wilson Oluoha]

Chers amis,

Il y a quelques semaines, Wiki in Africa a publié un appel à des
ambassadeurs bénévoles pour Wiki Loves Africa
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors#The_role_-_WLA_Ambassadors>
avec l'objectif général de contribuer à l'initiative Wiki Loves Africa.

Je suis très heureux d'annoncer nos nouveaux ambassadeurs de l'ALE dans
trois catégories linguistiques ;

*French :*


   - Minette Lontsie <https://fr.wikipedia.org/wiki/Utilisatrice:Serieminou>
   - Mermoze Adodo <https://fr.wikipedia.org/wiki/Utilisateur:Adoscam>

* Anglais :*


   - Ogali Hilary <https://meta.wikimedia.org/wiki/User:Ogalihillary>
   - Alvin Ategyeka <https://meta.wikimedia.org/wiki/User:Alvinategyeka>

*L'arabe :*


   - Donia Domiaty
   
<https://ar.wikipedia.org/wiki/%D9%85%D8%B3%D8%AA%D8%AE%D8%AF%D9%85%D8%A9:%D8%AF%D9%86%D9%8A%D8%A7>
   - Ola Mahadi
   
<https://ar.wikipedia.org/wiki/%D9%85%D8%B3%D8%AA%D8%AE%D8%AF%D9%85:Ola.mahadi>

Accueillez-les chaleureusement 珞


Je tiens également à remercier toutes les personnes qui ont posé leur
candidature. L'appel a été difficile, c'est pourquoi nous avons dû
augmenter les sélections finales d'une personne par catégorie, car nous
avons constaté que tous les candidats avaient une combinaison unique
d'expérience et de compétences à offrir. Nous apprécions vraiment l'intérêt
que vous avez manifesté en étant si nombreux à poser votre candidature.


Cordialment

-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa] Announcing Wiki Loves Africa Ambassadors

[Wilson Oluoha]

Dear Friends,

A few weeks ago, Wiki in Africa published a call for volunteer Ambassadors
for Wiki Loves Africa
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa/Ambassadors#The_role_-_WLA_Ambassadors>
with the overall objective of helping on the Wiki Loves Africa initiative.

I am very happy to announce our new WLA Ambassadors in three language
categories;

*French :*


   - Minette Lontsie <https://fr.wikipedia.org/wiki/Utilisatrice:Serieminou>
   - Mermoze Adodo <https://fr.wikipedia.org/wiki/Utilisateur:Adoscam>

* English :*


   - Ogali Hilary <https://meta.wikimedia.org/wiki/User:Ogalihillary>
   - Alvin Ategyeka <https://meta.wikimedia.org/wiki/User:Alvinategyeka>

*Arabic :*


   - Donia Domiaty
   
<https://ar.wikipedia.org/wiki/%D9%85%D8%B3%D8%AA%D8%AE%D8%AF%D9%85%D8%A9:%D8%AF%D9%86%D9%8A%D8%A7>
   - Ola Mahadi
   
<https://ar.wikipedia.org/wiki/%D9%85%D8%B3%D8%AA%D8%AE%D8%AF%D9%85:Ola.mahadi>

Please give them a warm welcome 珞


I would like to also extend my thanks to all the people we received
applications from. This has been a tough call hence why we had to increase
the final selections by 1 person per category as we observed that all the
applicants had some unique combination of experience and skill to offer. We
really appreciate the interest from so many of you who applied.


Best,

-- 

*Wilson Oluoha*

UTC+1

Skype: studywilson1106 | Telegram: @Wilsn_Oluoha | Whatsapp: message
<https://wa.me/2348069451106>

Wikimedia  <https://meta.wikimedia.org/wiki/User:OtuNwachinemere>|
<https://www.linkedin.com/in/devouard/>LinkedIn
<https://www.linkedin.com/in/wilson-oluoha-a2b4a6181/> | Website
<https://www.wikilovesafrica.net/> | Instagram
<https://instagram.com/i_see_a_picture> | Twitter
<https://twitter.com/OluohaWilson>

Hear my name <https://namedrop.io/wilsonoluoha>
___
African-Wikimedians mailing list -- african-wikimedians@lists.wikimedia.org
To unsubscribe send an email to african-wikimedians-le...@lists.wikimedia.org

Re: CCADB Update: Upcoming Addition of Network Security and S/MIME Audits in the CCADB

[Ben Wilson]

Greetings,
The previously mentioned updates to the CCADB have been made. Please let us
know if you have any questions.
Thanks,
Ben

On Wed, Dec 13, 2023 at 3:29 PM 'Hannah Sokol' via CCADB Public <
public@ccadb.org> wrote:

> All,
>
>
>
> On Thursday, December 14, 2023, we will be updating the CCADB to introduce
> the ability to upload Network Security and S/MIME audit statements to the
> AUDITS tab for ‘Add/Update Root Request' cases.
>
>
>
> CA Owners should not be impacted during this update.
>
>
>
> This new functionality should enable CA Owners to:
>
>
>
> + Add Network Security and S/MIME Audit Statements to Root CA root records
> using the AUDITS tab of an 'Add/Update Root Request' case.
>
> + Add Network Security and S/MIME Audit Statements to Subordinate CA
> records in the same manner as done today with other types of Audit
> Statements.
>
> + Archive Network Security and S/MIME Audit Statements.
>
>
>
> We will also have a new “All Cert Information v2” csv report hosted in
> parallel with the existing report, accessible from
> https://www.ccadb.org/resources. This new report will include data on
> S/MIME and Network Security audits. (Version 1 of the report will
> eventually be discontinued.)
>
>
>
> We will send a separate email on Friday, December 15th, 2023, when these
> functionalities are fully available.
>
>
>
> Thank you,
>
> - Hannah, on behalf of the CCADB Steering Committee
>
> --
> You received this message because you are subscribed to the Google Groups
> "CCADB Public" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to public+unsubscr...@ccadb.org.
> To view this discussion on the web visit
> https://groups.google.com/a/ccadb.org/d/msgid/public/MW4PR00MB1028130539F41B38D7E716989B8DA%40MW4PR00MB1028.namprd00.prod.outlook.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to public+unsubscr...@ccadb.org.
To view this discussion on the web visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CA%2B1gtabcRVVcwTtepFY-0RMrRRnfTBnavfAOL%3Dp%2BquoPn0c7uQ%40mail.gmail.com.

[ovs-dev] [PATCH v2] python: idl: Handle monitor_canceled

[Terry Wilson]

Currently python-ovs claims to be "db change aware" but does not
parse the "monitor_canceled" notification. Transactions can continue
being made, but the monitor updates will not be sent. This handles
monitor_cancel similarly to how ovsdb-cs currently does.

Signed-off-by: Terry Wilson 
---
 python/ovs/db/idl.py | 32 
 1 file changed, 32 insertions(+)

diff --git a/python/ovs/db/idl.py b/python/ovs/db/idl.py
index 9fc2159b0..be6ae2ca4 100644
--- a/python/ovs/db/idl.py
+++ b/python/ovs/db/idl.py
@@ -299,6 +299,7 @@ class Idl(object):
 self._server_schema_request_id = None
 self._server_monitor_request_id = None
 self._db_change_aware_request_id = None
+self._monitor_cancel_request_id = None
 self._server_db_name = '_Server'
 self._server_db_table = 'Database'
 self.server_tables = None
@@ -481,6 +482,10 @@ class Idl(object):
 break
 else:
 self.__parse_update(msg.params[1], OVSDB_UPDATE)
+elif self.handle_monitor_canceled(msg):
+break
+elif self.handle_monitor_cancel_reply(msg):
+break
 elif (msg.type == ovs.jsonrpc.Message.T_REPLY
   and self._monitor_request_id is not None
   and self._monitor_request_id == msg.id):
@@ -615,6 +620,33 @@ class Idl(object):
 
 return initial_change_seqno != self.change_seqno
 
+def handle_monitor_canceled(self, msg):
+if msg.type != msg.T_NOTIFY:
+return False
+if msg.method != "monitor_canceled":
+return False
+
+if msg.params[0] == str(self.uuid):
+params = [str(self.server_monitor_uuid)]
+elif msg.params[0] == str(self.server_monitor_uuid):
+params = [str(self.uuid)]
+else:
+return False
+
+mc_msg = ovs.jsonrpc.Message.create_request("monitor_cancel", params)
+self._monitor_cancel_request_id = mc_msg.id
+self.send_request(mc_msg)
+self.restart_fsm()
+return True
+
+def handle_monitor_cancel_reply(self, msg):
+if msg.type != msg.T_REPLY:
+return False
+if msg.id != self._monitor_cancel_request_id:
+return False
+self._monitor_cancel_request_id = None
+return True
+
 def compose_cond_change(self):
 if not self.cond_changed:
 return
-- 
2.34.3

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[CODE4LIB] Cool Discovery Projects Follow-up

[Kristen Wilson]

Hi everyone,

A while back, I sent out a question on this list asking people to share
cool and innovative discovery projects. I got some good responses here, as
well as from other colleagues who I asked directly. I thought people might
be interested in the responses. I've compiled them into a spreadsheet with
the help of my colleague Hiva Kadivar. Take a look and let me know if you
have any other ideas to add!

https://docs.google.com/spreadsheets/d/18G0PIKtfrTMU-JCbhKbvDKZaxcFBgbFeLiPC2FnK9kk/edit#gid=14383371

Best,
Kristen


-- 
Kristen Wilson (she/her)
Discovery Systems Manager
NC State University Libraries
(919) 513-2118
kmbl...@ncsu.edu

Re: Seattle D Meetup Mailing List - Ferrari Night

[Adam Wilson via Digitalmars-d-announce]

On Saturday, 16 December 2023 at 22:24:46 UTC, Walter Bright 
wrote:

If you want to be on it, email me your address!

We hope to have some fun activities for D aficionados. For 
example, I am planning "Ferrari Night" towards the end of the 
month where we all meet at the theater to watch "Ferrari".


https://www.imdb.com/title/tt3758542


You have my email already!

[Translators-l] Re: Ready for translation: Tech News #51 (2023)

[Nick Wilson (Quiddity)]

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/51
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F51=page
>

The text of the newsletter is now final.
*One item has been added* since yesterday.
There won't be any more changes; you can translate safely. Thanks!

P.s. This is the last edition of the year, and I want to deeply thank
everyone here for being part of this newsletter, and all the other
translations you create/fix/discuss!
*You are appreciated*, by me, and the movement. :)
See you again in January, and best wishes for the new year!
Quiddity / Nick
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Celebrating Alice Kibombo

[Wilson Oluoha]

The Amazing Alice Kibombo ❤️.

I am forever grateful to you for your assistance in my early WiR  days.

Congratulations and more to come.

Best,

Wilson

On Fri, Dec 15, 2023 at 1:31 AM Florence Devouard 
wrote:

> Congratulations Alice ! Very well deserved ! Keep on the good work !
>
>
> Flo
>
>
> Le 14/12/2023 à 16:47, Belinda Mbambo a écrit :
>
>
> Hello, Muli mutya!
>
>
> It’s no secret that librarians make amazing Wikimedians. Whether it is
> because of the shared passion for knowledge or superpowers in working with
> sources, databases and categories, or the simple fact that librarians are
> just great human beings, we know that they thrive in the Wikimedia projects.
>
> Today, we Wikicelebrate
> <https://meta.wikimedia.org/wiki/Communications/WikiCelebrate>a truly
> amazing Wikimedian and librarian: Alice Kibombo
> <https://en.wikipedia.org/wiki/User:AKibombo> – a contributor to
> Wikipedia, Wikidata, Wikisource
> <https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Uganda/WikiSource_in_Uganda_2022>,
> and the Wikimedia Community User Group Uganda, a #1lib1ref trainer
> <https://www.youtube.com/watch?v=U3X_-w0tYp4=2854s>, and, in her
> Wikimedian in Residence role, personally trained ~180 English-speaking
> librarians in Wikidata!. From a common start as a Wikipedia reader to a
> transformative role as a teacher and community supporter, Alice Kibombo has
> become an inspiring figure in the pursuit of barrier-free access to the sum
> of human knowledge
>
> As she says: “Participating in the Wikimedia Movement has offered me the
> responsibility to be a more responsible contributor, a  community resource
> person as well as a teacher.”
>
> Learn more about Alice on Diff
> <https://diff.wikimedia.org/2023/12/14/one-librarian-many-achievements-meet-alice-kibombo-librarian-extraordinaire/>
>  as
> we WikiCelebrate her incredible dedication to free knowledge.
>
> Each month we WikiCelebrate a different Wikimedian, acknowledging the
> amazing community, the pillars of our movement. We warmly invite you to
> participate in the celebrations. If there’s an outstanding Wikimedian that
> you think should be celebrated, recommend
> <https://wikimediafoundation.limesurvey.net/WikiCelebrate>them.
>
> Happy celebrating!
>
> Winnie, Natalia, and Belinda
>
> *Belinda Mbambo*
> Senior Manager: Global Movement Communications
> Wikimedia Foundation <https://wikimediafoundation.org/>
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/QAHKIOZP65CVL4AGCCFC3KDPTXGJ3X44/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/DMNBPXRDOSODYUZJGD6MCTIU7VSA73KB/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/UUVWFT3NBNEGREERO4WVHPGJTJWHXO3T/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Translators-l] Ready for translation: Tech News #51 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/51

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F51=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Infrastructure] Draft Minutes of Meeting 13-Dec-2023

[Ben Wilson via Infrastructure]

Here are the draft minutes from today's call:

*Minutes of Infrastructure Committee – 13-December-2023*

*Present:*  Ben Wilson, Dean Coclin, Iñigo Barreira, Paul Van
Brouwershaven, Wayne Thayer, and Roman Fischer

Ben read the Note Well.

The major topic for discussion was the creation of procedures documents for
handling tasks related to new and existing members. Iñigo asked whether
anything could be added to Member Tools to facilitate the processing of
applications and onboarding of new members.  The creation of a handbook for
working group chairs was also recommended. Process flows need to consider
applicants for full membership (Certificate Issuers and Certificate
Consumers), interested parties, associate members and probationary members.
Procedures need to address all possibilities and information needs to be
collected for which working group and subcommittees the member wants to
join, the names of voting representatives, etc. Checklist documents will be
needed, as well as a calendar that can be transitioned to a new working
group chair when the existing chair leaves office. (E.g. how would we track
the 6-month probationary period during a transition to new leadership?)

Iñigo said he would prepare a list of the documents of which he is aware
and provide a framework for dealing with the issues he encounters.  We’ll
need to prepare an outline of the handbook. The handbook could be generic
and useable by all working groups, with appendices for things that
specifically apply only to one working group.

Instructions for the Member Tools are also needed. It’s unclear how to
update a person’s record if they leave a company. Also, it was noted that
there are a couple of member self-management options that members should
use, which they should be able to find through links available on the wiki
– one using Member Tools and one using a Google Form.

Paul also suggested that we transition from WordPress to GoHugo (
https://gohugo.io). Then, we can manage the website’s member lists,
ballots, guideline documents, and minutes more easily using GitHub. He said
he has had a favorable experience doing so with another organization.

The meeting on December 27th is cancelled.

Meeting adjourned.
___
Infrastructure mailing list
Infrastructure@cabforum.org
https://lists.cabforum.org/mailman/listinfo/infrastructure

[jira] [Commented] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795959#comment-17795959
 ] 

Wilson M Penha Jr. commented on AMBARI-26009:
-

I was able to install ambari however it doesn't come with ambari-metris and 
ambari-infra-solr which is being used by the repo you have added to the 
package, so ambari-infra-solr is removed from ambari-3.0?

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

Re: Seattle Area D-Meetup

[Adam Wilson via Digitalmars-d-announce]

On Tuesday, 12 December 2023 at 17:52:12 UTC, Gregor Mückl wrote:

Hi!

I'm interested in joining this time. Looking forward to meeting 
you all!


I look forward to meeting you!

Re: [Frameworks] Jane

[Brian Wilson]

 I got to meet Jane in 2019 when I was in Denver showing some of my 16mm work. 
We remained pen pals over the few years since. 
For the 20 years prior to my meeting her, my concept of her had been forged by 
her appearances in the films. She was more myth than reality. But getting to 
know her opened my eyes to just how complex and funny and deeply creative she 
really was. 
I was glad to call her a friend for at least that short period of time. 


Brian Wilson

Assistant Professor

Languages, Arts, and Social Sciences

Loudoun Campus / LR-307A

21200 Campus Drive, Sterling, VA 20164

618.924.3865 / bwil...@nvcc.edu

On Tuesday, December 12, 2023 at 02:39:20 PM CST, Adam Hyman 
 wrote:  
 
 
She was a delightful human being.

  

Here’s a NY Times obit.

 https://www.nytimes.com/2023/12/07/books/jane-wodening-dead.html

We hosted her in March 2020.

Here is the video from the event

https://www.youtube.com/watch?v=P844IAg8rUM=27s

  

Best regards,

Adam

  

  

-- 

Adam Hyman

Los Angeles Filmforum

a...@lafilmforum.org

http://www.lafilmforum.org

  

  

On 12/10/23, 6:36 AM, "Frameworks on behalf of Dominic Angerame" 
 
wrote:

  

Marilyn Brakhage had told me this last week, but I was remiss in reporting it 
here. Thought it was already posted and I had missed it. I had the pleasure of 
meeting her a few times…..

  

D






On Dec 9, 2023, at 9:47 PM, Pip Chodorov  wrote:

  

I’m sad to read that Jane Wodening has died.

  

  

| 
<06wodening-01-pvqj-facebookJumbo.png>
 |
| 
| 
Jane Wodening, Experimental Film Star and Intrepid Writer, Dies at 87 (Gift 
Article)

nytimes.com
 |

 |


-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org


  

-- Frameworks mailing list Frameworks@film-gallery.org 
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org 
-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org
  -- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org

[jira] [Commented] (AMBARI-26028) ambiguous python shebang and mangling shebang error on CentOS 8 series

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795937#comment-17795937
 ] 

Wilson M Penha Jr. commented on AMBARI-26028:
-

I got this same issue and I got to replace it all with python2 and the build 
finished and I was able to install ambari-server, but there are still many 
things to be done to make it work 100%

I use "sed" to change all .py/.py.j2 files

> ambiguous python shebang and mangling shebang error on CentOS 8 series
> --
>
> Key: AMBARI-26028
> URL: https://issues.apache.org/jira/browse/AMBARI-26028
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.8.0
> Environment: {code:bash}
> $ cat /etc/os-release 
> NAME="Rocky Linux"
> VERSION="8.8 (Green Obsidian)"
> ID="rocky"
> ID_LIKE="rhel centos fedora"
> VERSION_ID="8.8"
> PLATFORM_ID="platform:el8"
> PRETTY_NAME="Rocky Linux 8.8 (Green Obsidian)"
> ANSI_COLOR="0;32"
> LOGO="fedora-logo-icon"
> CPE_NAME="cpe:/o:rocky:rocky:8:GA"
> HOME_URL="https://rockylinux.org/;
> BUG_REPORT_URL="https://bugs.rockylinux.org/;
> SUPPORT_END="2029-05-31"
> ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
> ROCKY_SUPPORT_PRODUCT_VERSION="8.8"
> REDHAT_SUPPORT_PRODUCT="Rocky Linux"
> REDHAT_SUPPORT_PRODUCT_VERSION="8.8"
> {code}
>Reporter: Kane
>Priority: Major
>  Labels: RedHat
>
> I tried to build the ambari-release-2.8.0-rc1 version on Rocky Linux 8.8, but 
> It can not be completed.
> Error as:
> {code:bash}
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/etc
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/usr/sbin
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/usr/lib/ambari-server
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/var/lib/ambari-server
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/var/log/ambari-server
> [INFO] Mapping empty with destination: ambari-server
> [INFO] Copying files to 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/tmp-buildroot/var/run/ambari-server
> [INFO] Creating spec file 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/SPECS/ambari-server.spec
> [DEBUG] writing attribute string for identified files in directory: /etc
> [DEBUG] writing attribute string for identified files in directory: /usr/sbin
> [DEBUG] writing attribute string for directory: /usr/lib/ambari-server
> [DEBUG] writing attribute string for directory: /var/lib/ambari-server
> [DEBUG] writing attribute string for directory: /var/log/ambari-server
> [DEBUG] writing attribute string for directory: /var/run/ambari-server
> [DEBUG] About to execute '/bin/sh -c cd 
> '/home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/SPECS'
>  && 'rpmbuild' '-bb' '--target' 'x86_64-redhat-linux' '--buildroot' 
> '/home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/buildroot'
>  '--define' '_topdir 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server' 
> '--define' '_build_name_fmt 
> %%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm' '--define' '_builddir 
> %{_topdir}/BUILD' '--define' '_rpmdir %{_topdir}/RPMS' '--define' '_sourcedir 
> %{_topdir}/SOURCES' '--define' '_specdir %{_topdir}/SPECS' '--define' 
> '_srcrpmdir %{_topdir}/SRPMS' 'ambari-server.spec''
> [INFO] Building target platforms: x86_64-redhat-linux
> [INFO] Building for target x86_64-redhat-linux
> [INFO] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.S5kaKk
> [INFO] + umask 022
> [INFO] + cd 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/BUILD
> [INFO] + '[' 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/buildroot
>  '!=' / ']'
> [INFO] + rm -rf 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/buildroot
> [INFO] ++ dirname 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server/buildroot
> [INFO] + mkdir -p 
> /home/kane/ambari-release-2.8.0-rc1/ambari-server/target/rpm/ambari-server
> [INFO] + mkdir 
&g

[jira] [Commented] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795924#comment-17795924
 ] 

Wilson M Penha Jr. commented on AMBARI-26009:
-

Hi [~jialiang] thanks a lot, I'll give it a try

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

Re: [Infrastructure] Update of "old" documents

[Ben Wilson via Infrastructure]

I have an item on my to-do list to work on this with Iñigo.
Cheers,
Ben

On Tue, Dec 12, 2023 at 8:32 AM Dean Coclin via Infrastructure <
infrastructure@cabforum.org> wrote:

> These were tools that Dimitris created and I refer to from time to time.
> We should keep/update them and add someplace in the tool.
> Dean
>
>
>
> *Dean Coclin *
>
> Sr. Director Business Development
>
> M 1.781.789.8686
>
>
>
>
>
>
>
>
>
> *From:* Infrastructure  *On Behalf
> Of *Inigo Barreira via Infrastructure
> *Sent:* Tuesday, December 12, 2023 4:28 AM
> *To:* Ben Wilson via Infrastructure 
> *Subject:* [Infrastructure] Update of "old" documents
>
>
>
> Hi there,
>
>
>
> Maybe of interest for tomorrow´s call.
>
> While reviewing the application of TrustAsia, found this google doc with a
> checklist of what to do Checklist for New Member in SCWG/CAB Forum -
> Google Sheets
> <https://docs.google.com/spreadsheets/d/1ayGAM80rUTlccsX5F-zxuUks6jftBsqVi3Vll0er1Z0/edit#gid=0>
>
> Do we need to update all these google docs? Have these implemented somehow
> in the member tool?
>
> Another one could be the IPRs document, do we need to keep the old ones in
> the wiki? What to do when one organization/person changes status? For
> example, TrustAsia from associate member to full member?
>
>
>
> Regards
> ___
> Infrastructure mailing list
> Infrastructure@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/infrastructure
>
___
Infrastructure mailing list
Infrastructure@cabforum.org
https://lists.cabforum.org/mailman/listinfo/infrastructure

Re: D Language Foundation October 2023 Quarterly Meeting Summary

[Nicholas Wilson via Digitalmars-d-announce]

On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson 
wrote:
Or you could use grep with `--output-ll` as noted by Johan 
https://github.com/ldc-developers/ldc/issues/4265#issuecomment-1376424944 although this will be with that `workaroundIssue1356` applied.


Thanks for highlighting this, as I must have forgotten. I 
should be able to create a CI job that checks this as part of 
the release. This will give us the confidence that we need.


I should note that regex will need some updating for the most 
recent LLVMs that have opaque pointers enabled:


`ptr byval\(%[a-zA-Z_][a-zA-Z0-9_\.]*\) align`

[Translators-l] Re: Ready for translation: Tech News #50 (2023)

[Nick Wilson (Quiddity)]

Thank you all for your help! It is deeply appreciated. The newsletter has
now been delivered (in 21 languages) to 1,102 pages.
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[Wikitech-ambassadors] Tech News 2023, week 50

[Nick Wilson (Quiddity)]

The latest technical newsletter is now available at
https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2023/50. Below
is the English version.
You can help write the next newsletter: Whenever you see information about
Wikimedia technology that you think should be distributed more broadly, you
can add it to the next newsletter at
https://meta.wikimedia.org/wiki/Tech/News/Next .
More information on how to contribute is available. You can also contact me
directly.
As always, feedback (on- or off-list) is appreciated and encouraged.
——
Other languages: Bahasa Indonesia
, Deutsch
, English, Hausa
, Nederlands
, Tiếng Việt
, Tyap
, español
, français
, italiano
, magyar
, norsk bokmål
, polski
, português
, português do Brasil
, svenska
, čeština
, русский
, українська
, עברית
, العربية
, ಕನ್ನಡ
, 中文
, 日本語


Latest *tech news
* from the
Wikimedia technical community. Please tell other users about these changes.
Not all changes will affect you. Translations
 are
available.

*Recent changes*

   - On Wikimedia Commons, there are some minor user-interface improvements
   for the "choosing own vs not own work" step in the UploadWizard. This is
   part of the Structured Content team's project of improving UploadWizard
   on Commons
   
.
   [1] [2]
   

*Problems*

   - There was a problem showing the Newcomer homepage
   

   feature with the "impact module" and their page-view graphs, for a few days
   in early December. This has now been fixed. [3]
   [4]
   

*Changes later this week*

   - The new version 
   of MediaWiki will be on test wikis and MediaWiki.org from 12 December. It
   will be on non-Wikipedia wikis and some Wikipedias from 13 December. It
   will be on all wikis from 14 December (calendar
   ). [5]
   [6]
   

*Future changes*

   - The 2023 Developer Satisfaction Survey
    is seeking the
   opinions of the Wikimedia developer community. Please take the survey if
   you have any role in developing software for the Wikimedia ecosystem. The
   survey is open until 5 January 2024, and has an associated privacy
   statement
   

   .

*Tech news 
prepared by Tech News writers
 and
posted by bot

•
Contribute
 •
Translate
 •
Get help  • Give feedback
 • Subscribe or unsubscribe
.*
___
Wikitech-ambassadors mailing list -- 

Re: D Language Foundation October 2023 Quarterly Meeting Summary

[Nicholas Wilson via Digitalmars-d-announce]

On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson 
wrote:
Always happy to help if you're interested in looking into 
using dcompute.


Thank you, I'll let you know!


And please do get in touch with Bruce Carneal if you want some 
tips and insight with the practical and applied side of dcompute 
(also with auto-vectorisation) as he has used it a lot more than 
I have.


Or you could use grep with `--output-ll` as noted by Johan 
https://github.com/ldc-developers/ldc/issues/4265#issuecomment-1376424944 although this will be with that `workaroundIssue1356` applied.


Thanks for highlighting this, as I must have forgotten. I 
should be able to create a CI job that checks this as part of 
the release. This will give us the confidence that we need.


-- Bastiaan.


Cheers, I look forward to some large speed increase reports.

Re: First camera case

[mike wilson]

No padding over the top of everything?
> On 11/12/2023 05:20 GMT Larry Colen  wrote:
> 
>  
> A couple of weeks back I was nattering about wanting a better case for 
> storing my gear, and carrying it in my car on a trip.
> 
> I just finished the first case, for the majority of my full frame glass and 
> the K-1.  I made it with a $30 case from Home Depot (I already had a bunch of 
> cases in this system), and about $20 worth of Kaizen foam.
> 
> It's not a $300 Pelican case, but it's a lot more protective and water 
> resistant than carrying everything in bags.
> 
> https://photos.app.goo.gl/EvxT6cztCbKZsHCA8
> 
> I photographed the whole build process.
> https://photos.app.goo.gl/1JTA4jxGw4mniNQX9
> 
> And, yes, I know that a couple  of y'all aren't fans of google photos, sorry 
> about that, but I just don't have the time and energy to come up with a plan 
> B.
> 
> Things would have worked better if I had hole saws with finer teeth.  Oh well.
>
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: D Language Foundation October 2023 Quarterly Meeting Summary

[Nicholas Wilson via Digitalmars-d-announce]

On Sunday, 10 December 2023 at 16:08:45 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 15:31:55 UTC, Richard (Rikki) 
Andrew Cattermole wrote:


It will be interesting to hear how dcompute will fare in your 
situation, due to it being D code it should be an incremental 
improvement once you're ready to move to D fully.


Yes, dcompute could mean another leap forward. There are so 
many great things to look forward to.


-- Bastiaan.


Always happy to help if you're interested in looking into using 
dcompute. I can't remember if we've talked about it before, but 
if you were wanting to use it you'd need OpenCL 2.x (explicitly 
the 2.x version series, or make sure the 3.x implementation 
supports SPIRV) running on that 20 logical core box (or if it has 
GPUs attached to it, CUDA (any version should do) for NVidia GPUs 
or OpenCL 2.x (as above) on any other GPUs).


With regards to the stack corruption there is 
https://github.com/ldc-developers/ldc/blob/master/gen/abi/x86.cpp#L260 which has been there for some time. It would be fairly simple to issue a diagnostic there (although getting source location from there might be a bit tricky) for when there is both a `byval` and an alignment specified.


Or you could use grep with `--output-ll` as noted by Johan 
https://github.com/ldc-developers/ldc/issues/4265#issuecomment-1376424944 although this will be with that `workaroundIssue1356` applied.

Re: Let's test the list!

[mike wilson]

Not horrendously expensive here, as long as your consumer unit (fusebox) has 
room for it.  Cartridge types (a base that fits the rail in the unit with a 
replaceable active part) vary from about £30 to £150.  No more than an hour's 
work for the sparky to fit it.  Using surge protector plugs on everything would 
easily cost us that.
> On 09/12/2023 17:24 GMT Alan Cole  wrote:
> 
>  
> In SA with up to 8 hours Load Shedding per day & subsequent switch on
> surges, the insurance claims have skyrocketed. Mostly TV's, Fridges &
> Aircons. The insurance companies have now "eliminated" their risk by
> insisting on a surge protector fitted to the DB by a certified electrician.
> Too expensive for most of us so we now have individual surge plugs on
> sensitive appliances.
> 
> Alan C
> 
> On Sat, Dec 9, 2023 at 10:41 AM mike wilson  wrote:
> 
> > Surge protectors are mandatory on new installs in the UK, now, probably
> > because of the poor state of the supply infrastructure.  We had three
> > failures last year (with accompanying surges) alone.  None so far this
> > year, surprisingly.
> > > On 07/12/2023 22:48 GMT Rick Womer  wrote:
> > >
> > >
> > > I don't know about the server gods, but some gods somewhere weren't happy
> > > with my photo computer .
> > >
> > > On the night of November 13 it seems that our house had a massive power
> > > surge. The victims were (1) my photo computer setup, consisting of a Mac
> > > Mini and two on-line OWC hard drives. A few days later we learned that
> > the
> > > control circuit board and some of the wiring for our house's minisplit
> > > AC/heating system were partially melted (we are now using our hot water
> > > heating system).
> > >
> > > We're waiting for a new circuit board and valves for the minisplit
> > system,
> > > and I've been chipping away at the computer problems. The OS on the Mac
> > > needs replacing, and both external drives have media and file system
> > errors
> > > on Disk Utility which are making them flaky.
> > >
> > > So, in the midst of other activities, I've been chipping away at the
> > > problem. I'm shifting files from two other external hard drives (which
> > > aren't in daily use) so that I can shift my files off the damaged drives
> > > and reformat them.
> > >
> > > Then I'll be able to transfer a bunch of files, reformat the external
> > > drives they were on, transfer files back, and hope that Lightroom
> > > cooperates in getting everything accessible.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: Let's test the list!

[mike wilson]

Surge protectors are mandatory on new installs in the UK, now, probably because 
of the poor state of the supply infrastructure.  We had three failures last 
year (with accompanying surges) alone.  None so far this year, surprisingly.
> On 07/12/2023 22:48 GMT Rick Womer  wrote:
> 
>  
> I don't know about the server gods, but some gods somewhere weren't happy
> with my photo computer .
> 
> On the night of November 13 it seems that our house had a massive power
> surge. The victims were (1) my photo computer setup, consisting of a Mac
> Mini and two on-line OWC hard drives. A few days later we learned that the
> control circuit board and some of the wiring for our house's minisplit
> AC/heating system were partially melted (we are now using our hot water
> heating system).
> 
> We're waiting for a new circuit board and valves for the minisplit system,
> and I've been chipping away at the computer problems. The OS on the Mac
> needs replacing, and both external drives have media and file system errors
> on Disk Utility which are making them flaky.
> 
> So, in the midst of other activities, I've been chipping away at the
> problem. I'm shifting files from two other external hard drives (which
> aren't in daily use) so that I can shift my files off the damaged drives
> and reformat them.
> 
> Then I'll be able to transfer a bunch of files, reformat the external
> drives they were on, transfer files back, and hope that Lightroom
> cooperates in getting everything accessible.
> 
>
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

[Translators-l] Re: Ready for translation: Tech News #50 (2023)

[Nick Wilson (Quiddity)]

On Thu, Dec 7, 2023 at 4:36 PM Nick Wilson (Quiddity) 
wrote:

> The latest tech newsletter is ready for early translation:
> https://meta.wikimedia.org/wiki/Tech/News/2023/50
>
> Direct translation link:
>
> https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F50=page
>

The text of the newsletter is now final.

*Three items have been added* since yesterday.

There won't be any more changes; you can translate safely. Thanks!
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org

[jira] [Comment Edited] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794829#comment-17794829
 ] 

Wilson M Penha Jr. edited comment on AMBARI-26009 at 12/8/23 9:20 PM:
--

Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

I found an error during the rpm install:
  Running scriptlet: ambari-server-3.0.0.0-SNAPSHOT.x86_64     1/1 
/var/tmp/rpm-tmp.aeukrL: line 27: //var/lib/ambari-server/install-helper.sh: 
Permission denied
By looking into that file I saw a reference to /usr/lib/python2.6 and I am on 
python2.7 

The rpm install is setting rw only for root when unpacking during ambari-server 
installation
By looking at ambari-agent I see the script with proper permissions rwxr-xr-x

Any advice is appreciated 


was (Author: wilsonpenha):
Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

I found an error during the rpm install:
  Running scriptlet: ambari-server-3.0.0.0-SNAPSHOT.x86_64     1/1 
/var/tmp/rpm-tmp.aeukrL: line 27: //var/lib/ambari-server/install-helper.sh: 
Permission denied
By looking into that file I saw a reference to /usr/lib/python2.6 and I am on 
python2.7 

Any advice is appreciated 

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Comment Edited] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794829#comment-17794829
 ] 

Wilson M Penha Jr. edited comment on AMBARI-26009 at 12/8/23 7:18 PM:
--

Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

I found an error during the rpm install:
  Running scriptlet: ambari-server-3.0.0.0-SNAPSHOT.x86_64     1/1 
/var/tmp/rpm-tmp.aeukrL: line 27: //var/lib/ambari-server/install-helper.sh: 
Permission denied
By looking into that file I saw a reference to /usr/lib/python2.6 and I am on 
python2.7 

Any advice is appreciated 


was (Author: wilsonpenha):
Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

I found an error during the rpm install:
  Running scriptlet: ambari-server-3.0.0.0-SNAPSHOT.x86_64     1/1 
/var/tmp/rpm-tmp.aeukrL: line 27: //var/lib/ambari-server/install-helper.sh: 
Permission denied
By looking into that file I saw a reference to /usr/lib/python2.6 and I am on 
python2.7 

Any advise is appreciated 

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Comment Edited] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794829#comment-17794829
 ] 

Wilson M Penha Jr. edited comment on AMBARI-26009 at 12/8/23 7:18 PM:
--

Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

I found an error during the rpm install:
  Running scriptlet: ambari-server-3.0.0.0-SNAPSHOT.x86_64     1/1 
/var/tmp/rpm-tmp.aeukrL: line 27: //var/lib/ambari-server/install-helper.sh: 
Permission denied
By looking into that file I saw a reference to /usr/lib/python2.6 and I am on 
python2.7 

Any advise is appreciated 


was (Author: wilsonpenha):
Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

Any advise is appreciated 

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Commented] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794829#comment-17794829
 ] 

Wilson M Penha Jr. commented on AMBARI-26009:
-

Thx for clarifying [~jialiang], I manage to do a few adaptation and could 
install ambari-agent and server, however it seems the ambari-server install is 
not creating the ambari-server.services as it used to do and as ambari-agent 
does and something is missing when I do it by hands causing the service to stop 
after start and show many warning msgs after this line : Errors:173 - The 
following warnings have been detected with resource and/or provider classes:

When I start ambari-server using normal 'sudo ambari-server start' it does keep 
up

I am planning to use it to deploy bigtop which is still python2 so I may try it 
here before get into python3

Any advise is appreciated 

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The PR that needs to be merged for Python3 is 
> [https://github.com/apache/ambari/pull/3751].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

Re: Public Discussion of D-Trust CA Inclusion Request

[Ben Wilson]

Greetings,

This is a reminder that the public discussion period on the inclusion
application of D-Trust will close next Friday, December 15, 2023.

Thank you,
Ben Wilson, on behalf of the CCADB Steering Committee

On Mon, Nov 6, 2023 at 10:02 AM Ben Wilson  wrote:

> All,
>
> Regarding the D-Trust Certification Practice Statement—instead of
> referencing the D-Trust Root PKI CPS, it should have referenced the CPS of
> the D-Trust CSM PKI, v.4.0, valid from 28-September-2023 (
> https://www.d-trust.net/internet/files/D-TRUST_CSM_PKI_CPS.pdf) (from 19
> July 2023, the CSM PKI CPS applies to certificates with policy levels
> QEVCP-w, QNCP-w, EVCP, OVCP and LCP).
>
> Also, it didn’t mention the following Bugzilla bugs opened in the past 24
> months:
>
> 1756122 <https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>
>
> D-TRUST: Wrong key usage (Key Agreement)
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1756122>
>
> RESOLVED
>
> [dv-misissuance]
>
> 1793440 <https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>
>
> D-TRUST: CRL not DER-encoded
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1793440>
>
> RESOLVED
>
> [crl-failure]
>
> 1861069 <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>
>
> D-Trust: Issuance of 15 DV certificates containing ‘serialNumber’ field
> within subject <https://bugzilla.mozilla.org/show_bug.cgi?id=1861069>
>
> OPEN
>
> [dv-misissuance]
>
> 1862082 <https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>
>
> D-Trust: Delay beyond 5 days in revoking misissued certificate
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1862082>
>
> OPEN
>
> [leaf-revocation-delay]
>
>
>
> Ben
>
> On Fri, Nov 3, 2023 at 9:39 AM Ben Wilson  wrote:
>
>> All,
>>
>> This email commences a six-week public discussion of D-Trust’s request to
>> include the following CA certificates as publicly trusted root certificates
>> in one or more CCADB Root Store Member’s program. This discussion period is
>> scheduled to close on December 15, 2023.
>>
>> The purpose of this public discussion process is to promote openness and
>> transparency. However, each Root Store makes its inclusion decisions
>> independently, on its own timelines, and based on its own inclusion
>> criteria. Successful completion of this public discussion process does not
>> guarantee any favorable action by any root store.
>>
>> Anyone with concerns or questions is urged to raise them on this CCADB
>> Public list by replying directly in this discussion thread. Likewise, a
>> representative of the applicant must promptly respond directly in the
>> discussion thread to all questions that are posted.
>>
>> CCADB Case Numbers:   # 1000
>> <https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1000>
>> and # 1001
>> <https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1001>
>>
>> Organization Background Information (listed in CCADB):
>>
>>-
>>
>>CA Owner Name: D-Trust GmbH
>>-
>>
>>Website:  https://www.d-trust.net/en
>>-
>>
>>Address:  Kommandantenstr. 15, Berlin, 10969, Germany
>>-
>>
>>Problem Reporting Mechanisms:
>>-
>>
>>   https://www.d-trust.net/en/support/reporting-certificate-problem
>>   -
>>
>>Organization Type: D-Trust GmbH is a subsidiary of the
>>Bundesdruckerei Group GmbH (bdr) and is fully owned by the German State.
>>-
>>
>>Repository URL:  https://www.bundesdruckerei.de/en/Repository
>>
>> Certificates Requested for Inclusion:
>>
>>1.
>>
>>D-Trust SBR Root CA 1 2022:
>>-
>>
>>   384-bit ECC
>>   -
>>
>>   Certificate download links: (CA Repository
>>   <http://www.d-trust.net/cgi-bin/D-Trust_SBR_Root_CA_1_2022.crt>,
>>   crt.sh
>>   
>> <https://crt.sh/?sha256=D92C171F5CF890BA428019292927FE22F3207FD2B54449CB6F675AF4922146E2>
>>   )
>>   -
>>
>>   Use cases served/EKUs:
>>   -
>>
>>  Secure Email (S/MIME) 1.3.6.1.5.5.7.3.4
>>  -
>>
>>  Client Authentication 1.3.6.1.5.5.7.3.2
>>  -
>>
>>  Document Signing AATL 1.2.840.113583.1.1.5
>>  -
>>
>>  Document Signing MS 1.3.6.1.4.1.311.10.3.12
>>
>>
>>
>>1.
>>
>>D-Trust SBR Root CA 2 2022:
>>-
>>
>>   409

[jira] [Commented] (AMBARI-26009) Add Rocky8 operating system support

[Wilson M Penha Jr. (Jira)]

[ 
https://issues.apache.org/jira/browse/AMBARI-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794482#comment-17794482
 ] 

Wilson M Penha Jr. commented on AMBARI-26009:
-

Hi
I've checked out this branch and tried to build it on RockyLinux 8.8,
 # the first issue was about many .py files getting this py: #!/usr/bin/env 
python. Change it to python3 (or python2) explicitly.
which I managed to fix using sed to replace it all and resume the build and it 
got complete
 # Then give a shop trying to install ambari-agent using rpm :
sudo rpm -i 
ambari-agent/target/rpm/ambari-agent/RPMS/x86_64/ambari-agent-3.0.0.0-SNAPSHOT.x86_64.rpm
 
error: Failed dependencies:
    python >= 2.6 is needed by ambari-agent-3.0.0.0-SNAPSHOT.x86_64
    rpm-python is needed by ambari-agent-3.0.0.0-SNAPSHOT.x86_64



Could you please tell me how to get away from this rpm-python dependency? That 
seems to be my only block and will be everyone else blocks

Cheers

Wilson

> Add Rocky8 operating system support
> ---
>
> Key: AMBARI-26009
> URL: https://issues.apache.org/jira/browse/AMBARI-26009
> Project: Ambari
>  Issue Type: New Feature
>Reporter: caijialiang
>Assignee: caijialiang
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[Translators-l] Ready for translation: Tech News #50 (2023)

[Nick Wilson (Quiddity)]

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2023/50

Direct translation link:
https://meta.wikimedia.org/w/index.php?title=Special:Translate=page-Tech%2FNews%2F2023%2F50=page

We plan to send the newsletter on Monday afternoon (UTC), i.e. Monday
morning PT. The existing translations will be posted on the wikis in
that language. Deadlines:
https://meta.wikimedia.org/wiki/Tech/News/For_contributors#The_deadlines

There will be more edits by Friday noon UTC but the existing content should
generally remain fairly stable. I will let you know on Friday in any
case.

Let us know if you have any questions, comments or concerns. As
always, we appreciate your help and feedback.

(If you haven't translated Tech News previously, see this email:
https://lists.wikimedia.org/pipermail/translators-l/2017-January/003773.html
___
Translators-l mailing list -- translators-l@lists.wikimedia.org
To unsubscribe send an email to translators-l-le...@lists.wikimedia.org