from:"wilson"

This system was a rsync clone of a baremetal 22.04 system with the
intention of being the drive I test the 24.04 upgrade on before doing
it, so I still have the source system on 22.04 if there is something you
want me to investigate on the source. I suppose the rsync command may
not be syncing correctly or I'm using the wrong flags.

The rsync was done

rsync -qaxH --delete --ignore-errors / /mnt/backup
rsync -qaxH --delete --ignore-errors /boot/efi /mnt/backup/boot

sed -i "s/$SourceRootUUID/$TargetRootUUID/g" /mnt/backup/etc/fstab
sed -i "s/$SourceRootUUID/$TargetRootUUID/g" /mnt/backup/boot/grub/grub.cfg
sed -i "s/$SourceEFIUUID/$TargetEFIUUID/g" /mnt/backup/etc/fstab
sed -i "s/$SourceEFIUUID/$TargetEFIUUID/g" /mnt/backup/boot/grub/grub.cfg
sed -i "s/$SourceRootUUID/$TargetRootUUID/g" 
/mnt/backup/boot/efi/EFI/ubuntu/grub.cfg
chroot /mnt/backup grub-install /dev/$DEV
chroot /mnt/backup /usr/sbin/update-grub

The clone is booted on another baremetal intel 700p.

I've done nothing to specifically remove /usr-merged.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Bug 2058648] Re: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz u

root@host:/lib/x86_64-linux-gnu# ls -lath ld*
-rwxr-xr-x 1 root root 236K Jan  2 08:22 ld-linux-x86-64.so.2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Bug 2058648] Re: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz u

dpkg -l output

** Attachment added: "dpkg output"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+attachment/5758139/+files/dpkg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Bug 2058648] Re: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz u

root@host:/lib/i386-linux-gnu# ls -lath
total 200K
drwxr-xr-x  2 root root 4.0K Mar 21 08:36 .
drwxr-xr-x 19 root root 4.0K Mar 21 08:36 ..
lrwxrwxrwx  1 root root   14 Jun  7  2023 libcap.so.2 -> libcap.so.2.44
-rw-r--r--  1 root root  38K Jun  7  2023 libcap.so.2.44
-rw-r--r--  1 root root 150K May 13  2023 libgcc_s.so.1
lrwxrwxrwx  1 root root   46 Dec 26  2022 libgpg-error.so.0.32.1 -> 
/usr/lib/i386-linux-gnu/libgpg-error.so.0.32.1
lrwxrwxrwx  1 root root   43 Dec 26  2022 libnss_nis.so.2.0.0 -> 
/usr/lib/i386-linux-gnu/libnss_nis.so.2.0.0
lrwxrwxrwx  1 root root   47 Dec 26  2022 libnss_nisplus.so.2.0.0 -> 
/usr/lib/i386-linux-gnu/libnss_nisplus.so.2.0.0
lrwxrwxrwx  1 root root   40 Dec 26  2022 liblzma.so.5.2.5 -> 
/usr/lib/i386-linux-gnu/liblzma.so.5.2.5
lrwxrwxrwx  1 root root   44 Dec 26  2022 libdbus-1.so.3.19.13 -> 
/usr/lib/i386-linux-gnu/libdbus-1.so.3.19.13
lrwxrwxrwx  1 root root   41 Dec 26  2022 libcom_err.so.2.1 -> 
/usr/lib/i386-linux-gnu/libcom_err.so.2.1
lrwxrwxrwx  1 root root   41 Dec 26  2022 libcrypt.so.1.1.0 -> 
/usr/lib/i386-linux-gnu/libcrypt.so.1.1.0
lrwxrwxrwx  1 root root   41 Dec 26  2022 libtirpc.so.3.0.0 -> 
/usr/lib/i386-linux-gnu/libtirpc.so.3.0.0
lrwxrwxrwx  1 root root   42 Dec 26  2022 libkeyutils.so.1.9 -> 
/usr/lib/i386-linux-gnu/libkeyutils.so.1.9
lrwxrwxrwx  1 root root   20 Oct 25  2022 libdbus-1.so.3 -> libdbus-1.so.3.19.13
lrwxrwxrwx  1 root root   17 Jul 25  2022 libtirpc.so.3 -> libtirpc.so.3.0.0
lrwxrwxrwx  1 root root   17 Jun  1  2022 libcom_err.so.2 -> libcom_err.so.2.1
lrwxrwxrwx  1 root root   16 Apr  8  2022 liblzma.so.5 -> liblzma.so.5.2.5
lrwxrwxrwx  1 root root   23 Mar 24  2022 libnss_nisplus.so.2 -> 
libnss_nisplus.so.2.0.0
lrwxrwxrwx  1 root root   19 Mar 24  2022 libnss_nis.so.2 -> libnss_nis.so.2.0.0
lrwxrwxrwx  1 root root   18 Feb 28  2022 libkeyutils.so.1 -> libkeyutils.so.1.9
lrwxrwxrwx  1 root root   22 Jan 18  2022 libgpg-error.so.0 -> 
libgpg-error.so.0.32.1
lrwxrwxrwx  1 root root   17 Dec 17  2021 libcrypt.so.1 -> libcrypt.so.1.1.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Bug 2058648] Re: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz u

# ls -lh /
total 2.1G
drwxr-xr-x   2 root   root 4.0K Mar 18 17:26 bin
drwxr-xr-x   4 root   root 4.0K Mar 19 16:34 boot
drwxrwxr-x   2 root   root 4.0K May 26  2018 cdrom
drwxr-xr-x   2 root   root 4.0K Feb 24  2021 code
-rw---   1 root   root 5.1M Jan 17  2020 core
drwxr-xr-x  20 root   root 4.8K Mar 20 20:33 dev
drwxr-xr-x 189 root   root  12K Mar 21 08:36 etc
drwxrwxrwx   3 root   root 4.0K Feb  4  2023 evs_temp
drwxr-xr-x  15 root   root 4.0K Feb 24  2021 home
lrwxrwxrwx   1 root   root   34 Sep 30  2021 initrd.img -> 
boot/initrd.img-4.15.0-159-generic
lrwxrwxrwx   1 root   root   34 Sep 30  2021 initrd.img.old -> 
boot/initrd.img-4.15.0-158-generic
drwxr-xr-x  19 root   root 4.0K Mar 21 08:36 lib
drwxr-xr-x   2 root   root 4.0K Jan 12 06:24 lib64
drwx--   2 root   root  16K May 26  2018 lost+found
drwxr-xr-x   4 root   root 4.0K Dec 29  2022 media
drwxr-xr-x   9 root   root 4.0K Jan  8  2023 mnt
drwxr-xr-x   3 root   root 4.0K Jul 12  2020 new
drwxr-xr-x  16 root   root 4.0K Jan 27 22:38 opt
dr-xr-xr-x 333 root   root0 Mar 20 20:33 proc
drwx--  29 root   root 4.0K Mar 21 09:05 root
drwxr-xr-x  51 root   root 1.5K Mar 21 08:36 run
drwxr-xr-x   2 root   root 4.0K Mar 21 08:36 sbin
drwxr-xr-x  20 root   root 4.0K Dec 26  2022 snap
drwxr-xr-x   4 root   root 4.0K Aug 11  2023 srv
drwxr-xr-x   4 wilson frontrow 4.0K Mar 18 17:02 storage
drwxr-xr-x   2 root   root 4.0K May 27  2019 storage-new
drwxr-xr-x   5 root   root 4.0K Jan  7  2023 storage.old
-rw---   1 root   root 2.0G May 26  2018 swapfile
dr-xr-xr-x  13 root   root0 Mar 20 20:33 sys
drwxrwxrwt  21 root   root 4.0K Mar 21 14:09 tmp
drwxr-xr-x  15 root   root 4.0K Dec 26  2022 usr
drwxr-xr-x  17 root   root 4.0K Mar 13 12:57 var
lrwxrwxrwx   1 root   root   31 Sep 30  2021 vmlinuz -> 
boot/vmlinuz-4.15.0-159-generic
lrwxrwxrwx   1 root   root   31 Sep 30  2021 vmlinuz.old -> 
boot/vmlinuz-4.15.0-158-generic


# ls -lh "/lib/ld-linux.so.2.usr-is-merged" "/lib/ld-linux.so.2"
ls: cannot access '/lib/ld-linux.so.2.usr-is-merged': No such file or directory
ls: cannot access '/lib/ld-linux.so.2': No such file or directory

# ls -lat /lib
total 152
drwxr-xr-x 19 root root  4096 Mar 21 08:36 .
drwxr-xr-x  2 root root  4096 Mar 21 08:36 i386-linux-gnu
drwxr-xr-x 30 root root  4096 Mar 21 08:36 ..
drwxr-xr-x 51 root root  4096 Mar 19 16:33 modules
drwxr-xr-x  2 root root  4096 Mar 18 17:05 udev
drwxr-xr-x 90 root root 69632 Mar 18 17:04 firmware
drwxr-xr-x  2 root root  4096 Mar 18 17:04 ifupdown
drwxr-xr-x  3 root root 12288 Mar 18 17:04 x86_64-linux-gnu
drwxr-xr-x  4 root root  4096 Mar 18 17:03 systemd
drwxr-xr-x  2 root root  4096 Nov 19 13:13 netplan
drwxr-xr-x  2 root root  4096 Aug 18  2023 ufw
lrwxrwxrwx  1 root root17 Dec 26  2022 apparmor -> /usr/lib/apparmor
lrwxrwxrwx  1 root root19 Dec 26  2022 modprobe.d -> /usr/lib/modprobe.d
lrwxrwxrwx  1 root root22 Dec 26  2022 recovery-mode -> 
/usr/lib/recovery-mode
lrwxrwxrwx  1 root root16 Dec 26  2022 apcupsd -> /usr/lib/apcupsd
lrwxrwxrwx  1 root root13 Dec 26  2022 init -> /usr/lib/init
lrwxrwxrwx  1 root root45 Dec 26  2022 klibc-K8e6DOmVI9JpyGMLR7qNe5iZeBk.so 
-> /usr/lib/klibc-K8e6DOmVI9JpyGMLR7qNe5iZeBk.so
drwxr-xr-x  2 root root  4096 Dec 26  2022 brltty
drwxr-xr-x  3 root root  4096 Dec 26  2022 crda
drwxr-xr-x  2 root root  4096 Dec 26  2022 hdparm
drwxr-xr-x  2 root root  4096 Dec 26  2022 linux-sound-base
drwxr-xr-x  3 root root  4096 Dec 26  2022 lsb
drwxr-xr-x  2 root root  4096 Dec 26  2022 console-setup
drwxr-xr-x  2 root root  4096 Dec 26  2022 resolvconf
drwxr-xr-x 16 root root  4096 Oct  4  2021 terminfo
lrwxrwxrwx  1 root root21 Oct 16  2018 cpp -> /etc/alternatives/cpp

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Corpora-List] [CfP] Deadline extended: Workshop on Reclaiming the Narrative: Digital Recovery, AI & Mitigating Harm in Social Media @ ICWSM 2024

2024-03-21 Thread Steve Wilson via Corpora

Join us for the 1st workshop on “Reclaiming the Narrative: Digital Recovery, AI 
& Mitigating Harm in Social Media” at ICWSM! 

If you work in harm reduction, NLP, AI, Social Sciences, recovery, HCI, and 
adjacent narrative studies, this one’s for you!
* When: June 3, 2024.
* Format: Hybrid (@Buffalo, NY and Zoom)
* [NEW] Submission deadline extended to: April 1

We invite submissions of abstracts (2 pages), as well as Long (8 pages) and 
Short (4 pages) papers, excluding references and appendices. The Long and Short 
papers will be included in the ICWSM Workshop proceedings, published by AAAI 
Press. 

For more details, please visit  
https://sites.google.com/view/reclaiming-the-narrative/___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

Re: [Servercert-wg] [External Sender] Re: [EXTERNAL]- Subject attribute encoding order requirement (rationale for)

2024-03-21 Thread Clint Wilson via Servercert-wg

Hi Adriano,

I haven’t looked through minutes and such yet, but as I recall this ordering 
was discussed a number of times on Validation Subcommittee calls during the 
creation of SC-062 (i.e. sometime in 2020-2023). The resultant ordering 
originated from the combination of 3 primary sources:
1. X.509/X.520
2. RFC 5280
3. WG Consensus

I think there’s additional discussion in the link that Jaime provided that’s 
relevant as well:

chrisbn May 13, 2022
How would fields need to be handled that are not in the current list? E.g. 
subject:businessCategory or subject:jurisdictionLocalityName from EVG? I'm also 
interested to know if there's a source for this requirement, or what's the 
driver for the ordering?

sleevi May 13, 2022
You mean, where would these be sorted?
These are requirements derived from the semantics of RFC 5280 and X.509. A DN 
is hierarchical in semantic naming, and an RDN with multiple elements is saying 
that these names are semantically equivalent hierarchically.
For the name forms listed, they are not semantically equivalent (e.g. a 
countryName is not the same hierarchy as a localityName / interchangeable 
with), and there is a semantic hierarchy.
These are already existing logical requirements, just being made explicit.

chrisbn May 13, 2022
Yes, I wonder about the order of fields not in this list.
I understand the hierarchy to order logic, but is the order defined in Section 
7.1.4.2 based on an existing specification, or how did we come to this ordering?

sleevi May 13, 2022
It is based on the definitions within X.509 and X.520, given these fields are 
generally geographical in nature.
That said, there’s definitely flexibility here to get us closer to consistency 
among CAs, which is a key point of profiling, so if there are changes and 
concerns, it’s totally appropriate to highlight.
Prior relevant art includes RFC 2377 
[https://datatracker.ietf.org/doc/html/rfc2377], RFC 1218 
[https://www.rfc-editor.org/rfc/rfc1218.html], and RFC 1255 
[https://www.rfc-editor.org/rfc/rfc1255]

Cheers,
-Clint

> On Mar 21, 2024, at 2:06 AM, Adriano Santoni via Servercert-wg 
>  wrote:
> 
> Thank you Jaime , but I had already checked that.
> 
> At that link I can only find the following very short exchange between 
> chrisbn and sleevi:
> 
> 
>> @chrisbn chrisbn May 13, 2022
>> Yes, I wonder about the order of fields not in this list.
>> I understand the hierarchy to order logic, but is the order defined in 
>> Section 7.1.4.2 based on an existing specification, or how did we come to 
>> this ordering?
>> @sleevi sleevi May 13, 2022
>> It is based on the definitions within X.509 and X.520, given these fields 
>> are generally geographical in nature.
>> That said, there’s definitely flexibility here to get us closer to 
>> consistency among CAs, which is a key point of profiling, so if there are 
>> changes and concerns, it’s totally appropriate to highlight.
> 
> That does not seem to clarify much, so I suppose there is more somewhere else.
> 
> No discussion of the mailing list? No discussion in SCWG calls?
> 
> Adriano
> 
> 
> 
> 
> 
> Il 21/03/2024 09:52, Jaime Hablutzel ha scritto:
>> The discussion in 
>> https://github.com/sleevi/cabforum-docs/pull/36#discussion_r872103477 could 
>> help.
>> 
>>> On 21 Mar 2024, at 09:39, Adriano Santoni via Servercert-wg 
>>>   wrote:
>>> 
>>> All, can anyone help me find the past email discussion, or at least the 
>>> rationale that someone wrote somewhere (e.g. on Github?), supporting the 
>>> Subject attributes encoding relative order requirement that was introduced 
>>> in BR 2.0.0 (Ballot SC-062) ? 
>>> 
>>> I am talking about §7.1.4.2 Subject Attribute Encoding, and specifically 
>>> about this language:
>>> 
>>> "CAs that include attributes in the Certificate subject field that are 
>>> listed in the table below
>>> SHALL encode those attributes in the relative order as they appear in the 
>>> table and follow the
>>> specified encoding requirements for the attribute."
>>> 
>>> I do not recall, and cannot find, a discussion on this mailing list on this 
>>> particular topic. Maybe I just missed a whole bunch of email messages due 
>>> to some otherwise undetected email problem. I also did a search on Github, 
>>> starting from the links provided at 
>>> https://cabforum.org/2023/03/17/ballot-sc62v2-certificate-profiles-update/),
>>>  but was unable to figure out who proposed it and, above all, for what 
>>> reason.
>>> 
>>> Adriano
>>> ___
>>> Servercert-wg mailing list
>>> Servercert-wg@cabforum.org 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.cabforum.org_mailman_listinfo_servercert-2Dwg=DwICAg=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM=-bX5hBm1IdRDykQ-dBR8tsFRCM4v1VXUyG7RZa2WqPY=TmnUymVu4aN7JJUi7E4FNf5W7JAuYX7-j6JtyhXK9EAAxJqhk7RvTa9sOsMmibge=pzZ-HMcq_CggzRO87gqT5_XxYy9n5hIbsxrERd7c_so=
>> 
>

Re: [cabfpub] Discussion Period Begins | Ballot FORUM-021: Form Definitions and Glossary WG

2024-03-21 Thread Ben Wilson via Public

Looks good to me.
Ben

On Thu, Mar 21, 2024 at 9:00 AM Clint Wilson via Public 
wrote:

> *Ballot FORUM-021*
>
> Proposed by Clint Wilson of Apple and endorsed by Tim Hollebeek of
> DigiCert and Tim Callan of Sectigo.
>
> *Purpose of Ballot*
>
> The CA/Browser Forum publishes Final Guidelines representing technical
> requirements about nuanced and challenging PKI implementations. It is
> proposed that the establishment of a Definitions and Glossary Working Group
> will assist the Forum as a whole, and its individual Chartered Working
> Groups, in the following ways:
>
> 1. *Clarity and Consistency*: Standardizing the definitions of terms will
> help Members and other interested parties have a clearer understanding of
> the terminology being used. This should reduce ambiguity and confusion,
> while increasing consistency in interpretation and use across Working
> Groups and Final Guidelines.
> 2. *Effective Communication*: A Glossary enables more effective
> communication among Members, as well as with external stakeholders such as
> industry partners, regulatory bodies, and other standardization
> organizations. It helps to ensure that everyone involved in the process is
> speaking the same language and, as such, may have a positive impact beyond
> the Forum alone.
> 3. *Quality*: By establishing a Glossary, the Forum can focus efforts on
> enhancing the quality and accuracy of the language used in published
> Guidelines. The availability of consistent, high-quality terminology
> reduces the risk of misunderstandings, errors, and misinterpretations that
> could undermine the effectiveness of the Forum.
> 4. *Accessibility and Learning*: For new Members or observers of the
> Forum, having a centralized Glossary provides a valuable resource for
> learning the specialized terminology used here. As with Guidelines in
> general, a focused Glossary can reduce the learning curve associated with
> understanding, implementing, and complying with complex baseline
> requirements documents.
> 5. *Cross-referencing and Interoperability*: A well-defined Glossary
> facilitates cross-referencing between Guidelines and promotes
> interoperability between the Forum’s Chartered Working Groups as well as
> external systems, products, processes, and people that rely on mutual
> understanding of shared terminology.
> 6. *Feedback and Iterative Improvement*: Building and maintaining a
> Glossary provides a framework for soliciting and receiving feedback from
> industry stakeholders and continuously improving the clarity and accuracy
> of the definitions over time. As new terms emerge or existing definitions
> evolve, the Glossary can be updated, ensuring that the Forum remains
> current and responsive to industry changes.
>
> *Following the passage of this ballot:*
>
>
>- A new Definitions and Glossary Chartered Working Group will be
>formed under the CA/Browser Forum, as outlined in section 5.3.1 of the
>Bylaws;
>- A Mailing list(s), GitHub repository(ies), and Wiki resource(s) will
>be established as needed to enable the D WG to fulfill its charter;
>- The D WG will collaborate with other CWGs in the Forum as
>stipulated in the charter found below; and
>- The D WG will produce and maintain a Glossary document.
>
>
> *MOTION BEGINS*
>
> *Establish Definitions and Glossary Working Group*
>
> Upon approval from the CA/Browser Forum by ballot in accordance with
> section 5.3 of the Forum Bylaws, the Definitions and Glossary Working Group
> (“DGWG”) is created to perform the activities as specified in the Charter
> as found here:
> https://github.com/cabforum/forum/compare/9805b6976e7a7ac391048d4eadb4379aa956110b...2b2b081a224031050aedf9404d9ce50344a468e8
>
> *MOTION ENDS*
>
> *The procedure for approval of this ballot is as follows:*
>
> *Discussion* (7+ days)
>
> *Start Time*: 2024-Mar-21 15:00 UTC
> *End Time*: After 2024-Mar-28 15:00 UTC
>
> *Vote for approval* (7 days)
>
> Start Time: TBD
> End Time: TBD
> ___
> 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

[cabfpub] Discussion Period Begins | Ballot FORUM-021: Form Definitions and Glossary WG

2024-03-21 Thread Clint Wilson via Public

Ballot FORUM-021

Proposed by Clint Wilson of Apple and endorsed by Tim Hollebeek of DigiCert and
Tim Callan of Sectigo.

Purpose of Ballot

The CA/Browser Forum publishes Final Guidelines representing technical
requirements about nuanced and challenging PKI implementations. It is proposed
that the establishment of a Definitions and Glossary Working Group will assist
the Forum as a whole, and its individual Chartered Working Groups, in the
following ways:

1. Clarity and Consistency: Standardizing the definitions of terms will help
Members and other interested parties have a clearer understanding of the
terminology being used. This should reduce ambiguity and confusion, while
increasing consistency in interpretation and use across Working Groups and
Final Guidelines.
2. Effective Communication: A Glossary enables more effective communication
among Members, as well as with external stakeholders such as industry partners,
regulatory bodies, and other standardization organizations. It helps to ensure
that everyone involved in the process is speaking the same language and, as
such, may have a positive impact beyond the Forum alone.
3. Quality: By establishing a Glossary, the Forum can focus efforts on
enhancing the quality and accuracy of the language used in published
Guidelines. The availability of consistent, high-quality terminology reduces
the risk of misunderstandings, errors, and misinterpretations that could
undermine the effectiveness of the Forum.
4. Accessibility and Learning: For new Members or observers of the Forum,
having a centralized Glossary provides a valuable resource for learning the
specialized terminology used here. As with Guidelines in general, a focused
Glossary can reduce the learning curve associated with understanding,
implementing, and complying with complex baseline requirements documents.
5. Cross-referencing and Interoperability: A well-defined Glossary facilitates
cross-referencing between Guidelines and promotes interoperability between the
Forum’s Chartered Working Groups as well as external systems, products,
processes, and people that rely on mutual understanding of shared terminology.
6. Feedback and Iterative Improvement: Building and maintaining a Glossary
provides a framework for soliciting and receiving feedback from industry
stakeholders and continuously improving the clarity and accuracy of the
definitions over time. As new terms emerge or existing definitions evolve, the
Glossary can be updated, ensuring that the Forum remains current and responsive
to industry changes.

Following the passage of this ballot:

A new Definitions and Glossary Chartered Working Group will be formed under the
CA/Browser Forum, as outlined in section 5.3.1 of the Bylaws;
A Mailing list(s), GitHub repository(ies), and Wiki resource(s) will be
established as needed to enable the D WG to fulfill its charter;
The D WG will collaborate with other CWGs in the Forum as stipulated in the
charter found below; and
The D WG will produce and maintain a Glossary document.

MOTION BEGINS

Establish Definitions and Glossary Working Group

Upon approval from the CA/Browser Forum by ballot in accordance with section
5.3 of the Forum Bylaws, the Definitions and Glossary Working Group (“DGWG”) is
created to perform the activities as specified in the Charter as found here:
https://github.com/cabforum/forum/compare/9805b6976e7a7ac391048d4eadb4379aa956110b...2b2b081a224031050aedf9404d9ce50344a468e8

MOTION ENDS

The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: 2024-Mar-21 15:00 UTC
End Time: After 2024-Mar-28 15:00 UTC

Vote for approval (7 days)

Start Time: TBD
End Time: TBD

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

[Bug 2058648] Re: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz u

Attempted removing diversions:

# dpkg-divert --quiet --remove --rename --package base-files --divert 
"/lib.usr-is-merged" "/lib"
# dpkg-divert --quiet --remove --rename --divert 
"/lib/ld-linux.so.2.usr-is-merged" "/lib/ld-linux.so.2"

# apt-get install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libopts25 php8.2-mysql sntp
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libc6
Suggested packages:
  glibc-doc
The following packages will be upgraded:
  libc6
1 upgraded, 0 newly installed, 0 to remove and 2382 not upgraded.
10 not fully installed or removed.
Need to get 0 B/3,262 kB of archives.
After this operation, 172 kB disk space will be freed.
Do you want to continue? [Y/n] y
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found 
(required by locale)
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found 
(required by locale)
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found 
(required by locale)
Preconfiguring packages ...
(Reading database ... 361971 files and directories currently installed.)
Preparing to unpack .../libc6_2.39-0ubuntu2_amd64.deb ...
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found 
(required by locale)
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found 
(required by locale)
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found 
(required by locale)
Checking for services that may need to be restarted...
Checking init scripts...
Checking for services that may need to be restarted...
Checking init scripts...
Stopping some services possibly affected by the upgrade (will be restarted 
later):

dpkg-divert: error: cannot divert directories

Use --help for help about diverting files.
dpkg: error processing archive 
/var/cache/apt/archives/libc6_2.39-0ubuntu2_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned error exit 
status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.39-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648

Title:
  package libc6 2.35-0ubuntu3.6 [modified:
  usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz
  usr/share/doc/libc6/README.hesiod.gz
  usr/share/doc/libc6/changelog.Debian.gz
  usr/share/lintian/overrides/libc6] failed to install/upgrade: new
  libc6:amd64 package pre-installation script subprocess returned error
  exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions


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

[Bug 2058648] [NEW] package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz

Public bug reported:

Doing upgrade from 22.04 -> 24.04 beta.

Upgrading
Fetched 0 B in 0s (0 B/s)
   Upgrading: libnih1:amd64 < 1.0.3-12build1 @ii mK Ib > due to libnih1:amd64 
Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU Ib > (< 2.36)
   Upgrading: libc6-x32:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii ugH Ib > 
due to libc6-x32:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 
2.39-0ubuntu2 @ii umU Ib > (= 2.35-0ubuntu3.6)
   Upgrading: libc6-i386:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii ugH Ib > 
due to libc6-i386:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 
2.39-0ubuntu2 @ii umU Ib > (= 2.35-0ubuntu3.6)
   Upgrading: libc6-dev:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii umH Ib > 
due to libc6-dev:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 
2.39-0ubuntu2 @ii umU Ib > (= 2.35-0ubuntu3.6)
   Upgrading: libc6-dbg:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii umH Ib > 
due to libc6-dbg:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 
2.39-0ubuntu2 @ii umU Ib > (= 2.35-0ubuntu3.6)
   Upgrading: libc-dev-bin:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii umH NPb 
Ib > due to libc-dev-bin:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 
2.39-0ubuntu2 @ii umU Ib > (< 2.36)
   Upgrading: libc-bin:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii umH Ib > due 
to libc-bin:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii 
umU Ib > (< 2.36)
  MarkInstall libc6:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU Ib > FU=1
MarkInstall locales:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU Ib > 
FU=0
Installing libc-bin:amd64 as Depends of locales:amd64
  MarkInstall libc-bin:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU > 
FU=0
MarkInstall libc6:i386 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU > FU=0
MarkInstall libnih1:amd64 < 1.0.3-12build1 @ii mK Ib > FU=0
  libnih1:amd64 Depends on libc6:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 
@ii pumU > (< 2.36) can't be satisfied! (dep)
   Removing: libnih1:amd64 as upgrade is not possible
MarkDelete libnih1:amd64 < 1.0.3-12build1 @ii mK Ib > FU=0
 Upgrading: libc6-dev-x32:amd64 < 2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii ugH 
NPb IPb > due to libc6-dev-x32:amd64 Depends on libc6-x32:amd64 < 
2.35-0ubuntu3.6 | 2.39-0ubuntu2 @ii ugH Ib > (= 2.35-0ubuntu3.6)
MarkInstall libc6-x32:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii ugU > 
FU=0
  MarkInstall libc6-dev-x32:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii 
ugU NPb Ib > FU=0
  Installing libc6-dev-i386:amd64 as Depends of libc6-dev-x32:amd64
MarkInstall libc6-dev-i386:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii 
ugU NPb Ib > FU=0
  MarkInstall libc6-dev:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii 
umU Ib > FU=0
  Installing libc-dev-bin:amd64 as Depends of libc6-dev:amd64
MarkInstall libc-dev-bin:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 
@ii umU NPb IPb > FU=0
ignore old unsatisfied important dependency on libc-devtools:amd64
Installing libc6-i386:amd64 as Depends of libc6-dev-i386:amd64
  MarkInstall libc6-i386:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii 
ugU > FU=0
ignore old unsatisfied important dependency on gcc-multilib:amd64
  ignore old unsatisfied important dependency on gcc-multilib:amd64
MarkInstall libc6-dbg:amd64 < 2.35-0ubuntu3.6 -> 2.39-0ubuntu2 @ii umU > 
FU=0
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) ureadahead:amd64 < 0.100.0-21 @ii mK Ib >
Broken ureadahead:amd64 Depends on libnih1:amd64 < 1.0.3-12build1 @ii mR > (>= 
1.0.0)
  Considering libnih1:amd64 0 as a solution to ureadahead:amd64 -2
  Removing ureadahead:amd64 rather than change libnih1:amd64
  MarkDelete ureadahead:amd64 < 0.100.0-21 @ii mK Ib > FU=0
Done

Upgrading
Fetched 0 B in 0s (0 B/s)
Preconfiguring packages ...
Preconfiguring packages ...
Preconfiguring packages ...
(Reading database ... 361984 files and directories currently installed.)
Removing ureadahead (0.100.0-21) ...
Removing libnih1 (1.0.3-12build1) ...

Progress: [  6%]
(Reading database ... 361965 files and directories currently installed.)
Preparing to unpack .../00-libc6-i386_2.39-0ubuntu2_amd64.deb ...
Unpacking libc6-i386 (2.39-0ubuntu2) over (2.35-0ubuntu3.6) ...

Progress: [ 12%]
Preparing to unpack .../01-libc-dev-bin_2.39-0ubuntu2_amd64.deb ...
Unpacking libc-dev-bin (2.39-0ubuntu2) over (2.35-0ubuntu3.6) ...
Preparing to unpack .../02-libc6-dev_2.39-0ubuntu2_amd64.deb ...

Progress: [ 18%]
Unpacking libc6-dev:amd64 (2.39-0ubuntu2) over (2.35-0ubuntu3.6) ...
Replacing files in old package libc6:amd64 (2.35-0ubuntu3.6) ...
Preparing to unpack .../03-libc6-dev-i386_2.39-0ubuntu2_amd64.deb ...
Unpacking libc6-dev-i386 (2.39-0ubuntu2) over (2.35-0ubuntu3.6) ...

Progress: [ 24%]
Preparing to unpack .../04-libc6-dev-x32_2.39-0ubuntu2_amd64.deb ...
Unpacking libc6-dev-x32 (2.39-0ubuntu2) over (2.35-0ubuntu3.6) ...
Preparing to unpack

Re: PESO: A strange looking bird

2024-03-20 Thread mike wilson

Saw it.  Twice.
> On 20/03/2024 09:14 GMT Alan C  wrote:
> 
>  
> Won't go. Trying again.
> 
> On 20-Mar-24 06:53 AM, Alan C wrote:
> > An African Snake Darter at Lake Panic, near Skukuza Camp, Kruger Park. 
> > Unfortunately back lit. These birds are closely related to Cormorants 
> > but swim with their bodies totally immersed giving the impression of a 
> > swimming snake. The second image (by a fellow photographer, Ian van 
> > Romburgh) shows that very well.
> >
> > https://www.flickr.com/photos/wisselstroom/53599214819/
> >
> > https://www.flickr.com/photos/wisselstroom/51790648710/
> >
> > K5 & Sigma 170-500 DG
> --
> %(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.
--
%(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: [Servercert-wg] Ballot to introduce linting in the TLS BRs

2024-03-19 Thread Ben Wilson via Servercert-wg

Hi Dimitris,
You can add me.
Thanks,
Ben

On Tue, Mar 19, 2024 at 9:01 AM Dimitris Zacharopoulos (HARICA) via
Servercert-wg  wrote:

>
>
> On 19/3/2024 5:27 π.μ., Corey Bonnell wrote:
>
> Hi Dimitris,
>
> I’d be happy to endorse and help flesh out the language.
>
>
> Thank you Corey, I added your name on the table with future ballots. Is
> there anyone else?
>
>
> Best regards,
> Dimitris.
>
>
>
> Thanks,
>
> Corey
>
>
>
> *From:* Servercert-wg 
>  *On Behalf Of *Dimitris
> Zacharopoulos (HARICA) via Servercert-wg
> *Sent:* Sunday, March 17, 2024 8:20 AM
> *To:* CA/B Forum Server Certificate WG Public Discussion List
>  
> *Subject:* [Servercert-wg] Ballot to introduce linting in the TLS BRs
>
>
>
> Hi all,
>
> This is still very draft
> 
> based on the latest F2F. I would like to ask for 2 endorsers so we can work
> on the details of the ballot language in the next few of weeks.
>
>
> Thank you,
> 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: [Servercert-wg] Discussion Period Begins - Ballot SC-067 V1: "Require domain validation and CAA checks to be performed from multiple Network Perspectives”

2024-03-19 Thread Ben Wilson via Servercert-wg

Greetings Antti,
Somehow, our group (working on the Subscriber Agreement/Terms of Use
ballot) had selected ballot number 67 on the wiki, but there were two
different wiki pages with ballot numbers that people were unaware of (which
led to a second selection of #67 by Chris and Ryan).  So Dustin, Tadahiko,
and I decided to go with SC-071 (the next unallocated one) for our ballot.
Ben

On Mon, Mar 18, 2024 at 11:19 PM Backman, Antti via Servercert-wg <
servercert-wg@cabforum.org> wrote:

> Hi Chris
>
>
>
> Could there be a numbering clash with this ballot and the one being worked
> on by Ben Wilson?
>
>
>
> “[Servercert-wg] Draft Ballot SC-067: Applicant, Subscriber and Subscriber
> Agreements - Feedback r”
>
> As I am not completely sure how ballot numbering should work out, can the
> numbers be recycled or how that pans out?
>
>
>
>
>
>
>
> //Antti
>
>
>
> *From: *Servercert-wg  on behalf of
> Chris Clements via Servercert-wg 
> *Date: *Monday, 18. March 2024 at 17.32
> *To: *CA/B Forum Server Certificate WG Public Discussion List <
> servercert-wg@cabforum.org>
> *Subject: *[Servercert-wg] Discussion Period Begins - Ballot SC-067 V1:
> "Require domain validation and CAA checks to be performed from multiple
> Network Perspectives”
>
> *Purpose of Ballot SC-067*:
>
>
>
> This Ballot proposes updates to the *Baseline Requirements for the
> Issuance and Management of Publicly-Trusted TLS Server Certificates*
> (i.e., TLS BRs) related to “Multi-Perspective Issuance Corroboration”
> (“MPIC”).
>
>
>
> *Background*:
>
>
>
> - MPIC refers to performing domain validation and CAA checks from multiple
> Network Perspectives before certificate issuance, as described within the
> Ballot for the applicable validation methods in TLS BR Sections 3.2.2.4 and
> 3.2.2.5.
>
> - Not all methods described in TLS BR Sections 3.2.2.4 and 3.2.2.5 will
> require using MPIC.
>
> - This work was most recently motivated by research presented at
> Face-to-Face 58 [1] by Princeton University, but has been discussed for
> years prior as well.
>
> - The goal of this proposal is to make it more difficult for adversaries
> to successfully launch equally-specific prefix attacks against the domain
> validation processes described in the TLS BRs.
>
> - Additional background information can be found in an update shared at
> Face-to-Face 60 [2].
>
>
>
> *Benefits of Adoption*:
>
>
>
> - Recent publicly-documented attacks have used BGP hijacks to fool domain
> control validation and obtain malicious certificates, which led to the
> impersonation of HTTPS websites [3][4].
>
> - Routing security defenses (e.g., RPKI) can mitigate the risk of global
> BGP attacks, but localized, equally-specific BGP attacks still pose a
> significant threat to the Web PKI [5][6].
>
> - Corroborating domain control validation checks from multiple network
> perspectives (i.e., MPIC) spread across the Internet substantially reduces
> the threat posed by equally-specific BGP attacks, ensuring the integrity of
> domain validation and issuance decisions [5][7][8].
>
> - Existing deployments of MPIC at the scale of millions of certificates a
> day demonstrate the feasibility of this technique at Internet scale [7][9].
>
>
>
> *Intellectual Property (IP) Disclosure*:
>
>
>
> - While not a Server Certificate Working Group Member, researchers from
> Princeton University presented at Face-to-Face 58, provided academic
> expertise, and highlighted publicly-available peer-reviewed research to
> support Members in drafting this ballot.
>
> - The Princeton University researchers indicate that they have not filed
> for any patents relating to their MPIC work and do not plan to do so in the
> future.
>
> - Princeton University has indicated that it is unable to agree to the
> CA/Browser Forum IPR agreement because it could encumber inventions
> invented by researchers not involved in the development of MPIC or with the
> CA/B Forum.
>
> - Princeton University has instead provided the attached IPR statement.
> Pursuant to the IPR statement, Princeton University has granted a worldwide
> royalty free license to the intellectual property in MPIC developed by the
> researchers and has made representations regarding its lack of knowledge of
> any other Princeton intellectual property needed to implement MPIC.
>
> - For clarity, Princeton University’s IPR statement is NOT intended to
> replace the Forum’s IPR agreement or allow Princeton to participate in the
> Forum in any capacity.
>
> - Members seeking legal advice regarding this ballot should consult their
> own counsel.
>
>
>
> *Proposal Revis

Re: [go-cd] SCM VALIDATE FAILED

2024-03-19 Thread Chad Wilson

 />\n  GOINPUTNAME[password].$error.server\">{{
> GOINPUTNAME[password].$error.server }}\n\n form_item_block\">\n Default Branch:\n  ng-model=\"defaultBranch\" ng-required=\"false\"/>\n  form_error\" ng-show=\"GOINPUTNAME[defaultBranch].$error.server\">{{
> GOINPUTNAME[defaultBranch].$error.server }}\n\n form_item_block\">\n Whitelisted branches:\n  text\" ng-model=\"branchwhitelist\" ng-required=\"false\"/>\n  \"form_error\" ng-show=\"GOINPUTNAME[branchwhitelist].$error.server\">{{
> GOINPUTNAME[branchwhitelist].$error.server }}\n\n \"form_item_block\">\n Blacklisted branches:\n  \"text\" ng-model=\"branchblacklist\" ng-required=\"false\"/>\n  class=\"form_error\" ng-show=\"GOINPUTNAME[branchblacklist].$error.server
> \">{{ GOINPUTNAME[branchblacklist].$error.server }}\n\n"
> }
> }
> } ]
> }, {
> "_links" : {
> "self" : {
> "href" : "https://serverurl.com/go/api/admin/plugin_info/github.pr;
> },
> "doc" : {
> "href" : "https://api.gocd.org/23.3.0/#plugin-info;
> },
> "find" : {
> "href" : "https://serverurl.com/go/api/admin/plugin_info/:id;
> }
> },
> "id" : "github.pr",
> "status" : {
> "state" : "active"
> },
> "plugin_file_location" :
> "/var/lib/go-server/plugins/external/github-pr-poller-1.4.0-RC4.jar",
> "bundled_plugin" : false,
> "about" : {
> "name" : "Github Pull Requests Builder",
> "version" : "1.4.0-RC4",
> "target_go_version" : "15.1.0",
> "description" : "Plugin that polls a GitHub repository for pull requests
> and triggers a build for each of them",
> "target_operating_systems" : [ ],
> "vendor" : {
> "name" : "Ashwanth Kumar",
> "url" : "https://github.com/ashwanthkumar/gocd-build-github-pull-requests;
> }
> },
> "extensions" : [ {
> "type" : "scm",
> "display_name" : "Github",
> "scm_settings" : {
> "configurations" : [ {
> "key" : "url",
> "metadata" : {
> "secure" : false,
> "required" : true,
> "part_of_identity" : true
> }
> }, {
> "key" : "username",
> "metadata" : {
> "secure" : false,
> "required" : false,
> "part_of_identity" : false
> }
> }, {
> "key" : "password",
> "metadata" : {
> "secure" : true,
> "required" : false,
> "part_of_identity" : false
> }
> }, {
> "key" : "defaultBranch",
> "metadata" : {
> "secure" : false,
> "required" : false,
> "part_of_identity" : false
> }
> }, {
> "key" : "shallowClone",
> "metadata" : {
> "secure" : false,
> "required" : false,
> "part_of_identity" : false
> }
> } ],
> "view" : {
> "template" : "\n URL: asterisk\">*\n  ng-required=\"true\"/>\n  GOINPUTNAME[url].$error.server\">{{ GOINPUTNAME[url].$error.server }}
> \n\n\n
> Username:\n  new-password\" ng-model=\"username\" ng-required=\"false\"/>\n  class=\"form_error\" ng-show=\"GOINPUTNAME[username].$error.server\">{{
> GOINPUTNAME[username].$error.server }}\n\n form_item_block\">\n Password:\n  autocomplete=\"new-password\" ng-model=\"password\" ng-required=\"false\"
> />\n  GOINPUTNAME[password].$error.server\">{{
> GOINPUTNAME[password].$error.server }}\n\n form_item_block\">\n Default Branch:\n  ng-model=\"defaultBranch\" ng-required=\"false\"/>\n  form_error\" ng-show=\"GOINPUTNAME[defaultBranch].$error.server\">{{
> GOINPUTNAME[defaultBranch].$error.server }}\n\n"
> }
> }
> } ]
> } ]
> }
> }%
> as you requested i shared the response here
> On Tuesday, March 19, 2024 at 12:58:39 PM UTC+5:30 Chad Wilson wrote:
>
>> Yes, the browser is not sending the correct data - probably for the same
>> reason I talked about. If the plugin, browser or server is not working
>> correctly, nothing you enter will work.
>>
>> Please share the response from */go/api/admin/plugin_info?type=scm* as I
>> requested below
>> *.*

Re: [go-cd] SCM VALIDATE FAILED

2024-03-19 Thread Chad Wilson

There is nothing you should *need* to configure that affects seeing those
raw template values like {{ GOINPUTNAME['url'].$error.server }} . You
should never see these - it means there is a problem in how your browser is
loading the plugin view and displaying plugin responses to you. We need to
find what is breaking the plugin view and fix that. When the plugin view is
working correctly you should see just errors like this:

[image: image.png]
I only have another couple of suggestions

   - Make sure you don't have multiple versions of the plugin installed in
   the server's plugin directory. If you remove duplicate plugin versions,
   restart the server afterwards and see if it's different.
   - If you are already in the network tab, perhaps you can share the JSON
   response from */go/api/admin/plugin_info?type=scm* when you click on the
   Admin > Pluggable SCMs tab (in the environment that is broken). There is
   nothing sensitive in that API response.

Something seems to be wrong with either the plugin, the way you installed
it, but without looking at the browser console and my earlier questions we
would just be guessing where the problem is.

-Chad

On Tue, Mar 19, 2024 at 2:14 PM Suthar robert 
wrote:

> i check using the inspect, in the response of the network tab it require
> key and value in it. In a working environment which is local host it has
> the key and value in it, But in the configured url which i mean i deployed
> the gocd into the specific domain url in the server, in that environment it
> didn't have key and value present in it. Also i check the source code of
> the plugin and check it, in that source code plugin they have scm template
> html file which show extact like this error in it but they didn't mention
> clarification about it how to config those
>
> On Tuesday, March 19, 2024 at 11:38:13 AM UTC+5:30 Chad Wilson wrote:
>
>> Version 1.4.0 of the plugin has never been officially released, so I am
>> not sure if that is stable, but I do not get those errors with that version
>> either. Please try and be specific about the version you are using in
>> different environments - do you mean "1.4.0-RC4" from here
>> <https://github.com/ashwanthkumar/gocd-build-github-pull-requests/releases/tag/v1.4.0-RC4>,
>> or did you build/compile the plugin yourself? Are both your localhost GoCD
>> server and the "real" server the same GoCD version 23.3.0?
>>
>> I don't understand what you mean by "so here the problem when i launched
>> the config gocd which is have own url in it for security purpose", sorry,
>> so cannot comment on this right now.
>>
>> Regardless, check the browser console for errors, and check the browser
>> debugger "network" tab to see if requests under the "JS" and "XHR" types
>> are being blocked or failing. Disable the browser cache and do a full
>> reload and check again.
>>
>> -Chad
>>
>> On Tue, Mar 19, 2024 at 1:56 PM Suthar robert 
>> wrote:
>>
>>> In the same browser when i use localhost gocd server it working fine.
>>> The version plugin is 1.4.0, so here the problem when i launched the config
>>> gocd which is have own url in it for security purpose. It display like
>>> this, whoever visit this url and use this scm plugin it display the error.
>>> i need to resolve it
>>>
>>>
>>> On Tuesday, March 19, 2024 at 11:13:05 AM UTC+5:30 Chad Wilson wrote:
>>>
>>>> I can't replicate this problem, but it looks like something is wrong
>>>> with the plugin or your browser. Try another browser (Edge, Safari,
>>>> Firefox) or Chrome Incognito mode (without plugins/extensions) to see if
>>>> you get the same errors.
>>>>
>>>> If it works in another browser, or without extensions/plugins, you may
>>>> also want to check your browser debugger javascript console for errors, as
>>>> this error seems to imply that the admin user interface is not creating the
>>>> plugin view correctly - this logic is done within the browser with
>>>> Javascript.
>>>>
>>>> Which version of the plugin did you install? e.g from
>>>> http://localhost:8153/go/admin/plugins
>>>>
>>>> [image: image.png]
>>>>
>>>> -Chad
>>>>
>>>> On Tue, Mar 19, 2024 at 12:36 PM Suthar robert 
>>>> wrote:
>>>>
>>>>> [image: image.png]
>>>>> Sorry for That
>>>>> Here it is
>>>>>
>>>>>
>>>>>
>>>>> On Monday, March 18, 2024 at 6:47:46 PM UTC+5:30 Chad Wilson wrote

Re: [go-cd] SCM VALIDATE FAILED

2024-03-19 Thread Chad Wilson

Version 1.4.0 of the plugin has never been officially released, so I am not
sure if that is stable, but I do not get those errors with that version
either. Please try and be specific about the version you are using in
different environments - do you mean "1.4.0-RC4" from here
<https://github.com/ashwanthkumar/gocd-build-github-pull-requests/releases/tag/v1.4.0-RC4>,
or did you build/compile the plugin yourself? Are both your localhost GoCD
server and the "real" server the same GoCD version 23.3.0?

I don't understand what you mean by "so here the problem when i launched
the config gocd which is have own url in it for security purpose", sorry,
so cannot comment on this right now.

Regardless, check the browser console for errors, and check the browser
debugger "network" tab to see if requests under the "JS" and "XHR" types
are being blocked or failing. Disable the browser cache and do a full
reload and check again.

-Chad

On Tue, Mar 19, 2024 at 1:56 PM Suthar robert 
wrote:

> In the same browser when i use localhost gocd server it working fine. The
> version plugin is 1.4.0, so here the problem when i launched the config
> gocd which is have own url in it for security purpose. It display like
> this, whoever visit this url and use this scm plugin it display the error.
> i need to resolve it
>
>
> On Tuesday, March 19, 2024 at 11:13:05 AM UTC+5:30 Chad Wilson wrote:
>
>> I can't replicate this problem, but it looks like something is wrong with
>> the plugin or your browser. Try another browser (Edge, Safari, Firefox) or
>> Chrome Incognito mode (without plugins/extensions) to see if you get the
>> same errors.
>>
>> If it works in another browser, or without extensions/plugins, you may
>> also want to check your browser debugger javascript console for errors, as
>> this error seems to imply that the admin user interface is not creating the
>> plugin view correctly - this logic is done within the browser with
>> Javascript.
>>
>> Which version of the plugin did you install? e.g from
>> http://localhost:8153/go/admin/plugins
>>
>> [image: image.png]
>>
>> -Chad
>>
>> On Tue, Mar 19, 2024 at 12:36 PM Suthar robert 
>> wrote:
>>
>>> [image: image.png]
>>> Sorry for That
>>> Here it is
>>>
>>>
>>>
>>> On Monday, March 18, 2024 at 6:47:46 PM UTC+5:30 Chad Wilson wrote:
>>>
>>>> Sorry, I don't think the screenshot came through correctly - please try
>>>> again?
>>>>
>>>> On Mon, Mar 18, 2024 at 7:39 PM Suthar robert 
>>>> wrote:
>>>>
>>>>> Sure here i am using a gocd versoin = 23.3.0, plugins is git featrure
>>>>> plugin which is the link i provide here
>>>>> https://github.com/ashwanthkumar/gocd-build-github-pull-requests
>>>>>
>>>>> the browser i am using chrome
>>>>>
>>>>> when i click a create new pluggable scm, it automatically arises like
>>>>> this, when i enter the url and save it, it still says the validation 
>>>>> failed
>>>>>
>>>>>
>>>>> Here i added the screenshot below for clarification
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>>
>>>>>
>>>>> On Monday, March 18, 2024 at 3:36:18 PM UTC+5:30 Chad Wilson wrote:
>>>>>
>>>>>> It may help if you share screenshots of exactly what you are doing
>>>>>> and entering in the fields, as it's a bit difficult to understand what 
>>>>>> you
>>>>>> are seeing?
>>>>>>
>>>>>> Can you also share the versions of your GoCD server and plugins, plus
>>>>>> which browser you are using?
>>>>>>
>>>>>> On Mon, Mar 18, 2024 at 5:51 PM Suthar robert 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>> I am using a git feature plugin for my works here, for that i need
>>>>>>> to configure the scm plugin in it. So that i can able to use git feature
>>>>>>> plugin, i am a facing a problem here which is validate which return 
>>>>>>> without
>>>>>>> entering the value in the field which is like
>>>>>>>
>>>>>>> {{ GOINPUTNAME['url'].$error.server }}
>>>>>>> like this error for every input field. I don't know how to fix this.
>>>>>>>
>>>>>

[African Wikimedians] [WLA 2024 Training] Uploading Videos to Wikimedia Commons

2024-03-18 Thread Wilson Oluoha

Dear Friends,

As part of Wiki In Africa's plans to increase participants capacity,
encourage quality contributions and generally improve knowledge and skills
with regards to Wikimedia Commons, We wish to cordially invite *You *to the
first WLA training of the year.

*Details* are available on the event page
<https://meta.wikimedia.org/wiki/Event:Uploading_Videos_to_Wikimedia_Commons>.
Kindly register and share with members of your community.

Best regards

-- 

*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: [go-cd] SCM VALIDATE FAILED

2024-03-18 Thread Chad Wilson

Sorry, I don't think the screenshot came through correctly - please try
again?

On Mon, Mar 18, 2024 at 7:39 PM Suthar robert 
wrote:

> Sure here i am using a gocd versoin = 23.3.0, plugins is git featrure
> plugin which is the link i provide here
> https://github.com/ashwanthkumar/gocd-build-github-pull-requests
>
> the browser i am using chrome
>
> when i click a create new pluggable scm, it automatically arises like
> this, when i enter the url and save it, it still says the validation failed
>
>
> Here i added the screenshot below for clarification
>
> [image: image.png]
>
>
>
> On Monday, March 18, 2024 at 3:36:18 PM UTC+5:30 Chad Wilson wrote:
>
>> It may help if you share screenshots of exactly what you are doing and
>> entering in the fields, as it's a bit difficult to understand what you are
>> seeing?
>>
>> Can you also share the versions of your GoCD server and plugins, plus
>> which browser you are using?
>>
>> On Mon, Mar 18, 2024 at 5:51 PM Suthar robert 
>> wrote:
>>
>>> Hi all,
>>> I am using a git feature plugin for my works here, for that i need to
>>> configure the scm plugin in it. So that i can able to use git feature
>>> plugin, i am a facing a problem here which is validate which return without
>>> entering the value in the field which is like
>>>
>>> {{ GOINPUTNAME['url'].$error.server }}
>>> like this error for every input field. I don't know how to fix this.
>>>
>>> i am using a pluing this one
>>> https://github.com/ashwanthkumar/gocd-build-github-pull-requests
>>>
>>> --
>>> 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+un...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/fcdceb39-542b-41bd-ba34-244341f12a56n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/go-cd/fcdceb39-542b-41bd-ba34-244341f12a56n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/25f7ac83-a6a7-4f45-9eb7-133d456e94d8n%40googlegroups.com
> <https://groups.google.com/d/msgid/go-cd/25f7ac83-a6a7-4f45-9eb7-133d456e94d8n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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_TxK6kx4cbazfz1xccTorQbpei6wnwJ_%2BkSvfMG-0G4g%40mail.gmail.com.

Re: [go-cd] SCM VALIDATE FAILED

2024-03-18 Thread Chad Wilson

It may help if you share screenshots of exactly what you are doing and
entering in the fields, as it's a bit difficult to understand what you are
seeing?

Can you also share the versions of your GoCD server and plugins, plus which
browser you are using?

On Mon, Mar 18, 2024 at 5:51 PM Suthar robert 
wrote:

> Hi all,
> I am using a git feature plugin for my works here, for that i need to
> configure the scm plugin in it. So that i can able to use git feature
> plugin, i am a facing a problem here which is validate which return without
> entering the value in the field which is like
>
> {{ GOINPUTNAME['url'].$error.server }}
> like this error for every input field. I don't know how to fix this.
>
> i am using a pluing this one
> https://github.com/ashwanthkumar/gocd-build-github-pull-requests
>
> --
> 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/fcdceb39-542b-41bd-ba34-244341f12a56n%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/CAA1RwH94XC00jXm2ADKxPUA-S5Pe7jm%3DVt4T-Ni-8Scc5yozCQ%40mail.gmail.com.

Re: [AusNOG] That's not a cutover. THIS is a cutover!

2024-03-17 Thread Scott Wilson

Back in the day when I worked for Telstra Wholesale we did ISP cutovers
from Telstra ADSL to the Spectrum Share product. Teams of techs would go
into exchanges and cut them over, then hand over the FNN's to the teams in
the office to make the billing changes. Some poor schlub (...me) had to
compare the "remove" list with the "add" list (by hand, with a highlighter
pen!) to figure out if there were any "removes" without corresponding
"adds" - then fix the mistake.

Automating that comparison process was the first software I wrote where I
got paid for it.

On Sun, 17 Mar 2024 at 23:35, Mark Smith  wrote:

> Courtesy of Nathan@NZNOG.
>
> Where have the Gary Brannons of the industry gone? The hair, the moustache
> and those glasses!
>
> https://youtu.be/saRir95iIWk?si=oS1AjiSqcUnxmvKb
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> https://lists.ausnog.net/mailman/listinfo/ausnog
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
https://lists.ausnog.net/mailman/listinfo/ausnog

Re: [go-cd] git clone failures in gocd pipelines after sonoma upgrade

2024-03-16 Thread Chad Wilson

Is it always "kex_exchange_identification: Connection closed by remote
host" as the failure reason?

If so, it usually means the remote host is closing it before exchanging SSH
keys (maybe because of connection limits, or authentication problems), or
perhaps there is a firewall/network proxy or something else in between your
agent and the git repository host that is closing the connection from both
the git client and the git server's perspective.

I can't think of anything obvious that would have changed due just to the
MacOS upgrade, unless something has changed with firewall settings, or
other such software you have installed on the agents. Are you sure nothing
changed in the network environment your agents are deployed, or on the
Gitlab instance at the same time?

It looks like you are using SSH Git materials, so once you can replicate
with git commands directly on the agent you might need to use environment
variable GIT_SSH_COMMAND="ssh -vvv" to see all of the raw SSH debug
information (GIT_CURL_VERBOSE is for HTTPS connections). If you discover
something here you can probably google to debug it further.

*But the issue still exists. on the GoCD,  we are still using pre-installed
git, do I need install git with brew on the GoCD as well.*

If the problem is only on the agents, then no need to change things on the
servers, especially if using homebrew Git didn't change anything.

-Chad

On Sun, Mar 17, 2024 at 12:31 AM SATYA R  wrote:

> Hi Chad,
> Thank you for responding to my issue.
> Just wanted to give some basic info on the GoCD version.
> We are using GoCD 23.1.0 aarch version, all of our servers are Mac OS M1
> servers(for both GoCD and agents)
>
>- What are the specific clone errors you are getting?
>
>
>
>
>
>
>
>
>
>
> *we get the below error when the job tried to clone more the repositories,
> at first we thorught the git server is closing the connection, the gitlab
> team took the logs from ec2 instance where it says the source ip which is
> go-agent is requesting the disconnection.pipelines logs:STDERR: Cloning
> into
> '/Users//go-agent-23.1.0/pipelines/Git_Clone/daf-mock-server'...STDERR:
> kex_exchange_identification: Connection closed by remote hostSTDERR:
> Connection closed by 10.112.205.90 port 22STDERR: fatal: Could not read
> from remote repository.STDERR: STDERR: Please make sure you have the
> correct access rightsSTDERR: and the repository exists.Failed to run git
> clone command*
>
>
> *Logs from Git server: the Ip in the logs is go-agent ip.Mar  5 23:30:23
> ip-10-112-205-125 sshd[3315655]: pam_unix(sshd:session): session closed for
> user git Mar  5 23:30:23 ip-10-112-205-125 sshd[3315640]: Received
> disconnect from 10.254.56.146 port 63239:11: disconnected by user*
>
>- Have you tried running clones manually to see if you can replicate
>the problem? That way you can enable git debugging flags to debug the
>issue. (e.g GIT_CURL_VERBOSE=1)
>
> *I have not done this part, I can try this on the agent.*
>
>- Which exact git version are you using? A Mac pre-installed one, or
>something from Brew or MacPorts?
>
> *Before this issue, we used pre-installed git version on all go-agents. In
> order to resolve this issue, I have installed git with brew on the
> go-agents and started using it. the version is 2.44.0. But the issue still
> exists. on the GoCD,  we are still using pre-installed git, do I need
> install git with brew on the GoCD as well.*
>
>- Are the errors always on agents or always on the server, or both?
>
> *This error is occurring on the agents when the job starts cloning the
> repos mentioned in the materials.*
>
>- What's the filesystem path that GoCD is cloning into when there are
>failures?
>
> *The failures are happening on the agents. the agent path is
> /Users//go-agent-23.1.0/*
> *We installed GoCD in /Applications/.*
>
> *The artifacts path is /Volumes/Artifacts.*
> Please let me know if you need more information.
> Thank you.
>
> On Saturday, March 16, 2024 at 9:37:21 AM UTC-4 Chad Wilson wrote:
>
>> GoCD doesn't do anything special with Git - it just uses whatever git
>> version you have available to the agent/server on the path. If something
>> has changed after the Sonoma upgrade, it is probably affecting all Git
>> usage on the machine.
>>
>>- What are the specific clone errors you are getting?
>>- Have you tried running clones manually to see if you can replicate
>>the problem? That way you can enable git debugging flags to debug the
>>issue. (e.g GIT_CURL_VERBOSE=1)
>>- Which exact git version are you using? A Mac pre-installed one, or
>>something from Brew or MacPorts?
>>- Are the errors

Re: I don’t know water fowl

2024-03-16 Thread mike wilson



> On 16/03/2024 14:27 GMT coll...@brendemuehl.net wrote:
> 
>  
> https://www.flickr.com/gp/101533246@N02/rLrsxU8r2Q
> 
> What can anyone tell me about them?

Look like Muscovy (i.e. domestic) ducks.  Maybe interbred with wildfowl but 
maybe not.
--
%(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: [go-cd] git clone failures in gocd pipelines after sonoma upgrade

2024-03-16 Thread Chad Wilson

GoCD doesn't do anything special with Git - it just uses whatever git
version you have available to the agent/server on the path. If something
has changed after the Sonoma upgrade, it is probably affecting all Git
usage on the machine.

   - What are the specific clone errors you are getting?
   - Have you tried running clones manually to see if you can replicate the
   problem? That way you can enable git debugging flags to debug the issue.
   (e.g GIT_CURL_VERBOSE=1)
   - Which exact git version are you using? A Mac pre-installed one, or
   something from Brew or MacPorts?
   - Are the errors always on agents or always on the server, or both?
   - What's the filesystem path that GoCD is cloning into when there are
   failures?

-Chad

On Sat, Mar 16, 2024 at 2:51 AM SATYA R  wrote:

> Hi Team,
>
> Recently, we upgraded all of our go-agents to macos Sonoma from ventura.
> GoCD also runs on Sonoma version.
> After the upgrade, we are seeing intermittent git clone failures in the
> pipelines.
> Each pipeline has 3 or more repos to clone, when multiple pipelines around
> 20 pipelines try to clone the 3 or more repositories from git, we are
> facing this git clone issue.
> sometimes the pipeline are able to clone all the repos but sometimes they
> fail.
>
> is there anything that we need to particularly look into in gocd and
> go-agents configuration due to sonoma upgrade. do we need to make any
> changes in go-agent service  in order to support the sonoma version?
>
> Kindly help us.
>
> Thank you.
>
> --
> 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/63efcffd-c537-4855-8039-9de9eafb885en%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/CAA1RwH9B7ZCqMopamO9At-wHMcyGhZattbTipwzWToD4q25qeA%40mail.gmail.com.

Re: [Servercert-wg] [EXTERNAL] [Discussion Period Begins]: SC-72 - Delete except to policyQualifiers in EVGs; align with BRs by making them NOT RECOMMENDED

2024-03-15 Thread Clint Wilson via Servercert-wg

Hi Paul,

There are a lot of ways that the EVGs differ from the TBRs; that’s basically 
the point of them, as I understand it. Specifically it’s within the profiles 
that most non-process-oriented differences can be found between EV, OV, IV, and 
DV TLS certificates. Are all of these differences issues which should be 
addressed by the WG to bring EV TLS certificates more in line with the leaner 
profiles found in the TBRs?

I don’t see how this is a genuine misalignment between the TBRs and the EVGs. I 
could possibly see a misalignment between RFC 5280 and the EVGs, but even there 
it’s very intentional that allowance is given such that individual use-cases 
can successfully be addressed without violating the RFC.

From https://datatracker.ietf.org/doc/html/rfc2119#section-4: (emphasis mine)
"SHOULD NOT   This phrase, or the phrase "NOT RECOMMENDED" mean that
   there may exist valid reasons in particular circumstances when the
   particular behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label.”

From https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.4:
"To promote interoperability, this profile RECOMMENDS that policy
   information terms consist of only an OID.  Where an OID alone is
   insufficient, this profile strongly recommends that the use of
   qualifiers be limited to those identified in this section.”

In both cases, it’s clear to me, when encountering a SHOULD, SHOULD NOT, 
RECOMMENDS, or NOT RECOMMENDED that the expectation is for CAs to individually 
assess what is the most appropriate action to take. That doesn’t sound like a 
misalignment, so much as an acknowledgement of potential nuance and the need 
for additional consideration. As you say, they shouldn’t "unless they have a 
good reason to" — such as the EV Guidelines explicitly requiring 
policyQualifiers.

I don’t have any particular concern with the change itself, to be clear, but 
the motivation behind this — and the abruptness of the introduction of the 
topic — remain opaque to me.

Thank you,
-Clint

> On Mar 15, 2024, at 9:09 AM, Paul van Brouwershaven 
>  wrote:
> 
> Hi Clint,
> 
> If the BRs specified MAY and the EVGs MUST you can put it in both and thus 
> have profile alignment. After this changed from MAY to NOT RECOMMENDED we end 
> up with a conflicting requirement, while allowed, its expected that CAs 
> adhere to a NOT RECOMMENDED unless they have a good reason to do so.
> 
> While it's possible to implement two different policies this does creates a 
> clear misalignment.
> 
> Paul
> 
> From: Clint Wilson
> Sent: Friday, March 15, 2024 17:00
> To: Paul van Brouwershaven; ServerCert CA/BF
> Subject: [EXTERNAL] Re: [Servercert-wg] [Discussion Period Begins]: SC-72 - 
> Delete except to policyQualifiers in EVGs; align with BRs by making them NOT 
> RECOMMENDED
> 
> Hi,
> 
> Could the ballot author and endorsers please provide some additional 
> explanation and context surrounding this ballot? As far as I can recall, this 
> topic hasn’t been discussed since SC-062, so it’s rather coming out of 
> nowhere as a ballot proposal (which is, of course, totally fine, but also 
> still abrupt/confusing). Why is this difference between the TBRs and the EVGs 
> necessary/valuable for the WG to address at the moment?
> 
> You indicate that this is a discrepancy introduced by Ballot SC-062, but I 
> don’t see how that’s the case. Before SC-062, the TBRs specified 
> policyQualifiers as Optional and after as NOT RECOMMENDED. Neither of these 
> match the MUST present in the EVGs and both of these are 
> compatible/non-conflicting with the MUST present in the EVGs.
> 
> Thanks,
> -Clint
> 
> 
> 
> On Mar 15, 2024, at 3:01 AM, Paul van Brouwershaven via Servercert-wg 
>  wrote:
> 
> This ballot updates the TLS Extended Validation Guidelines (EVGs) by removing 
> the exceptions topolicyQualifiers in section 9.7, to align them with the 
> Baseline Requirements (BRs).As result, this ballot changes policyQualifiers 
> from MUST to NOT RECOMMENDED as stated in the TLS Baseline Requirements, 
> resolving a discrepancy introduced byBallot SC-62v2 
> <https://cabforum.org/2023/03/17/ballot-sc62v2-certificate-profiles-update/> 
> between section 7.1.2.7.9 Subscriber Certificate Policies 
> <https://cabforum.org/working-groups/server/baseline-requirements/requirements/#71279-subscriber-certificate-certificate-policies>
>  of the BRs and the Additional Technical Requirements for EV Certificates 
> <https://cabforum.org/working-groups/server/extended-validation/guidelines/#97-additional-technical-requirements-for-ev-certificates>
>  in the EVGs.
> 
> The following motion has been

Re: [Servercert-wg] [Discussion Period Begins]: SC-72 - Delete except to policyQualifiers in EVGs; align with BRs by making them NOT RECOMMENDED

2024-03-15 Thread Clint Wilson via Servercert-wg

Hi,

Could the ballot author and endorsers please provide some additional 
explanation and context surrounding this ballot? As far as I can recall, this 
topic hasn’t been discussed since SC-062, so it’s rather coming out of nowhere 
as a ballot proposal (which is, of course, totally fine, but also still 
abrupt/confusing). Why is this difference between the TBRs and the EVGs 
necessary/valuable for the WG to address at the moment?

You indicate that this is a discrepancy introduced by Ballot SC-062, but I 
don’t see how that’s the case. Before SC-062, the TBRs specified 
policyQualifiers as Optional and after as NOT RECOMMENDED. Neither of these 
match the MUST present in the EVGs and both of these are 
compatible/non-conflicting with the MUST present in the EVGs.

Thanks,
-Clint



> On Mar 15, 2024, at 3:01 AM, Paul van Brouwershaven via Servercert-wg 
>  wrote:
> 
> This ballot updates the TLS Extended Validation Guidelines (EVGs) by removing 
> the exceptions to policyQualifiers in section 9.7, to align them with the 
> Baseline Requirements (BRs).As result, this ballot changes policyQualifiers 
> from MUST to NOT RECOMMENDED as stated in the TLS Baseline Requirements, 
> resolving a discrepancy introduced byBallot SC-62v2 
>  
> between section 7.1.2.7.9 Subscriber Certificate Policies 
> 
>  of the BRs and the Additional Technical Requirements for EV Certificates 
> 
>  in the EVGs.
> 
> The following motion has been proposed by Paul van Brouwershaven (Entrust) 
> and endorsed by Dimitris Zacharopoulos (HARICA) and Iñigo Barreira (Sectigo).
> 
> You can view and comment on the GitHub pull request representing this ballot 
> here:https://github.com/cabforum/servercert/pull/490 
> 
> --- Motion Begins ---
> 
> This ballot modifies the “Guidelines for the Issuance and Management of 
> Extended Validation Certificates” (“EV Guidelines”) as follows, based on 
> version 1.8.1:
> 
> MODIFY the Extended Validation Guidelines as specified in the following 
> redline: 
> https://github.com/cabforum/servercert/compare/8e7fc7d5cac0cc27c44fe2aa88cf45f5606f4b94...7b9bb1dbfd41b1d0459b8a985ed629ad841ce122
>  
> 
> --- Motion Ends ---
> 
> Discussion (at least 7 days):
> - Start: 2024-03-15 10:00 UTC
> - End no earlier than 2024-03-22 10:00 UTC
> 
> Vote for approval (7 days):
> - Start: TBD
> - End: TBD
> 
> 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. 
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org 
> https://lists.cabforum.org/mailman/listinfo/servercert-wg



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

[gdal-dev] Hanging (or very slow) when ogr2ogr appending to PostGIS table

2024-03-14 Thread Robin Wilson via gdal-dev

Hi,

I’ve been using ogr2ogr to import vector datasets into PostGIS tables.

I originally tried this using a local Postgres server, and ran the following 
commands to import one file into a PostGIS table, and then append the contents 
of another file to the same table:

ogr2ogr --debug ON -f PostgreSQL PG:”host=localhost user=postgres password=blah 
dbname=test_db" buildings1.gpkg -nln ogr_test
ogr2ogr -append -update --debug ON -f PostgreSQL PG:”host=localhost 
user=postgres password=blah dbname=test_db" buildings2.gpkg -nln ogr_test

This works fine, and both commands run quickly.

I then tried the same thing, but with a PostGIS server hosted on Azure. 
Obviously I expect things to take longer when accessing across the internet, 
but this time the first command completed quickly, but the second command seems 
to hang. Looking at the debug output, it shows:

GPKG: GeoPackage v1.2.0
GDAL: GDALOpen(buildings2.gpkg, this=0x131011800) succeeds as GPKG.
PG: Client encoding: 'UTF8'
PG: PostGIS schema: 'public'
PG: PostgreSQL version string : 'PostgreSQL 15.4 on x86_64-pc-linux-gnu, 
compiled by gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit'
PG: PostGIS version string : '3.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1'
GDAL: GDALOpen(PG:, this=0x140f25850) succeeds as PostgreSQL.
PG: Primary key name (FID): fid, type : int4
PG: Using column 'fid' as FID for table 'ogr_test'
OGR2OGR: Using WriteArrowBatch()

and then nothing else.

I’m intrigued as to why it seems to hang, and what it is doing, or trying to 
do. I’ve tried adding buildings2.gpkg to a new table on the Azure PostGIS 
server and it completes very quickly, so it’s not just that buildings2 is 
larger and takes a long time to upload. Similarly, merging the two buildings 
files with ogrmerge.py and then running the ogr2ogr command to import to 
PostGIS also works, and runs quickly.

I’m also intrigued as to why this only seems to be happening with the Azure 
server - is there some configuration option I need to set? I’ve tried 
connecting as the ‘postgres’ root user, so it shouldn’t be a permissions issue.

Any ideas or suggestions of things to try?

Any help gratefully received,

Best regards,

Robin___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev

[Touch-packages] [Bug 2057944] [NEW] pidwait doesn't work. Instead behaves like pgrep

Public bug reported:

pidwait doesn't work at all.

Seems like pidwait was renamed in an Ubuntu patch from upstream pwait -
however the executable that is built acts as "pgrep" unless it's called
as "pwait"; this check also needs to be updated with the executable name
"pidwait".

** Affects: procps (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2057944

Title:
  pidwait doesn't work. Instead behaves like pgrep

Status in procps package in Ubuntu:
  New

Bug description:
  pidwait doesn't work at all.

  Seems like pidwait was renamed in an Ubuntu patch from upstream pwait
  - however the executable that is built acts as "pgrep" unless it's
  called as "pwait"; this check also needs to be updated with the
  executable name "pidwait".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 2057944] Re: pidwait doesn't work. Instead behaves like pgrep

This is the case for jammy - for numbat the pwait -> pidwait change has
happened upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057944

Title:
  pidwait doesn't work. Instead behaves like pgrep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+subscriptions


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

[Bug 2057944] [NEW] pidwait doesn't work. Instead behaves like pgrep

Public bug reported:

pidwait doesn't work at all.

Seems like pidwait was renamed in an Ubuntu patch from upstream pwait -
however the executable that is built acts as "pgrep" unless it's called
as "pwait"; this check also needs to be updated with the executable name
"pidwait".

** Affects: procps (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057944

Title:
  pidwait doesn't work. Instead behaves like pgrep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+subscriptions


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

[Touch-packages] [Bug 2057944] Re: pidwait doesn't work. Instead behaves like pgrep

This is the case for jammy - for numbat the pwait -> pidwait change has
happened upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2057944

Title:
  pidwait doesn't work. Instead behaves like pgrep

Status in procps package in Ubuntu:
  New

Bug description:
  pidwait doesn't work at all.

  Seems like pidwait was renamed in an Ubuntu patch from upstream pwait
  - however the executable that is built acts as "pgrep" unless it's
  called as "pwait"; this check also needs to be updated with the
  executable name "pidwait".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Sprinklerforum] Re: FDC for Standpipe

I would hope there would be a provision that if you hydraulicly prove it whit 
one connection that should be acceptable.

Christopher S. Wilson SET
Project Design Manager
Treasure Valley Fire Protection
2731 S. Saturn Way
Boise, ID 83709
Phone:  208-362-1888
Fax: 208-362-2207

please note all TVFP email
addresses have changed
new email below

chr...@tvfpinc.com<mailto:chr...@tvfp.us>

From: Steve Leyton 
Sent: Thursday, March 14, 2024 10:48 AM
To: Discussion list on issues relating to automatic fire sprinklers 

Cc: Dewayne Martinez 
Subject: [Sprinklerforum] Re: FDC for Standpipe

That’s hydraulics.  If you can deliver the demand with no more inlet pressure 
than the FD is willing to accept, I think you can use 4” for the FDC.


The foregoing is my opinion only and does not represent NFPA or the NFPA 14 
Technical Committee, nor intended to serve as an interpretation of the standard.

Protection Design and Consulting
Steve Leyton, President
T  |  619.255.8964 x 102  |  
www.protectiondesign.com<http://www.protectiondesign.com/>
2851 Camino Del Rio South  |  Suite 210  |  San Diego, CA  92108
Fire Protection System Design | Consulting | Planning | Training







From: Dewayne Martinez 
mailto:dmarti...@total-mechanical.com>>
Sent: Thursday, March 14, 2024 9:30 AM
To: Discussion list on issues relating to automatic fire sprinklers 
mailto:sprinklerforum@lists.firesprinkler.org>>
Cc: Dewayne Martinez 
mailto:dmarti...@total-mechanical.com>>
Subject: [Sprinklerforum] Re: FDC for Standpipe

Would a 5”x4” Storz be 750gpm because of the Storz connection size or 500gpm 
because of the pipe?

From: John Denhardt 
mailto:jdenha...@firesprinkler.org>>
Sent: Thursday, March 14, 2024 10:39 AM
To: Discussion list on issues relating to automatic fire sprinklers 
mailto:sprinklerforum@lists.firesprinkler.org>>
Subject: [Sprinklerforum] Re: FDC for Standpipe

Here is the reference:
NFPA 14 - 2024
10.7.3.1.1

Where a 4 in. (100 mm) inlet is used, the assumed flow per inlet shall be 500 
gpm (1900 L/min).
10.7.3.1.2

Where a 5 in. (125 mm) inlet is used, the assumed flow per inlet shall be 750 
gpm (2850 L/min).

The above is my opinion and has not been processed as a formal interpretation 
in accordance with the NFPA Regulations Governing Committee Projects. This is 
provided with the understanding that the AFSA assumes no liability for this 
opinion or actions taken on it and they are not to be considered the official 
position of the AFSA, and/or NFPA or its technical committees.AFSA cannot 
provide design or consulting engineering services, and this opinion should 
therefore not be considered, nor relied upon, as such.

Thanks,
John

[https://www.dropbox.com/s/g4h8r7hdtsr6154/AFSA_L.png?raw=1]
John August Denhardt, PE
Vice President, Engineering and Technical Services
American Fire Sprinkler Association
m: p:
301-343-1457
214-349-5965 ext 121
w:
firesprinkler.org<https://link.edgepilot.com/s/05225bcc/ClJhZiur_EuTVK5AEN1N7A?u=http://firesprinkler.org/>


Treat Your Apprentices Like VIPs!
AFSA’s Virtual Instruction Program (VIP) for Apprentices is training that comes 
straight from our expert instructors. They lead the way to ensure your men and 
women are trained, letting you focus on OJT. Click 
here<https://link.edgepilot.com/s/0d0f910e/I3IXFpacwkKPqQT68TdoAA?u=https://www.firesprinkler.org/sprinkler-apprentice-training/>
 to learn more and enroll.


On Thu, Mar 14, 2024 at 11:25 AM John Denhardt 
mailto:jdenha...@firesprinkler.org>> wrote:
To all - review NFPA 14 -2024 as it has new requirements for 4" and 5" storz 
connections.
4" is limited to 500 GPM per connection
5" is limited to 750 GPM per connection

Unfortunately, I'm at a conference where my internet connection is very 
limited, otherwise I would give you a section reference.


The above is my opinion and has not been processed as a formal interpretation 
in accordance with the NFPA Regulations Governing Committee Projects. This is 
provided with the understanding that the AFSA assumes no liability for this 
opinion or actions taken on it and they are not to be considered the official 
position of the AFSA, and/or NFPA or its technical committees.AFSA cannot 
provide design or consulting engineering services, and this opinion should 
therefore not be considered, nor relied upon, as such.

Thanks,
John

[https://www.dropbox.com/s/g4h8r7hdtsr6154/AFSA_L.png?raw=1]
John August Denhardt, PE
Vice President, Engineering and Technical Services
American Fire Sprinkler Association
m: p:
301-343-1457
214-349-5965 ext 121
w:
firesprinkler.org<https://link.edgepilot.com/s/05225bcc/ClJhZiur_EuTVK5AEN1N7A?u=http://firesprinkler.org/>


Treat Your Apprentices Like VIPs!
AFSA’s Virtual Instruction Program (VIP) for Apprentices is training that comes 
straight from our expert instructors. They lead the way to ensure your men and 
women are trained, letting you focus on

[Tinycc-devel] tcc-0.9.27 unable to compile latest mob

2024-03-13 Thread Liam Wilson

Hi,

I notice that the release_0_9_27 tag is unable to build the latest mob
(I tested 9d2068c6309dc50dfdbbc30a5d6757683d3f884c). I get the
following error:

$make
tcc -o tcc.o -c tcc.c -DTCC_TARGET_I386 -DONE_SOURCE=0
-DTCC_GITHASH="\"2024-03-03 mob@9d2068c6\"" -Wall -O2 -I.
tcc -o libtcc.o -c libtcc.c -DTCC_TARGET_I386 -DONE_SOURCE=0
-Wall -O2 -I.
tcc -DC2STR conftest.c -o c2str.exe && ./c2str.exe include/tccdefs.h tccdefs_.h
/usr/lib/crt1.o: error: Invalid relocation entry [16]
'.rel.debug_info' @ 04be
tcc: error: file 'crt1.o' not found
tcc -o tccpp.o -c tccpp.c -DTCC_TARGET_I386 -DONE_SOURCE=0 -Wall -O2 -I.
tccpp.c:3747: error: identifier expected
make: *** [Makefile:282: tccpp.o] Error 1

Above was an i386 Linux build using ./configure --cc=tcc

The issue seems to have been introduced in
7b9f19eaab7e568a7c7a42725da812377a588f50

The following patch seems to resolve the issue (make test passes)

--- a/tccpp.c
+++ b/tccpp.c
@@ -3742,7 +3742,7 @@ static void tok_print(const int *str, const char
*msg, ...)
 va_list ap;
 int t, t0, s;
 CValue cval;
-va_start(ap, msg), vfprintf(fp, msg, ap), va_end(ap);
+va_start(ap, msg); vfprintf(fp, msg, ap); va_end(ap);

 s = t0 = 0;
 while (str) {

Was the comma operator used for a reason? If not, it would be useful
to apply that patch to allow the latest mob to be bootstrapped from
the last offical release.

Thanks
Liam

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

[Wikimedia-l] Re: Roses are red, Salicyna made their links blue and we are here, to Wikicelebrate her with you!

2024-03-12 Thread Wilson Oluoha

This was a beautiful read.

My interest in Polish Wikipedia and life in rural Poland has just piqued.

Congratulations Salicyna, You've got a new fan.

Thank you Natalia for writing so beautifully too.

Best,


On Tue, Mar 12, 2024 at 5:28 PM Maciej Artur Nadzikiewicz <
macieknadzikiew...@gmail.com> wrote:

> Congratulations Salicyna, you deserved it!
>
> For those of you who don't edit Polish Wikipedia (you really should,
> people there are amazing!), if you see an article edited by Salicyna you
> can be sure that it meets all the criteria. Most of her DidYouKnow articles
> go through confirmation without any discussion and corrections. It is a
> pleasure working with her.
>
> I hope you can meet her this summer at Wikimania 2024 in Katowice, Poland!
>
> Cheers,
> --
>
>
> Maciej Artur Nadzikiewicz (He/him)
>
> Wikimania 2024 Poland – Team Lead
>
> Wikimedia Europe Board Member
>
> Wikipedia Administrator
>
> User:Nadzik <https://meta.wikimedia.org/wiki/User:Nadzik>
>
> ᐧ
>
> wt., 12 mar 2024 o 13:21 Natalia Szafran 
> napisał(a):
>
>> Hi all,
>>
>> Once again we celebrate an exceptional Wikimedian, this time - an admin,
>> a contributor, a person with many roles in Wikimedia projects.
>>
>>
>> Salicyna <https://pl.wikisource.org/wiki/Wikiskryba:Salicyna>knows the
>> struggle of lacking access to knowledge all too well. Growing up in rural
>> Poland, she was a passionate reader with no access to well-stocked
>> libraries and cultural institutions. This was still in the pre-Internet
>> times, and her family, struggling financially, couldn't provide the
>> resources she yearned for. "I remember this unsatisfied hunger for
>> knowledge as stronger and more severe than the physical hunger," she
>> reflects. “Sadly”, she says “millions still face this very knowledge hunger
>> today, restricted by geographical location, poverty, disabilities, or
>> illness”. Salicyna sees Wikimedia projects, with their free access to
>> knowledge and culture, as a powerful tool to help alleviate this yearning,
>> at least partially.
>>
>> Driven by a desire to offer others what she lacked as a child, Salicyna
>> has become a prolific contributor to the Wikimedia movement, boasting over
>> 680,000 contributions across various projects. She wears many hats: a
>> Wikisource admin, an author of well-regarded medical articles on Wikipedia,
>> a Wikibooks contributor, and a passionate photographer on Wikimedia
>> Commons, specializing in roses and seedlings.
>>
>> Today we WikiCelebrate
>> <https://meta.wikimedia.org/wiki/Communications/WikiCelebrate> her
>> contributions to the Wikimedia Movement!
>>
>> Learn more about her Wikimedia Commons and Wikisource contributions and
>> her story on Diff blog
>> <https://diff.wikimedia.org/2024/03/12/roses-are-red-salicyna-makes-their-links-blue-we-celebrate-her-and-the-content-she-grew/>
>> (available in English, French, Polish, Spanish) or Meta
>> <https://meta.wikimedia.org/wiki/Communications/WikiCelebrate/Salicyna>
>> (where you can also congratulate Salicyna!).
>>
>> 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 them
>> <https://wikimediafoundation.limesurvey.net/WikiCelebrate>.
>>
>> Happy celebrating!
>>
>> --
>> *Natalia Szafran-Kozakowska* (she/her)
>> Senior Global Movement Communications Specialist (European Region)
>> 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/BQX5TBF4POHXXRHSACEHO35A343JZUSR/
>> 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/DATKART4NFL7QROXN7FSWH6QKUAEIXU4/
> To unsubscribe send an email to wikimedia-l-le...@lists.

Re: Public Discussion of Firmaprofesional CA Inclusion Request

2024-03-11 Thread Ben Wilson

All,
This is just a reminder that the public discussion period ends this 
Wednesday, March 13.
Thanks,
Ben

On Wednesday, January 31, 2024 at 3:12:59 PM UTC-7 Ben Wilson wrote:

> All,
>
> This email commences a six-week public discussion of Firmaprofesional’s 
> request to include the “FIRMAPROFESIONAL CA ROOT-A WEB” as a publicly 
> trusted root certificate in one or more CCADB Root Store Member’s program. 
> This discussion period is scheduled to close on March 13, 2024.
>
> 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 Number: 1044 
> <https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=1044>;
>  
> Bugzilla: 1785215 <https://bugzilla.mozilla.org/show_bug.cgi?id=1785215>
>
> Organization Background Information (listed in CCADB):
>
>- 
>
>CA Owner Name: Autoridad de Certificacion Firmaprofesional; 
>Firmaprofesional S.A.
>- 
>
>Website(s): https://www.firmaprofesional.com/
>- 
>
>Address: Passeig de Gracia 50, 2º1º, Barcelona E-08007, Spain
>- 
>
>Problem Reporting Mechanism(s): sop...@firmaprofesional.com
>- 
>
>Organization Type: Firmaprofesional S.A. is a commercial entity in 
>Spain (NIF A62634068)
>- 
>
>Repository URL: 
>https://www.firmaprofesional.com/certification-policies-and-practices/
>
> Certificates Requesting Inclusion:
>
>1. 
>
>FIRMAPROFESIONAL CA ROOT-A WEB:
>- 
>   
>   Certificate download links: (CA Repository 
>   <https://crl.firmaprofesional.com/caroot-a_web.crt>, crt.sh 
>   
> <https://crt.sh/?sha256=BEF256DAF26E9C69BDEC1602359798F3CAF71821A03E018257C53C65617F3D4A>
>   )
>   - 
>   
>   Use cases served/EKUs: 
>   - 
>  
>  Server Authentication 1.3.6.1.5.5.7.3.1
>  - 
>  
>  Client Authentication 1.3.6.1.5.5.7.3.2
>  - 
>   
>   Test websites:
>   - 
>  
>  Valid: https://testsslev2022ec.firmaprofesional.com  
>  - 
>  
>  Revoked: https://testrevokedsslev2022ec.firmaprofesional.com  
>  - 
>  
>  Expired: https://testexpiredsslev2022ec.firmaprofesional.com 
>  
>
> Existing Publicly Trusted Root CAs from Firmaprofesional S.A.:
>
>1. 
>
>Autoridad de Certificacion Firmaprofesional CIF A62634068:
>
>
>- 
>
>Certificate download links: CA Repository 
><https://crl.firmaprofesional.com/caroot.crt> (most recent),
>- 
>   
>   crt.sh 
>   
> <https://crt.sh/?q=57DE0583EFD2B26E0361DA99DA9DF4648DEF7EE8441C3B728AFA9BCDE0F9B26A>
>  
>   (most recent root certificate, included in Google, Microsoft, and 
> Mozilla)
>   - 
>   
>   crt.sh 
>   
> <https://crt.sh/?q=04048028BF1F2864D48F9AD4D83294366A828856553F3B14303F90147F5D40EF>
>  
>   (prior root certificate, included in Apple, Microsoft)
>   - 
>
>Use cases served/EKUs: 
>- 
>   
>   Server Authentication 1.3.6.1.5.5.7.3.1
>   - 
>   
>   Client Authentication 1.3.6.1.5.5.7.3.2
>   - 
>
>Certificate Corpus (subCAs and OCSP): here 
>
> <https://search.censys.io/search?resource=certificates=parsed.extensions.authority_key_id%3A+65cdebab351e003e7ed574c01cb473470e1a642f>
>  
>(requires Censys account)
>- 
>
>Included in: Apple, Chrome, Microsoft, Mozilla
>
> Relevant Policy and Practices Documentation: 
>
>- 
>
>Firmaprofesional CPS in English 
>
> <https://www.firmaprofesional.com/wp-content/uploads/pdfs/FP_CPS-230413-EN-sFP.pdf>,
>  
>version 230413
>- 
>
>Firmaprofesional Website Authentication Certificates CP in English 
>
> <https://www.firmaprofesional.com/wp-content/uploads/pdfs/FP_CP_Autenticacion_Web-230616-EN-sFP.pdf>,
>  
>version 230616
>
>
> Most Recent Self-Assessmen

Re: [Goanet] Goa Welfare Association donates to vehicles to Street Providence

2024-03-09 Thread Wilson Coelho


Please note

GOAN WELFARE SOCIETY - KUWAIT DONATES TWO VEHICLES TO STREET PROVIDENCE IN 
SUPPORT OF THE NOVLE CAUSE


Sent from my Galaxy




 Original message 
From: Frederick Noronha 
Date: 04/12/2023 00:09 (GMT+05:30)
To: Goanet 
Subject: [Goanet] Goa Welfare Association donates to vehicles to Street 
Providence

 Original message 
From: Frederick Noronha 
Date: 04/12/2023 00:09 (GMT+05:30)
To: Goanet 
Subject: [Goanet] Goa Welfare Association donates to vehicles to Street 
Providence

https://t.ly/1jBd6
--

FN * +91-9822122436 * 784 Saligao 403511 Bardez Goa

Re: [go-cd] Is it possible for multiple GoCD servers to use the same database?

2024-03-07 Thread Chad Wilson

Unfortunately moving to an active-active state would be a huge
architectural change for GoCD, and unfortunately not consistent with its
original design - let alone its current maintainer/community state
 (alive, but not
thriving).

Previously, GoCD had a commercial "business continuity" extension to make
"active-passive" setups easier to automate and reduce "switchover" time.
This was a commercial extension later integrated into the core of GoCD
during its "full" open sourcing in 2020, however post-integration it
had a critical
security defect, and was disabled 
and later removed due to lack of interest/usage.

My current recommendation is generally to use the features of
Kubernetes/container orchestration, load balancers and/or cloud providers
to have an external database and both "shared" artfact file/cloud storage
(AWS EBS, EFS and the like) and database in a way that makes switching the
location the server runs as fast as possible, however making this even more
seamless could also do with some work.

In an ideal state of seamless active/passive switches, GoCD would have a
mode to be able to automatically turn on maintenance mode during shutdown,
gracefully shutdown after n-seconds (even if jobs are still running on some
agents), then start in an alternate location with limited human
intervention (utilising the ability for agents to continue in the
background without a server temporarily).

-Chad

On Fri, Mar 8, 2024 at 9:57 AM Lance Nehring 
wrote:

> Thank you.  The steps you are describing is almost exactly what I do
> today.  However, I think GoCD could see more widespread use, if it were
> possible to run multiple servers simultaneously.  If I had time, I'd try to
> help with such a feature.  Even with this limitation, I'd never go back to
> Jenkins.
>
> On Thu, Mar 7, 2024, 13:05 Sriram Narayanan  wrote:
>
>>
>>
>> On Thu, Mar 7, 2024 at 10:21 PM Lance Nehring 
>> wrote:
>>
>>> I'm wanting to deploy a GoCD server into 2 different K8S clusters and
>>> have them share a database. My goal is to be able performance
>>> maintenance on one K8S cluster without impacting the developers.
>>>
>>> *SO* the question is: can multiple GoCD servers share a database
>>> without interfering with each other?
>>>
>>
>> The two instances will have a unique server ID and should not point to
>> the same database. Please do not attempt this even by making them share the
>> same identity since they will be writing to the database.
>>
>> For higher availability, you'll need to think more about the agents
>> connecting to the server on the second K8s cluster. Agents can continue
>> with their job when a server is unavailable and can reconnect to the server
>> once it is back online.
>>
>> You can leverage this behaviour to achieve some form of HA by:
>> - keeping postgres external to the cluster
>> - stopping the GoCD server on the first cluster
>> - starting the GoCD server with the same configuration on the second
>> cluster
>> - either setting up an LB in front of the first with a fail over to the
>> second K8s cluster
>> OR setting up DNS round robin to refer to the second K8s
>> OR setting a really low TTL for the DNS name and making it point to the
>> second cluster for a switch over.
>>
>>
>>>
>>> Thanks.
>>>
>>> --
>>> 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/448aff6b-4bbf-4a5f-a3a2-3289a228dfe6n%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/CANiY96basJe4Jiteh-GNsX%2BF5OJzDuCh82Dg-nBLmS%3DsPY7DiA%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/CAMj%3DmE8akBXupyv4%2B9HbXt-n%3DFZaBfYOi%2B8jJx4hS5Ochnq4QA%40mail.gmail.com
> 
> .
>

-- 
You received this message

Re: SecureD 3.0 has been released!

2024-03-07 Thread Adam Wilson via Digitalmars-d-announce


On Thursday, 7 March 2024 at 17:06:00 UTC, Andrea Fontana wrote:

On Wednesday, 6 March 2024 at 07:47:04 UTC, Adam Wilson wrote:
SecureD 3.0 has been released. This version was set in motion 
by a Cedric Picard, a D community member with Cryptography 
experience, reaching out and suggesting a number of 
improvements to the Symmetric and KDF API's. This resulted in 
an API for symmetric encryption that improves correctness and 
security without significantly increasing developer workload. 
Also improved is the encryption envelope that contains 
symmetrically encrypted data.


Algorithm Changes:
- Removed: SHA2-224, AES-OFB
- Added: SHA3-224/256/384/512

And I even remembered to update the examples in the README.

Future work will focus on using the Operating System provided 
cryptography where available.


Check it out here: https://code.dlang.org/packages/secured


Well done Adam!

I only miss the docs :)

Andrea


Yea, I totally whiffed and forgot to add examples for the new 
methods. And I can never seem to find the time for the DDoc 
comments that it really needs. It'll happen ... someday.

Re: SecureD 3.0 has been released!

2024-03-07 Thread Adam Wilson via Digitalmars-d-announce


On Thursday, 7 March 2024 at 11:04:08 UTC, Dukc wrote:

On Wednesday, 6 March 2024 at 07:47:04 UTC, Adam Wilson wrote:
This version was set in motion by a Cedric Picard, a D 
community member with Cryptography experience, reaching out 
and suggesting a number of improvements to the Symmetric and 
KDF API's.


Wow, a Cym13 verified crypto library - excellent news!


Indeed. I was actually excited to get the feedback. I am quite 
proud of what this release accomplished.

Re: SecureD 3.0 has been released!

2024-03-07 Thread Adam Wilson via Digitalmars-d-announce


On Thursday, 7 March 2024 at 08:17:47 UTC, aberba wrote:

On Wednesday, 6 March 2024 at 07:47:04 UTC, Adam Wilson wrote:
SecureD 3.0 has been released. This version was set in motion 
by a Cedric Picard, a D community member with Cryptography ...




And I even remembered to update the examples in the README.


+1

I wish more packages did this


And even then I still forgot to add examples for the new Password 
methods...

Re: [go-cd] Is it possible for multiple GoCD servers to use the same database?

2024-03-07 Thread Chad Wilson

Unfortunately not if they are both running at the same time; no. GoCD does
not support active-active configurations like that.

If they otherwise share DB and storage and have the same identity, but one
deployment is scaled to 0 and the other scaled to 1 replica, that is
theoretically possible - but you'd need to co-ordinate very carefully, and
there'd still be brief downtime when you switched instances; similar to if
you just moved the server from one node to another within a single cluster
while doing "maintenance"; so in my personal view not worthwhile.

-Chad

On Fri, Mar 8, 2024 at 12:51 AM Lance Nehring 
wrote:

> I'm wanting to deploy a GoCD server into 2 different K8S clusters and have
> them share a database. My goal is to be able performance maintenance on
> one K8S cluster without impacting the developers.
>
> *SO* the question is: can multiple GoCD servers share a database without
> interfering with each other?
>
> Thanks.
>
> --
> 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/448aff6b-4bbf-4a5f-a3a2-3289a228dfe6n%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/CAA1RwH8-hpS44JxCH%3DX3bxX-k6TvzxbruYHRstk2ZWbpe%2BVSOA%40mail.gmail.com.

[Sprinklerforum] Re: Manual Wet Standpipe Inspection

2024-03-07 Thread Chris Wilson

In our area they don’t make us perform the test but we are required to have a 
sign at the fdc with the flow and pressure needed to get the 100 psi at the 
remote hose conecttion.

Christopher S. Wilson SET
Project Design Manager
Treasure Valley Fire Protection
2731 S. Saturn Way
Boise, ID 83709
Phone:  208-362-1888
Fax: 208-362-2207

please note all TVFP email
addresses have changed
new email below

chr...@tvfpinc.com<mailto:chr...@tvfp.us>

From: Steve Mackinnon 
Sent: Thursday, March 7, 2024 7:08 AM
To: Discussion list on issues relating to automatic fire sprinklers 

Subject: [Sprinklerforum] Re: Manual Wet Standpipe Inspection

Good morning,

We’ve found it all depends on the district and individual AHJ…

We do a number of manual wet/dry standpipes in our area and each one comes with 
it’s own challenges.

One of my colleagues just invested in a used fire truck figuring the best 
course of action is to be over prepared than under.

Another company gives “donations” to the local Fire Dept. to come and flow the 
standpipe at test time (this can get expensive over time).

But we always provide a hydraulic calculation for the required flow beforehand.

I found most Fire Pump operators start with 90-100 psi and increase by 10 psi 
until we reach the desired flow and pressure on the roof.

From: Chris Dorn 
mailto:chris.d...@dornfireprotection.com>>
Sent: Wednesday, March 6, 2024 6:53 PM
To: Discussion list on issues relating to automatic fire sprinklers 
mailto:sprinklerforum@lists.firesprinkler.org>>
Subject: [Sprinklerforum] Re: Manual Wet Standpipe Inspection

We have been required to perform a flow test using the city fire truck and the 
top two hose valves. I only did it once but the firemen seemed excited to do 
it. I have been required to run some quick calculations to tell them what 
pressure the pumper needed to provide at the FDC to give them the pressure they 
wanted at the top of a standpipe pretty much every one we do.

Christopher Dorn
Dorn Fire Protection LLC
4132 Dumont Street #4
Cincinnati, Ohio 45226
(513) 295-2499

On Mar 6, 2024, at 5:06 PM, Anthony Carrizosa 
mailto:anth...@archerconstruction.com>> wrote:

Derik,
NFPA 25 states flow tests 6.3.1 Shall be conducted every 5 years on all 
automatic standpipe systems.. your system is not automatic but manual. Since it 
is under water pressure at all times no need for a hydro test either.

Anthony Carrizosa
Project Manager | Fire Protection
7855 S 206th St Kent, WA 98032
Cell: 206-679-5283 | Office Dir: 253-341-4593

https://archerconstruction.com<https://linkprotect.cudasvc.com/url?a=https%3a%2f%2farcherconstruction.com%2f=E,1,Wdb65AWzMgSBzW3HDw91SfcRQCtxDUQKoJf-UowQ-WnB_WMosgG-8W7eLePJ42PwWQvLiQx16Pls052VqwHO7tKm-_u5AnWly0ewkNiMkxn-AjQb1JI,=1>

From: Derik Rich mailto:dr...@certfs.com>>
Sent: Wednesday, March 6, 2024 1:53 PM
To: 
sprinklerforum@lists.firesprinkler.org<mailto:sprinklerforum@lists.firesprinkler.org>
Subject: [Sprinklerforum] Manual Wet Standpipe Inspection

Looking for some guidance on flow testing a manual wet standpipe. I have been 
told; A. You don’t have to flow test. B. Perform flow test and calculate 
assistance needed. C. You need to do a proper test with a pumper truck. The 
only thing I can find in 25 is that no hydrostatic test is required on manual 
wet. Can anybody steer me in the right direction? Thanks,


Derik Rich
Estimator


O:
801-281-0746
C:
801-231-6375
A:
1015 S. 3600 W. SLC, UT 84104
E:
dr...@certfs.com<mailto:dr...@certfs.com>
<https://www.facebook.com/certfs/>

<https://www.linkedin.com/company/14776965/>

<https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fcertfs.com%2f=E,1,wEIMwwzvZLvEOpO3oTJ9O3LcWCmB_bKGjKeRHx3AqpZFUGqxltzjLXcLL2QdS7_mib0mFs_oH-4geaUkpKI8cLXyYhgAH5J1R_lhzmATVDBZFFmYtVXuxOQ,=1>




_
SprinklerForum mailing list:
https://lists.firesprinkler.org/list/sprinklerforum.lists.firesprinkler.org
To unsubscribe send an email to 
sprinklerforum-le...@lists.firesprinkler.org<mailto:sprinklerforum-le...@lists.firesprinkler.org>

_
SprinklerForum mailing list:
https://lists.firesprinkler.org/list/sprinklerforum.lists.firesprinkler.org
To unsubscribe send an email to sprinklerforum-le...@lists.firesprinkler.org

Re: [Servercert-wg] Compromised/Weak Keys Ballot Proposal

2024-03-07 Thread Clint Wilson via Servercert-wg

Hi Wayne,

Thank you for carrying this work item forward. I have a few concerns regarding 
the proposed removal of Debian weak key checking, outlined below.

I don’t believe there has been sufficient explanation or data presented to 
justify the removal of the requirement to check for Debian weak keys. It seems 
to me there are feasible methods for CAs to continue performing this check. 
Similar to what Martijn has pointed out, the reasoning provided is lacking 
(hasty generalization, fallacy of composition, etc.). 

I don’t believe a compromise where Debian weak keys only need be checked for 
specific key sizes addresses the core issue, unless tied together with a 
restriction from accepting key sizes which are not included in such a list 
(which I do see as reasonable and something I’m under the impression is already 
being done by some CAs).

The removal of this check seems to shift a burden currently placed on CAs to a 
risk (long assumed resolved) for Relying Parties and Subscribers. From my 
reading of the ballot, the requirement that a CA revoke Certificates with 
Debian weak keys remains in effect, serving only to remove the pre-issuance 
“blocking” requirement, but retaining an expectation that certificates are 
checked post-issuance based on the CA’s awareness of this method of 
compromising a Private Key; this generally seems a significantly worse 
experience for Subscribers. Have I missed something regarding the intent of the 
changes in this regard?

There have been incidents involving certificates issued to Debian weak keys in 
recent years; some CAs have indicated that they don’t receive Debian weak keys 
in requests, but evidence exists to the contrary for the ecosystem as a whole.

Thank you!
-Clint

> On Mar 5, 2024, at 12:01 PM, Wayne Thayer via Servercert-wg 
>  wrote:
> 
> Now that everyone should be back from the F2F meeting, I'd like to get back 
> to this ballot. It currently removes all requirements for Debian weak key 
> checks. I'll plan to begin the formal discussion period in a few days unless 
> there are more responses to this thread.
> 
> Thanks,
> 
> Wayne
> 
> On Mon, Feb 26, 2024 at 1:24 PM Wayne Thayer via Servercert-wg 
> mailto:servercert-wg@cabforum.org>> wrote:
>> Martijn,
>> 
>> The purpose of the first weak keys ballot was to make the requirements more 
>> explicit. If I correctly understand your proposal, by removing the exception 
>> for Debian keys from this ballot, it does the opposite. The only compromise 
>> I can see is to require checking for Debian weak keys but only for specific 
>> key sizes, e.g. 2048, 3072, and 4096. That would somewhat reduce the burden 
>> of these checks, and I'd be happy to go that route if there is consensus for 
>> doing so (with approval of the endorsers, of course). I would appreciate 
>> input from other members on the preferred approach to Debian weak key 
>> checking requirements.
>> 
>> Thanks,
>> 
>> Wayne
>> 
>> On Sun, Feb 25, 2024 at 12:15 AM Martijn Katerbarg 
>> mailto:martijn.katerb...@sectigo.com>> wrote:
>>> Thanks Wayne,
>>> 
>>>  
>>> 
>>> >- The Debian vulnerability is more than 15 years old. If an Applicant 
>>> >submits a Debian weak key at this point, they almost certainly have bigger 
>>> >security issues.
>>> 
>>>  
>>> 
>>> This is the bit I have problems with. Just because the applicant (probably) 
>>> has bigger security issues, doesn’t mean we should be putting relying 
>>> parties at even further risk.  If that’s our measure stick, we might as wel 
>>> allow MD5 again because only insecure systems would generate it.
>>> 
>>> Just this year I’ve seen at least one applicant trying to submit a debian 
>>> weak key for order (which obviously got blocked).
>>> 
>>>  
>>> 
>>> I really like what was done with this ballot, except for this bit. I’d even 
>>> be alright with removing the debian weak key check requirement itself. But 
>>> calling it out explicitly as an excempt, I feel is a step too much.
>>> 
>>>  
>>> 
>>> Regards,
>>> 
>>> Martijn
>>> 
>>>  
>>> 
>>> From: Wayne Thayer mailto:wtha...@gmail.com>>
>>> Date: Friday, 23 February 2024 at 17:21
>>> To: Martijn Katerbarg >> >
>>> Cc: CA/B Forum Server Certificate WG Public Discussion List 
>>> mailto:servercert-wg@cabforum.org>>
>>> Subject: Re: [Servercert-wg] Compromised/Weak Keys Ballot Proposal
>>> 
>>> CAUTION: This email originated from outside of the organization. Do not 
>>> click links or open attachments unless you recognize the sender and know 
>>> the content is safe.
>>> 
>>>  
>>> 
>>> Martijn,
>>> 
>>>  
>>> 
>>> I would summarize the reasoning for removing the Debian requirements as 
>>> follows:
>>> 
>>> - CAs would prefer the greater clarity that would be provided by the weak 
>>> keys ballot that failed last year.
>>> 
>>> - However, some CAs were of the opinion that the prior ballot imposed more 
>>> explicit requirements for Debian weak key checking rather than just 
>>> clarifying existing

[Yahoo-eng-team] [Bug 2056366] [NEW] Neutron ml2/ovn does not exit when killed with SIGTERM

2024-03-06 Thread Terry Wilson

Public bug reported:

When Neutron is killed with SIGTERM (like via systemctl), when using
ML2/OVN neutron workers do not exit and instead are eventually killed
with SIGKILL when the graceful timeout is reached (often around 1
minute).

This is happening due to the signal handlers for SIGTERM. There are
multiple issues.

1) oslo_service, ml2/ovn mech_driver, and ml2/ovo_rpc.py all call 
signal.signal(signal.SIGTERM, ...) overwriting each others signal handlers.
2) SIGTERM is handled in the main thread, and running blocking code there 
causes AssertionErrors in eventlet
3) The ml2/ovn cleanup code doesn't cause the process to end, so it interrupts 
the killing of the process

oslo_service has a singleton SignalHandler class that solves all of
these issues and we should use that instead of calling signal.signal()
ourselves.

** Affects: neutron
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2056366

Title:
  Neutron ml2/ovn does not exit when killed with SIGTERM

Status in neutron:
  New

Bug description:
  When Neutron is killed with SIGTERM (like via systemctl), when using
  ML2/OVN neutron workers do not exit and instead are eventually killed
  with SIGKILL when the graceful timeout is reached (often around 1
  minute).

  This is happening due to the signal handlers for SIGTERM. There are
  multiple issues.

  1) oslo_service, ml2/ovn mech_driver, and ml2/ovo_rpc.py all call 
signal.signal(signal.SIGTERM, ...) overwriting each others signal handlers.
  2) SIGTERM is handled in the main thread, and running blocking code there 
causes AssertionErrors in eventlet
  3) The ml2/ovn cleanup code doesn't cause the process to end, so it 
interrupts the killing of the process

  oslo_service has a singleton SignalHandler class that solves all of
  these issues and we should use that instead of calling signal.signal()
  ourselves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2056366/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Re: [Rpm-maint] [rpm-software-management/rpm] rpmbuild: make it possible to not include SPEC tag (rpm-4.17 compat behavior) (Issue #2727)

2024-03-06 Thread Jarod Wilson

How do you know if the package was built with an older rpm vs. the new rpm? If 
you can ascertain that, then you can surely have the latest rpm complain/warn 
if it finds an rpm built with the latest rpm that doesn't have the tags, while 
older rpm would be blissfully unaware, happy, and able to use an rpm generated 
by the latest rpm.

It just feels like straight-forward backwards compatibility support (which 
would be opt-in, and could emit a warning when you try to do it) would not be 
that difficult to maintain here, and would make a number of users lives much 
easier. Most people would never even know they could do this, because they only 
use rpm via dnf or rpmbuild scripts, which would NOT be setting this optional 
flag. Admittedly, the number of people who would need/want this feature would 
be minimal, but I'm still not seeing why it would be so terrible to carry a few 
extra lines of code here.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2727#issuecomment-1980970565
You are receiving this because you are subscribed to this thread.

Message ID: ___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

[Scikit-learn-commits] Re: Coursework writing services

2024-03-06 Thread Harry Wilson

This site https://gamblersguide.info/en/ is a treasure trove of valuable 
information for any gambler. The guides are comprehensive yet easy to 
understand, making them perfect for both newbies and seasoned players. I 
appreciate the attention to detail and the thoroughness of the content. It's 
evident that the authors are experts in their field, and their expertise shines 
through in every guide.
___
Scikit-learn-commits mailing list -- scikit-learn-commits@python.org
To unsubscribe send an email to scikit-learn-commits-le...@python.org
https://mail.python.org/mailman3/lists/scikit-learn-commits.python.org/
Member address: arch...@mail-archive.com

[Scikit-learn-commits] Re: [scikit-learn/scikit-learn] 6b646d: fix space missing around parameter in documentatio...

2024-03-06 Thread Harry Wilson

This site https://gamblersguide.info/en/ is a treasure trove of valuable 
information for any gambler. The guides are comprehensive yet easy to 
understand, making them perfect for both newbies and seasoned players. I 
appreciate the attention to detail and the thoroughness of the content. It's 
evident that the authors are experts in their field, and their expertise shines 
through in every guide.
___
Scikit-learn-commits mailing list -- scikit-learn-commits@python.org
To unsubscribe send an email to scikit-learn-commits-le...@python.org
https://mail.python.org/mailman3/lists/scikit-learn-commits.python.org/
Member address: arch...@mail-archive.com

[Scikit-learn-commits] Re: [scikit-learn/scikit-learn] 6b646d: fix space missing around parameter in documentatio...

2024-03-06 Thread Harry Wilson

This site https://gamblersguide.info/en/ is a treasure trove of valuable 
information for any gambler. The guides are comprehensive yet easy to 
understand, making them perfect for both newbies and seasoned players. I 
appreciate the attention to detail and the thoroughness of the content. It's 
evident that the authors are experts in their field, and their expertise shines 
through in every guide.
___
Scikit-learn-commits mailing list -- scikit-learn-commits@python.org
To unsubscribe send an email to scikit-learn-commits-le...@python.org
https://mail.python.org/mailman3/lists/scikit-learn-commits.python.org/
Member address: arch...@mail-archive.com

SecureD 3.0 has been released!

2024-03-05 Thread Adam Wilson via Digitalmars-d-announce

SecureD 3.0 has been released. This version was set in motion by 
a Cedric Picard, a D community member with Cryptography 
experience, reaching out and suggesting a number of improvements 
to the Symmetric and KDF API's. This resulted in an API for 
symmetric encryption that improves correctness and security 
without significantly increasing developer workload. Also 
improved is the encryption envelope that contains symmetrically 
encrypted data.


Algorithm Changes:
- Removed: SHA2-224, AES-OFB
- Added: SHA3-224/256/384/512

And I even remembered to update the examples in the README.

Future work will focus on using the Operating System provided 
cryptography where available.


Check it out here: https://code.dlang.org/packages/secured

Re: [Rpm-maint] [rpm-software-management/rpm] rpmbuild: make it possible to not include SPEC tag (rpm-4.17 compat behavior) (Issue #2727)

2024-03-05 Thread Jarod Wilson

What if a current RPM version complained about a package created w/o the tags? 
It's already possible to generate them by simply using an older RPM version, so 
I don't really see how "latest RPM always creates them" guarantees this feature 
any more than latest RPM if patched to allow creation of RPMs w/o the tags. 
This is legitimately breaking some people's current workflows, as they do devel 
work on a current Fedora system, then need to put resulting SRPMS onto an older 
system. Sure, you could get around this with containers, but that's the same 
way someone could just as easily omit the tags. Basically, it's already a 
feature you cannot rely on, so there's really not much harm in taking Denys' 
suggested changes in, no? It's not needed "for all time", but there ARE 
distributions still shipping and supported that cannot use rpms generated by 
the latest rpm.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2727#issuecomment-1979676380
You are receiving this because you are subscribed to this thread.

Message ID: ___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

[grpc-io] Save the Date - gRPConf 2024!

2024-03-05 Thread 'Terry Wilson' via grpc.io



Hello gRPC Community,

Mark your calendars for the premier gRPC event of the year! gRPConf 2024 
will land on the Google Cloud Campus in Sunnyvale, California, on August 
27th, 2024.

Get ready to:

   - 
   
   Dive into the latest gRPC developments
   - 
   
   Network with fellow gRPC users and experts
   - 
   
   Learn best practices and innovative use cases
   
More details, including registration and a Call for Proposals, will be 
coming soon. For now, block off August 27th, 2024, and stay tuned for 
updates!

Best regards,

The gRPConf Team

Follow us on YouTube @gRPCio  


-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/795cf320-355d-47dd-862d-f7fd42ce9986n%40googlegroups.com.

Re: Public Discussion of Acquisition of e-commerce monitoring GmbH by AUSTRIA CARD-Plastikkarten und Ausweissysteme GmbH

2024-03-05 Thread Ben Wilson

 the trusted services. 
> Deviations from the expected quality KPIs trigger the notification and 
> remediation process of our trained IT personnel during working hours and 
> standby. 
>
> Additionally, manual and automated self-audits are carried out on a 
> quarterly basis against a random percentage of all issued certificates as 
> required.
>
>  
>
> *Auditing* 
>
> e-commerce monitoring GmbH will continue to be evaluated by the auditor 
> “A-SIT Zentrum für sichere Informationstechnologie” – Austria under the 
> eIDAS / ETSI audit scheme.
>
> The most recent audit attestation including auditor’s accreditation scope 
> and team qualification can be found under the provided URl and follows the 
> ACAB-c template in its most recent version: 
> https://www.a-sit.at/wp-content/uploads/2023/05/VIG-23-044_audit-attestation_globaltrust-etsi-2023_final_signed.pdf
>
> The most recent eIDAS conformity assessment report can be found here:  
> https://service.globaltrust.eu/static/conformity-assessment-2023.pdf
>
> Here is a quick bottom-up way to reproduce the auditor's qualifications:
>
>
>-  Accreditation scope A-SIT: 
>https://akkreditierung-austria.gv.at/overview  (see A-SIT)
>-  Notification of  A-SIT as CAB: (Name “Zentrum für sichere 
>Informationstechnologie – Austria“ Acronym: “A-SIT”)
>-  Notification of Akkreditierung Austria as NAB: 
>https://eidas.ec.europa.eu/efda/browse/notification/cab-nab
>- Accreditation / “Akkreditierung Austria” at EA: 
>
> https://european-accreditation.org/ea-members/directory-of-ea-members-and-mla-signatories/
>
> A-SIT has been recorded as auditor in the CCADB with Audit Firm Confidence 
> Status as evaluated by Root Store Managers “High” 
> https://ccadb.my.site.com/s/detail/a0F1J1ICCfqUAH  
> <https://ccadb.my.site.com/s/detail/a0F1J1ICCfqUAH>
>
>
> On Thursday, February 8, 2024 at 1:19:33 PM UTC+1 e-commerce monitoring 
> wrote:
>
>> Dear All,
>>
>> e-commerce monitoring GmbH is now 100% subsidiary of AUSTRIA 
>> CARD-Plastikkarten und Ausweissysteme Gesellschaft m.b.H., which is 
>> classified as “große Kapitalgesellschaft” (large corporation) and therefore 
>> needs to comply with all regulations of the Austrian GmbHG (limited 
>> liabilities company Act) and UGB (Commercial Code).
>>
>> e-commerce monitoring GmbH was taken over as a fully functional and 
>> independent entity inside the AUSTRIA CARD group of companies. The 
>> certified policies, processes and commitments of e-commerce monitoring GmbH 
>> continue to apply.
>>
>> The takeover of the company also includes the taking over of the 
>> established staff which results in no changes except top management and 
>> e-commerce monitoring GmbH will continue to adhere and operate according to 
>> the respective policies.
>>
>> Best regards,
>> Daniel
>>
>> On Wednesday, February 7, 2024 at 12:22:36 AM UTC+1 Ben Wilson wrote:
>>
>>> Hi Aaron,
>>>
>>> On Tue, Feb 6, 2024 at 3:00 PM Aaron Gable  
>>> wrote:
>>>
>>>> e-commerce monitoring GmbH currently has multiple open bugzilla tickets 
>>>> which have not had any updates from their staff in multiple months:
>>>> - https://bugzilla.mozilla.org/show_bug.cgi?id=1815534
>>>> - https://bugzilla.mozilla.org/show_bug.cgi?id=1862004
>>>>
>>>
>>> Correct - the questions raised by these incidents still need to be 
>>> answered.
>>>  
>>>
>>>> Does the behavior of the CA being acquired factor into decisions like 
>>>> this, or just the behavior of the acquiring entity? 
>>>>
>>>
>>> The behavior of the entity being acquired and the capabilities and 
>>> history of the acquiring company are relevant, going back for an 
>>> unspecified period of time. (Factors to be considered in deciding how far 
>>> to go back include the nature and severity of any non-compliance and the 
>>> degree to which any incidents reveal persistent, systemic problems.) 
>>>  
>>>
>>>> If a distrust conversation were to arise in the future, how do root 
>>>> programs ensure that bugs filed under previous corporate names are still 
>>>> included in the analysis?
>>>>
>>>
>>> We have not experienced a lot of M/name-change activity recently. I 
>>> believe the Mozilla Community has sufficient continuity, institutional 
>>> memory, and community-based knowledge about the history of CA operators. 
>>> So, I think this concern can be handled wh

[spectre] MA Spiel und Objekt - Apply Now!

2024-03-05 Thread Hannah Perner-Wilson via SPECTRE

[for english version please see below]

Liebe Freunde und Kolleg*Innen von Spiel und Objekt,

Wir gehen in die vierte Runde und freuen uns auf Bewerbungen für unseren 
nächsten Jahrgang! Bewerbungszeitraum hierfür ist vom 11.03. bis 14.05.2024. 
Bitte bewerbt euch, und/oder leitet diese Info weiter 
 an alle, die hieran 
Interesse haben könnten.

Weitere Informationen zum Bewerbungsverfahren sind auf der Webseite des 
Studiengangs zu finden www.spielundobjekt.de  

Der Masterstudiengang Spiel und Objekt schafft Zeit und Raum für das 
Experimentieren mit neuen Ästhetiken im theatralen Erzählen. Gleichzeitig wird 
fundiertes technisches und handwerkliches Wissen über Bühnenvorgänge vermittelt.

Wir freuen uns:-)
Hannah && Clemens


x x x x x x x x x x x x english below x x x x x x x x x x x x


Dear friends and colleagues of Spiel und Objekt,

We’re entering the fourth round, and look forward to receiving applications for 
our next cohort! The application period is from 11.03. to 14.05.2024. Please 
consider applying, and/or forwarding this information 
 to anyone who could be 
interested.

Further information on applications can be found on our program’s website 
www.spielundobjekt.de  

The MA studio Spiel und Objekt provides time and space for experimenting with 
new aesthetics in theatrical storytelling, while learning the fundamental 
skills and technical knowledge for staging interactive theatrical processes.

Greetings:-)
Hannah && Clemens

_
Spiel und Objekt
Hochschule für Schauspielkunst Ernst Busch
spielundobj...@hfs-berlin.de 
https://spielundobjekt.de/ 
https://www.hfs-berlin.de/ 
https://www.instagram.com/spiel_und_objekt/ 



__
SPECTRE list for media culture in Deep Europe
Info, archive and help:
http://post.in-mind.de/cgi-bin/mailman/listinfo/spectre

Re: [Servercert-wg] [Voting Period Begins]: SC65: Convert EVGs into RFC 3647 format v2

2024-03-05 Thread Ben Wilson via Servercert-wg

Mozilla votes "yes" on Ballot SC-65 - Convert EVGs to RFC 3647 format

On Mon, Mar 4, 2024 at 8:33 AM Inigo Barreira via Servercert-wg <
servercert-wg@cabforum.org> wrote:

> *Summary: *
>
> The Extended Validation Certificates guidelines (EVGs) were developed and
> written in a specific format. Since then, the RFC 3647 has been the basis
> (and the de-facto standard) for the CA/Browser Forum to develop other
> documents.
>
> This ballot aims to update the EVGs to follow the RFC 3647 format without
> changing any content, just moving current sections to those defined in the
> RFC 3647. There are no normative requirements changes.
>
> This change also affects the Baseline Requirements for TSL certificates
> (BRs) which needs to point to the new sections of the EVGs. Both documents
> will be updated according to the latest version published.
>
> This ballot is proposed by Iñigo Barreira (Sectigo) and endorsed by Pedro
> Fuentes (OISTE) and Ben Wilson (Mozilla).
>
> --- Motion Begins ---
>
> This ballot modifies the “Baseline Requirements for the Issuance and
> Management of Publicly-Trusted TLS Certificates" ("TLS Baseline
> Requirements"), based on Version 2.0.2 and the “Guidelines for the Issuance
> and Management of Extended Validation Certificates” (EVGs) based on Version
> 1.8.0.
>
> MODIFY the TLS EVGs and BRs as specified in the following Redline:
>
> Comparing
> 90a98dc7c1131eaab01af411968aa7330d315b9b...dedeebfe036fa5a6f0d7ae985ea08317ba60b8cb
> · cabforum/servercert (github.com)
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fcompare%2F90a98dc7c1131eaab01af411968aa7330d315b9b...dedeebfe036fa5a6f0d7ae985ea08317ba60b8cb=05%7C02%7Cinigo.barreira%40sectigo.com%7C864b0df3402c4c71a48308dc3235d77c%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638440454045736811%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=9dyuwM9JFeGMUk4fRNcFdaLuNlOwQGoDI0XmWGbD%2BQE%3D=0>
>
> --- Motion Ends ---
>
> This ballot proposes a Final Maintenance Guideline for the BRs and EVGs.
> The procedure for approval of this ballot is as follows:
>
> Discussion (at least 7 days)
>
>1. Start time: 2024-02-20 17:00:00 UTC
>2. End time: not before 2024-03-04 15:00:00 UTC
>
> Vote for approval (7 days)
>
>1. Start time: 2024-03-04 15:30:00 UTC
>2. End time: 2024-03-11 15:30:00 UTC
>
>
> ___
> 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: [Servercert-wg] [Voting Period Begins]: SC-69v3 Clarify router and firewall logging requirements

2024-03-05 Thread Ben Wilson via Servercert-wg

Mozilla votes "yes" on Ballot SC-69v3 - Clarify router and firewall logging
requirements.

On Mon, Mar 4, 2024 at 3:59 AM Martijn Katerbarg via Servercert-wg <
servercert-wg@cabforum.org> wrote:

> *Summary: *
>
> This ballot aims to clarify what data needs to be logged as part of the
> "Firewall and router activities" logging requirement in the Baseline
> Requirements.
>
> This ballot is proposed by Martijn Katerbarg (Sectigo) and endorsed by
> Daniel Jeffery (Fastly) and Ben Wilson (Mozilla).
>
> --- Motion Begins ---
>
> This ballot modifies the “Baseline Requirements for the Issuance and
> Management of Publicly-Trusted Certificates" ("Baseline Requirements"),
> based on Version 2.0.2.
>
> MODIFY the Baseline Requirements as specified in the following Redline:
> https://github.com/cabforum/servercert/compare/41f01640748fa612386f8b1a3031cd1bff3d4f35...d5bd141e14de098ff00c10de7cf500668cbc6843
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fcompare%2F41f01640748fa612386f8b1a3031cd1bff3d4f35...d5bd141e14de098ff00c10de7cf500668cbc6843=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C5eccf95fe1f248a869b808dc369891e2%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638445276113081044%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=MRsVWWShRU8P7UpEJqlCypru27QkzR2BCFu0sUX1Xkw%3D=0>
>
> --- Motion Ends ---
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
>
> Discussion (at least 7 days)
>
>1. Start time: 2024-02-26 07:00:00 UTC
>2. End time: 2024-03-04 11:00:00 UTC
>
> Vote for approval (7 days)
>
>1. Start time: 2024-03-04 11:00:00 UTC
>2. End time: 2024-03-11 11:00:00 UTC
>
>
>
>
> ___
> 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: Phobos 3 Development is Open!

2024-03-05 Thread Adam Wilson via Digitalmars-d-announce


On Thursday, 29 February 2024 at 00:34:59 UTC, zjh wrote:
On Wednesday, 28 February 2024 at 20:41:46 UTC, Adam Wilson 
wrote:
 or start a discussion if there is disagreement on how to 
handle this.




Although Github has discussions, why not just discuss them in 
the `D forum`? This is `the forum`. Github doesn't have the 
convenience of the `D forum` at all. Why bother with them?


A couple of reasons.
First it's easier to cross-tab discussions with work on the 
design docs.
Second, we started this during the whole fork and didn't need 
that bleeding into the discussion.
Third, we didn't know how this will this GH experiment would work 
but we wanted to try it out. So far it's been a smashing success.

Re: A half-frame Pentax film camera

2024-03-03 Thread mike wilson


> On 03/03/2024 15:04 GMT Comcast  wrote:
> 
>  
> As a medium, film suffers in comparison to digital in that it is less capable 
> of low light reproduction and when pushed, image quality drops precipitously. 
> The solution has always been larger formats. My best film work was generally 
> on 6x7 or 6x6 film. Half a f a 35 mm frame has no appeal whatsoever. Am I 
> missing something here?
> Paul

Not being (or wanting to be) part of the in crowd?

> 
> > On Mar 3, 2024, at 4:01 AM, Henk Terhell  wrote:
> > 
> > More news on the Pentax film camera:
> > https://youtu.be/xqRQTOkhOJU?si=PssAjafiIoYaxbuW
> > 
> > As for me, with a least a dozen film camera's accumulating dust on the 
> > shelf is not fair to these to invest in a new one.
> >
--
%(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: [Emc-users] Mitsubishi VFD control

2024-03-02 Thread lloyd wilson


The only other option (again quoting from the manual):

External signal input (across
terminals 2 (4)-5, multi-speed selection)

which is even _less_ appropriate.

On 3/2/24 05:00, andy pugh wrote:

On Sat, 2 Mar 2024 at 02:37, lloyd wilson  wrote:


- operation mode (param. 79) set to 1 (to quote the manual: 'digital
setting by key operation of the control panel or parameter unit').

What are the other options? That might be the best fit, but doesn't
sound _exactly_ right.




___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Mitsubishi VFD control

2024-03-01 Thread lloyd wilson

thanks to all who have responded; I've tried most (or more) of the 
suggestions given. To reply specifically to the points raised:


- platform is a fresh install of LCNC version 2.8.2. At this point, I'm 
just using halcmd to exercise the various pieces of this puzzle. 
Hardware interface is an external RS-232 to RS-48S adapter (4-wire, full 
duplex). HAL interface is mitsub_vfd.py, with a couple of debug tweaks 
to show the complete interchange with the drive (as shown in original post).


- scaling value is set at default value of 1.0. The hex values for 
requested speeds shown in the original post correspond to the values in 
the VFD manual examples.


- operation mode (param. 79) set to 1 (to quote the manual: 'digital 
setting by key operation of the control panel or parameter unit'). The 
parameter unit (with functional speed control) plugs into the RJ45 
socket used for RS485 communication. I have to assume the param. unit 
generates RS485 data; there are not enough pins to provide some sort of 
'back-channel' speed command data.


-the 3450 test motor runs at ~900 rpm, equivalent to 15 HZ, which is 
minimum frequency value set in the VFD (parameter 2).


the adventure continues- I'll be away for a few days, hopefully 
inspiration will appear!


thanks again

-ldw

On 3/1/24 16:42, Chris Morley wrote:

The man page for Mitsub_vfd mentions the required settings. Check the scaling 
of the command.

Chris



Sent from my Galaxy



 Original message 
From: Thaddeus Waldner 
Date: 2024-03-01 10:59 a.m. (GMT-08:00)
To: "Enhanced Machine Controller (EMC)" 
Subject: Re: [Emc-users] Mitsubishi VFD control

I recently set up a Mitsubishi D700 to work with Mitsub_vfd

These inverters are highly flexible in how they are configured to respond to 
control commands. I spent many hours of trial and error to get the correct 
combination of parameters to even get it to respond to network commands. What 
tripped me up initially was that the drive must be reset by cycling the power 
to make any changes take effect.

It has a handy list of all the non-default parameters. I have attached them 
below. Everything appears to work, though there is some inconsistency in how 
manual seed control works in gmoccapy.


The E500 could be a whole different animal but maybe this will help.


pr  namevalue
1   Maximum frequency   300
2
Minimum frequency
30
3
Base frequency
300
7   Acceleration time   2.5
8
Deceleration time
3
9
Electronic thermal O/L relay
9
13  Starting speed  20
18  High speed maximum frequency300
19
Base frequency voltage
200
20
Acceleration/deceleration reference frequency
300
29
Acceleration/deceleration pattern selection
2
41
RUN key rotation direction selection
5
72
PWM frequency selection
15
77  Parameter write selection   2
82  Motor excitation current80
84
Rated motor frequency
120
96
Auto tuning setting/status
21
117
PU communication station number
96
120
PU communication parity check
0
124
PU communication CR/LF selection
0
160 Extended function display selection 0
298
Frequency search gain
39
340
Communication startup mode selection
1
551
PU mode operation command source selection
4

Hope this helps!,

Thaddeus




On Mar 1, 2024, at 7:34 AM, lloyd wilson  wrote:

I'm using a Mitsubishi E500 VFD for spindle drive on the VMC I'm retrofitting & 
can't get variable speed to cooperate. The mitsub_vfd program operates properly (I 
think)- run/stop behaves as expected, speed commands are generated and accepted by 
the VFD, but the  motor speed stays the same. I hacked in a couple of debugging 
statements to show the dialogs (running in halcmd):

setp sp.motor-cmd 50
halcmd: 01ED11388EF   SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x33 0x38 0x38 
0x45 0x46
7!DEBUG:  ,0,1, 0x6 0x30 0x31

show pins



  4  float IN 50  sp.motor-cmd

...

  then

setp sp.motor-cmd 80
halcmd: 01ED11F40F6   SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x46 0x34 0x30 
0x46 0x36
7!DEBUG:  ,0,1, 0x6 0x30 0x31

show pins



  4  float IN 80  sp.motor-cmd

...

the messages are properly formatted per the Mitsub manual & replies show no 
errors

--but the test motor keeps running at the same speed.

Anyone have a clue where to look for the solution?

as always, thanks

-ldw



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users


___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.

RE: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

2024-03-01 Thread Michail Wilson

Heh

Michail Wilson
206-920-6312

From: neonixie-l@googlegroups.com  On Behalf Of 
Jeff Walton
Sent: Friday, March 1, 2024 9:20 AM
To: neonixie-l@googlegroups.com
Subject: Re: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

Here's some friendly advice:  don't ever use the end of a paper clip to test 
whether there is a glass seal inside that nipple.  The little pop you hear is 
the sound of magic gas escaping.  It's fragile...

Jeff

 Original message 
From: "Jon D." mailto:jondad...@gmail.com>>
Date: 3/1/24 10:10 AM (GMT-07:00)
To: neonixie-l mailto:neonixie-l@googlegroups.com>>
Subject: Re: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

Well, my bad then.  I actually have a few of these somewhere that I know work, 
but I never noticed them looking like these.  My apologies to the group.  And 
thanks for all of the quick feedback !!
On Friday, March 1, 2024 at 10:06:06 AM UTC-7 Jeff Walton wrote:
Hi Jon,

Actually, if you have worked with panaplex, you will recognize that these 
nipples are normal.  The glass seal is actually sucked into the stem that you 
are seeing.  I've bought from this seller and they are used but worked fine.  I 
paid less than the listing price.

Jeff

 Original message 
From: "Jon D." 
Date: 3/1/24 9:40 AM (GMT-07:00)
To: neonixie-l 
Subject: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

CAUTION !!  Buyer BEWARE !!!

>From this eBay auction: Beckman SP-353 Gas Discharge 3 Digits 7-segment Display
https://www.ebay.com/itm/233805887906?mkpid=0=e11304.m43.l3160=osgood=49c6ad514b75487aad670cc6dd87e9ff=43123697509=0=0=-1%7E1=20240301092435=11304

Photo of back of all 4 shows glass nipples ALL broken off (i.e. no neon inside).

"Sold as is."  I wonder why ???  (photo attached)

He's offering these to me for $37.52 each (25% off of $49.88) !!  What a 
deal

Jon J.

--
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neonixie-l+...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/a45de05e-1542-466a-b5f6-311cabf842e3n%40googlegroups.com<https://groups.google.com/d/msgid/neonixie-l/a45de05e-1542-466a-b5f6-311cabf842e3n%40googlegroups.com?utm_medium=email_source=footer>.
--
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
neonixie-l+unsubscr...@googlegroups.com<mailto:neonixie-l+unsubscr...@googlegroups.com>.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/67e11e98-7bd3-420f-9c60-55a7481d4da0n%40googlegroups.com<https://groups.google.com/d/msgid/neonixie-l/67e11e98-7bd3-420f-9c60-55a7481d4da0n%40googlegroups.com?utm_medium=email_source=footer>.
--
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
neonixie-l+unsubscr...@googlegroups.com<mailto:neonixie-l+unsubscr...@googlegroups.com>.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/65e20e34.170a0220.bdecc.685d%40mx.google.com<https://groups.google.com/d/msgid/neonixie-l/65e20e34.170a0220.bdecc.685d%40mx.google.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neonixie-l+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/SA0PR01MB6170BEFC684C64D0F71BA93D825E2%40SA0PR01MB6170.prod.exchangelabs.com.

RE: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

2024-03-01 Thread Michail Wilson

Hello,

I have about 50 units myself.  They all look the same as in the photo.

Michail Wilson
206-920-6312

From: neonixie-l@googlegroups.com  On Behalf Of 
Jon D.
Sent: Friday, March 1, 2024 8:41 AM
To: neonixie-l 
Subject: [neonixie-l] Beckman SP-353s on eBay -- WARNING !!

CAUTION !!  Buyer BEWARE !!!

>From this eBay auction: Beckman SP-353 Gas Discharge 3 Digits 7-segment Display
https://www.ebay.com/itm/233805887906?mkpid=0=e11304.m43.l3160=osgood=49c6ad514b75487aad670cc6dd87e9ff=43123697509=0=0=-1%7E1=20240301092435=11304

Photo of back of all 4 shows glass nipples ALL broken off (i.e. no neon inside).

"Sold as is."  I wonder why ???  (photo attached)

He's offering these to me for $37.52 each (25% off of $49.88) !!  What a 
deal

Jon J.

--
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
neonixie-l+unsubscr...@googlegroups.com<mailto:neonixie-l+unsubscr...@googlegroups.com>.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/a45de05e-1542-466a-b5f6-311cabf842e3n%40googlegroups.com<https://groups.google.com/d/msgid/neonixie-l/a45de05e-1542-466a-b5f6-311cabf842e3n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to neonixie-l+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/neonixie-l/SA0PR01MB6170739C450A525E8F9245F4825E2%40SA0PR01MB6170.prod.exchangelabs.com.

[Emc-users] Mitsubishi VFD control

2024-03-01 Thread lloyd wilson

I'm using a Mitsubishi E500 VFD for spindle drive on the VMC I'm 
retrofitting & can't get variable speed to cooperate. The mitsub_vfd 
program operates properly (I think)- run/stop behaves as expected, speed 
commands are generated and accepted by the VFD, but the  motor speed 
stays the same. I hacked in a couple of debugging statements to show the 
dialogs (running in halcmd):


setp sp.motor-cmd 50
halcmd: 01ED11388EF   SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x33 0x38 
0x38 0x45 0x46

7!DEBUG:  ,0,1, 0x6 0x30 0x31

show pins



 4  float IN 50  sp.motor-cmd

...

 then

setp sp.motor-cmd 80
halcmd: 01ED11F40F6   SENT: 0x5 0x30 0x31 0x45 0x44 0x31 0x31 0x46 0x34 
0x30 0x46 0x36

7!DEBUG:  ,0,1, 0x6 0x30 0x31

show pins



 4  float IN 80  sp.motor-cmd

...

the messages are properly formatted per the Mitsub manual & replies show 
no errors


--but the test motor keeps running at the same speed.

Anyone have a clue where to look for the solution?

as always, thanks

-ldw



___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: Phobos 3 Development is Open!

2024-02-29 Thread Adam Wilson via Digitalmars-d-announce


On Thursday, 29 February 2024 at 13:44:37 UTC, Andrew wrote:
On Wednesday, 28 February 2024 at 20:41:46 UTC, Adam Wilson 
wrote:
I am totally on board with this if the community thinks there 
are improvements to be had here. Head on over to the Design 
repo and you can either submit a PR to the design document, or 
start a discussion if there is disagreement on how to handle 
this.


I'll see if I can check it out next weekend, if that's not too 
late. Studying for my private pilot exam takes priority sadly.


As a fellow pilot, I agree with this prioritization.

Re: [Goanet] RESTORE POWERS OF GOA’S FRRO

2024-02-29 Thread Wilson Coelho

Excellent opinion but hope the message goes clear
Best wishes
Wilson Coelho

From: Goanet  on behalf of Aires Rodrigues 

Sent: February 27, 2024 9:11 PM
To: goanet 
Subject: [Goanet] RESTORE POWERS OF GOA’S FRRO

Our Chief Minister Dr. Pramod Sawant needs to be commended for promptly
raising with the Central government the long-standing issue of Dual
Citizenship, highlighting the grievances and hardships being faced by those
opting for Portuguese Passports and while applying for OCI and about those
Goans whose birth is registered in Portugal.

It would be also appropriate for the Goa Government to ensure that the
powers of the Foreigners Regional Registration Officer (FRRO) Goa are
restored. For the last few years, the office of the FFRO Goa has been
stripped of all powers and has been acting as a mere post-office for the
FRRO Mumbai.

The FRRO implemented by the Government plays a crucial role in ensuring the
safety and security of people visiting India and provides a central point
of contact for registering foreigners and issuing registration certificates
required for various activities. Goa is an important tourist state and
therefore the FRRO in Goa must be able to carry out all the necessary
functions just like Mumbai.

Everything now is being managed by FFRO Mumbai with even those applying for
OCI having to travel personally to Mumbai for the appointment. Goa having a
sizeable number diaspora overseas with Goans spread across the world, the
office of FRRO Goa should be restored as a fully functioning hub to deal
with affairs of those needing their services.

Let us hope that the Goa Government will act diligently and swiftly so that
our FRRO becomes empowered and fully operational to enable Goans to get
their work done without unnecessary inconvenience, delay and expense.
Adv. Aires Rodrigues

C/G-2, Shopping Complex

Ribandar Retreat

Ribandar – Goa – 403006

Mobile No: 9822684372

Office Tel  No: (0832) 2444012

Email: airesrodrigu...@gmail.com

You can also reach me on

Facebook.com/ AiresRodrigues

Twitter@rodrigues_aires

www.airesrodrigues.in<http://www.airesrodrigues.in>

airesrodrigues1@instagram

Re: Phobos 3 Development is Open!

2024-02-28 Thread Adam Wilson via Digitalmars-d-announce


On Wednesday, 28 February 2024 at 19:45:53 UTC, Greggor wrote:

On Wednesday, 28 February 2024 at 15:55:52 UTC, Andrew wrote:

On Wednesday, 28 February 2024 at 15:45:06 UTC, ryuukk_ wrote:

https://github.com/dlang/phobos/pull/8925/files#diff-647aa2ce9ebedd6759a2f1c55752f0279de8ae7ba55e3c270bd59e1f8c1a5162R131

Why can't D have its own types?


I have to agree with ryuukk_ on this one; it's one thing to 
maintain binary compatibility with C, and another to import 
and use C symbols all over the place in the standard library. 
I think that interfaces with C (or any other language) should 
be reduced to the minimum required to make something work, and 
nothing more. So, keep the usage of malloc/realloc/free to 
allocators and whatnot, and use fread/fwrite only in stdio.


Absolutely agreed, I’d love to use Phobos in code targeting 
smaller platforms that is not just desktop Linux, macOS, 
windows or Bsd. Also being able to use smaller libc(s) where a 
full glibc is not available would be really nice.


I am totally on board with this if the community thinks there are 
improvements to be had here. Head on over to the Design repo and 
you can either submit a PR to the design document, or start a 
discussion if there is disagreement on how to handle this.

Phobos 3 Development is Open!

2024-02-28 Thread Adam Wilson via Digitalmars-d-announce


The first PR for Phobos 3 has been merged into the Phobos repo!

Now, to be clear, this is mostly a housekeeping PR that paves the 
way for further work and there isn't actually anything useful in 
it yet. We've setup the basic structure, DUB build/test config, 
and copied over the modules that don't have any `std` imports. 
The next project will be to (slowly) audit each file for any 
trace of auto-decoding. No module can be added to V3 without 
first being cleared of auto-decoding.


With this comes a few changes in the development process for 
Phobos. The first of which is that all changes to Phobos will now 
need to be cross-applied to both libraries. We have kept V3 in 
the same repo as V2 to make this process easier, but you will 
need to check the V3 directory (tentatively labeled `lib`) to see 
if the V2 file you're modifying is included in V3 yet, and if it 
is, please include your change in corresponding V3 file as well. 
This will be enforced during the review process. If you are 
unsure, you can ping me on GitHub as `@LightBender` in your PR 
and I'll take a look. As we progress, I am sure that the other 
reviewers will become familiar with the state of the V3 code-base.


Note that this process will continue for the indefinite future as 
we intended to maintain V2 alongside V3+. While the exact level 
of support that V2 will receive once V3 is launched hasn't been 
fulled resolved, at a minimum, it must remain in a buildable 
state indefinitely.


Another note is that I do have a day job, so I will only be 
working on V3 in my spare time, as such, any help with the 
auto-decoding audit would be immensely appreciated as that will 
significantly speed up the time to completion and let us start 
focusing on the projects we all want to see happen in Phobos.


If you have any V3 specific questions or comments you can join 
the discussion that's happening in this GitHub repo: 
https://github.com/LightBender/PhobosV3-Design
Or, you can ask on the Forums and in the Discord and I'll do my 
best to keep up with the updates in those places.


Finally, I would like to thank everybody who has contributed to 
the design of V3 already  (there are too many to list, you know 
who you are), you've been a wonderful help as we start this 
journey. Thanks to your efforts the future of Phobos is looking 
very bright!

Re: [ima-evm-utils: PATCH v1 1/1] Change license to LGPL-2.0-or-later and GPL-2.0-or-later

2024-02-26 Thread George Wilson

On Wed, Feb 21, 2024 at 10:11:34AM +0200, Dmitry Kasatkin wrote:
> Currently libimaevm provided by this project is used by the tool evmctl,
> which is also provided by this project.
> 
> An issue was reported about using libimaevm with other software. Its
> GPL2-only license makes it incompatible to use with other licenses, in
> particular GPL3-only.
> 
> To address this issue, change the project license to GPL-2.0-or-later
> and libimaevm to LGPL 2.0 or later.
> 
> Signed-off-by: Dmitry Kasatkin 

Acked-by: George Wilson

Re: Problems reading SD cards

2024-02-25 Thread mike wilson

Not wishing to teach granny how to suck eggs but you could set your old hard 
drive as the C: drive by installing it where the existing new drive plugs in.  
The new drive can then be plugged in and act as an internal storage (usually 
D:) drive.  Swap as much data as possible from the old drive to the new and you 
should have enough space for a reinstall of W7, PS6 or whatever route you 
choose.
> On 24/02/2024 17:25 GMT John Sessoms  wrote:
> 
>  
> Bookmarked that link. I may be able to find the part from Amazon in the 
> U.S. if I need it, but having the part bookmarked gives me the NAME to 
> look up.
> 
> On 2/24/2024 1:47 AM, mike wilson wrote:
> > Transfer the guts of the new machine to the case of the old.  You should be 
> > able to either plug the drive straight into the motherboard via an existing 
> > socket or use a card in one of the PCIE slots. For example:
> > https://www.amazon.co.uk/Rivo-Controller-Expansion-Profile-Non-Raid/dp/B0828FY1B2/ref=sr_1_4
> >> On 23/02/2024 17:11 GMT John Sessoms  wrote:
> >>
> >>   
> >> I'll look into both possibilities.
> >>
> >> The hard part is going to be figuring out if I actually have the media
> >> for Photoshop CS6 Extended and if so where did I put it when I moved?
> >>
> >> I hope I don't have to replace the Photoshop computer. For one thing, it
> >> has a LightScribe Blue-ray/DVD/CDROM burner & new computers you can't
> >> even get a DVD player.
> >>
> >> They don't even build the chassis with a bay to install one anymore.
> >>
> >> On 2/22/2024 4:21 PM, Paul Sorenson wrote:
> >>> Since Win7 was working for you have you considered backing everything up
> >>> and re-installing Win7?  If all you use that computer for is photo
> >>> processing there shouldn't be a lot of software to re-install.
> >>>
> >>> OTOH, if you have a computer running (or able to run) Win10, Win10 has a
> >>> compatibility mode that you can activate that allows you to run aged
> >>> games and software.
> >>>
> >>> -p
> >>>
> >>> On 2/21/2024 6:54 PM, John Sessoms wrote:
> >>>> I spent today doing some maintenance on my photography - making sure I
> >>>> have all of my images copied off of the memory cards onto the computer
> >>>> & batch renaming by Camera Type & Sequence Number ... so that IMGP5432
> >>>> from the K-2 becomes K3-05432
> >>>>
> >>>> Part of the reason for this is the default for Pentax Raw files is
> >>>> "IMGP" and a couple of my cameras have rolled over past  and
> >>>> the K-1 numbering was reset when I had to send it in for repair after
> >>>> I fell & yanked the screen off the back.
> >>>>
> >>>> So it's K10D-1, K20D-0, K-3-0 & K-1-1 ... I pretty
> >>>> much kept up with it WHILE I was downloading images from the camera up
> >>>> until Covid (when I got lazy and sometimes wouldn't download the
> >>>> images for months after I took them)
> >>>>
> >>>> ANYWAY - The K-3 has been giving me fits downloading images today.
> >>>> Adobe Bridge "get media" seems to fail after pulling down about 8
> >>>> images. I'm having the same problem directly copying from the card to
> >>>> the computer - 8 images & an error.
> >>>>
> >>>> When the error comes Windoze says the DCIM folder is empty & can't
> >>>> even see the card to eject it. If I just pull the card reader out &
> >>>> plug it in again the sub-folders are still there in DCIM and I can go
> >>>> into the sub-folder and copy images manually ... but if I select more
> >>>> than 8 at a time it's going to have the same error copying.
> >>>>
> >>>> If I just select 8 images they seem to copy fine and then I can select
> >>>> 8 more and they'll copy, but rarely works for a third batch of 8.
> >>>> Repeat remove & reinsert & select the next 8 ...
> >>>>
> >>>> I only had the problem with the K-3 cards - 2-32GB Sandisk Extreme
> >>>> SDHC and 1-32GB Sandisk Ultra SDXC.
> >>>>
> >>>> I'm pretty sure I only lost a single image to corruption. Sucks, but
> >>>> at least it's not worse. I copied all the images over to my file server.
> >>>>
> >>>> I don't know if it's the camera, the cards, the card reader or the
> >>>> computer. I hope it's not the computer because it's Windows 7 &
> >>>> Photoshop CS6 Extended (which I don't think will run on Windoze 10 &
> >>>> Windoze 10 definitely would not install on this computer (I shall not
> >>>> repeat my previous rant about the attempt to install Windows 10 ...)
> >>>>
> >>>> I'll shut the Photoshop computer down tomorrow, open it up & give it a
> >>>> good cleaning inside & see where we go from here.
--
%(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: Problems reading SD cards

2024-02-23 Thread mike wilson

Transfer the guts of the new machine to the case of the old.  You should be 
able to either plug the drive straight into the motherboard via an existing 
socket or use a card in one of the PCIE slots. For example:
https://www.amazon.co.uk/Rivo-Controller-Expansion-Profile-Non-Raid/dp/B0828FY1B2/ref=sr_1_4
> On 23/02/2024 17:11 GMT John Sessoms  wrote:
> 
>  
> I'll look into both possibilities.
> 
> The hard part is going to be figuring out if I actually have the media 
> for Photoshop CS6 Extended and if so where did I put it when I moved?
> 
> I hope I don't have to replace the Photoshop computer. For one thing, it 
> has a LightScribe Blue-ray/DVD/CDROM burner & new computers you can't 
> even get a DVD player.
> 
> They don't even build the chassis with a bay to install one anymore.
> 
> On 2/22/2024 4:21 PM, Paul Sorenson wrote:
> > Since Win7 was working for you have you considered backing everything up 
> > and re-installing Win7?  If all you use that computer for is photo 
> > processing there shouldn't be a lot of software to re-install.
> > 
> > OTOH, if you have a computer running (or able to run) Win10, Win10 has a 
> > compatibility mode that you can activate that allows you to run aged 
> > games and software.
> > 
> > -p
> > 
> > On 2/21/2024 6:54 PM, John Sessoms wrote:
> >> I spent today doing some maintenance on my photography - making sure I 
> >> have all of my images copied off of the memory cards onto the computer 
> >> & batch renaming by Camera Type & Sequence Number ... so that IMGP5432 
> >> from the K-2 becomes K3-05432
> >>
> >> Part of the reason for this is the default for Pentax Raw files is 
> >> "IMGP" and a couple of my cameras have rolled over past  and 
> >> the K-1 numbering was reset when I had to send it in for repair after 
> >> I fell & yanked the screen off the back.
> >>
> >> So it's K10D-1, K20D-0, K-3-0 & K-1-1 ... I pretty 
> >> much kept up with it WHILE I was downloading images from the camera up 
> >> until Covid (when I got lazy and sometimes wouldn't download the 
> >> images for months after I took them)
> >>
> >> ANYWAY - The K-3 has been giving me fits downloading images today. 
> >> Adobe Bridge "get media" seems to fail after pulling down about 8 
> >> images. I'm having the same problem directly copying from the card to 
> >> the computer - 8 images & an error.
> >>
> >> When the error comes Windoze says the DCIM folder is empty & can't 
> >> even see the card to eject it. If I just pull the card reader out & 
> >> plug it in again the sub-folders are still there in DCIM and I can go 
> >> into the sub-folder and copy images manually ... but if I select more 
> >> than 8 at a time it's going to have the same error copying.
> >>
> >> If I just select 8 images they seem to copy fine and then I can select 
> >> 8 more and they'll copy, but rarely works for a third batch of 8. 
> >> Repeat remove & reinsert & select the next 8 ...
> >>
> >> I only had the problem with the K-3 cards - 2-32GB Sandisk Extreme 
> >> SDHC and 1-32GB Sandisk Ultra SDXC.
> >>
> >> I'm pretty sure I only lost a single image to corruption. Sucks, but 
> >> at least it's not worse. I copied all the images over to my file server.
> >>
> >> I don't know if it's the camera, the cards, the card reader or the 
> >> computer. I hope it's not the computer because it's Windows 7 & 
> >> Photoshop CS6 Extended (which I don't think will run on Windoze 10 & 
> >> Windoze 10 definitely would not install on this computer (I shall not 
> >> repeat my previous rant about the attempt to install Windows 10 ...)
> >>
> >> I'll shut the Photoshop computer down tomorrow, open it up & give it a 
> >> good cleaning inside & see where we go from here.
> >>
> > -- 
> > %(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.
> 
> -- 
> Vivere in aeternum aut mori conatur
> 
> -- 
> This email has been checked for viruses by AVG antivirus software.
> www.avg.com
> --
> %(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.
--
%(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: Search on Cyrus 3.4.1 (RH9 packaged) - recommendations?

2024-02-23 Thread Simon Wilson via Info



--=_=-_OpenGroupware_org_NGMime-1274332-1708740152.041268-10--
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 1180


No-one have any recommendations on how to best set-up search on Cyrus on Re=
d hat - really?




On Saturday, February 17, 2024 16:51 AEST, "Simon Wilson via Info"  wrote:
=C2=A0Over the last few years there has been much discussion that I have se=
en (whether in the list or when I've searched) about squat and xapian etc. =
breaking, only searching some emails, including unindexed emails in search =
results, etc.=C2=A0

I'm currently on 3.0.7 on RH 8, and poised to move the mail server to RH 9,=
 which ships with 3.4.1.

On 3.0.7 I use "search_engine: squat", with the squatter command "squatter =
cmd=3D"squatter -R -n squat"" (the 'squat' channel is defined in imapd.conf=
). Header searches work fine. Complex text / body searches fairly regularly=
 time out and fail, and we've just put up with this...

At risk of starting a war, as I prepare to move to the RH9 server with 3.4.=
1 what is the recommended, easiest, best way to get best outcome for search=
es on 3.4.1?

--=C2=A0
Simon Wilson
M: 0400 121 116Cyrus / Info / see discussions + participants + delivery=C2=
=A0options Permalink
--=C2=A0
Simon Wilson
M: 0400 121 116

--
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Td3528afd579ba728-M7d4f0b=
3e0465df5a8062d051
Delivery options: https://cyrus.topicbox.com/groups/info/subscription

--=_=-_OpenGroupware_org_NGMime-1274332-1708740152.041268-10--
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 1967

No-one have any recommendations on how to best set-up sea=
rch on Cyrus on Red hat - really?On Saturday,=
 February 17, 2024 16:51 AEST, Simon Wilson via Info info@c=
yrus.topicbox.com wrote:Over the last few years there has been m=
uch discussion that I have seen (whether in the list or when Ive searc=
hed) about squat and xapian etc. breaking, only searching some emails, incl=
uding unindexed emails in search results, etc.Im cur=
rently on 3.0.7 on RH 8, and poised to move the mail server to RH 9, which =
ships with 3.4.1.On 3.0.7 I use search_engine: squat=
;, with the squatter command squatter cmd=3Dsquatter -R -n squa=
t (the squat channel is defined in imapd.conf). Heade=
r searches work fine. Complex text / body searches fairly regularly time ou=
t and fail, and weve just put up with this...At risk of st=
arting a war, as I prepare to move to the RH9 server with 3.4.1 what is the=
 recommended, easiest, best way to get best outcome for searches on 3.4.1?<=
br />--Simon WilsonM: 0400 121 116--Simon WilsonM: 0400 121 116

https://cyrus.topicbox.com/latest; style=3D"color:inheri=
t;text-decoration:none">Cyrus
  / Info / see
https://cyrus.topicbox.com/groups/info;>discussions
  +
https://cyrus.topicbox.com/groups/info/members;>participants
  +
https://cyrus.topicbox.com/groups/info/subscription;>delivery=
sp;options
https://cyrus.topicbox.com/groups/info/Td3528afd579ba728-M7d4f0b=
3e0465df5a8062d051" style=3D"float:right">Permalink

=

--=_=-_OpenGroupware_org_NGMime-1274332-1708740152.041268-10

[African Wikimedians] [Wiki Loves Africa 2024] Rejoignez Maryana Iskander pour le lancement de WLA 2024

Chers Wikimédiens,

J'espère que cet e-mail vous trouvera en pleine forme!

L'équipe d'organisation internationale du concours
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Team> Wiki Loves Africa
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa> a le
plaisir de vous inviter à la cérémonie de lancement officiel du concours Wiki
Loves Africa 2024
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024> et à*
la célébration du 10e anniversaire du concours*. Votre présence ajoutera
une étincelle particulière à cet événement virtuel passionnant!

*Détails de l'événement : Cliquez pour voir et vous inscrire sur la page de
l'événement
<https://meta.wikimedia.org/wiki/Event:Wiki_Loves_Africa_2024_Contest_Launch>*
*Date:* Vendredi 1er mars
*Heure:* 16:00 UTC
*Où:* sur Zoom <https://us02web.zoom.us/j/87953314116>.


*Ordre du jour:*

   1. Extravagance d'ouverture : Lancez le processus avec un coup d'envoi
   engageant, perspicace et vibrant.
   2. Voyage à travers une décennie : Alors que nous célébrons une décennie
   d'innovation, découvrez l'histoire étonnante et les points forts de Wiki
   Loves Africa.
   3. Pleins feux sur le thème 2024 !
   4. Présentation des communautés (invités) : Laissez-vous inspirer par
   les membres de la communauté qui partagent leurs connaissances sur
   l'importance de la narration visuelle.
   5. Questions et réponses
   6. Lancement officiel du concours

L'événement durera environ une heure et demie.
Il y aura des traductions en arabe et en français.

Nous serions honorés de vous compter parmi nous. N'hésitez pas à partager
les détails de l'événement avec les autres membres de votre communauté.

Nous sommes très heureux de partager cette occasion spéciale avec vous!

Merci,

-- 

*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

[Commons-l] [Wiki Loves Africa 2024] Join Maryana Iskander to Launch WLA 2024

Dear Wikimedians,

I trust this email meets you in great spirits!

The international organising team
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Team> of the Wiki Loves
Africa <https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa>
contest is thrilled to extend an invitation to you for the official launch
ceremony of the 2024 Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024> contest
and the celebration of the contest's *10 year anniversary*. Your attendance
will add a special spark to this exciting virtual event!

Event details: *Click to view and register on event page*
<https://meta.wikimedia.org/wiki/Event:Wiki_Loves_Africa_2024_Contest_Launch>

When: Friday, March 1st

Time: 16:00 UTC

Where: via Zoom.  <https://us02web.zoom.us/j/87953314116>

Agenda:

   1.

   Opening Extravaganza: Get the launch started with an engaging,
   insightful and vibrant kickoff
   2.

   Journey through a Decade: As we celebrate a decade of innovation,
   discover the amazing history and highlights if Wiki Loves Africa.
   3.

   Spotlighting the 2024 Theme!
   4.

   Communities (guests) Presentation: Gain inspiration from community
   members as they share their knowledge on the importance of visual
   storytelling.
   5.

   Questions & Answers
   6.

   Official Contest Launch


The event is anticipated to last approximately 1.5 hours.

Don't miss out on the excitement! We would be honoured to have you with us.
Please share the event details with your fellow community members.

We are very excited to share this special occasion with you!

Best wishes



-- 

*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>
___
Commons-l mailing list -- commons-l@lists.wikimedia.org
To unsubscribe send an email to commons-l-le...@lists.wikimedia.org

[Wikimedia-l] [Wiki Loves Africa 2024] Join Maryana Iskander to Launch WLA 2024

Dear Wikimedians,

I trust this email meets you in great spirits!

The international organising team
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Team> of the Wiki Loves
Africa <https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa>
contest is thrilled to extend an invitation to you for the official launch
ceremony of the 2024 Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024> contest
and the celebration of the contest's *10 year anniversary*. Your attendance
will add a special spark to this exciting virtual event!

Event details: *Click to view and register on event page*
<https://meta.wikimedia.org/wiki/Event:Wiki_Loves_Africa_2024_Contest_Launch>

When: Friday, March 1st

Time: 16:00 UTC

Where: via Zoom. <https://us02web.zoom.us/j/87953314116>

Agenda:

Opening Extravaganza: Get the launch started with an engaging,
insightful and vibrant kickoff
2.

Journey through a Decade: As we celebrate a decade of innovation,
discover the amazing history and highlights if Wiki Loves Africa.
3.

Spotlighting the 2024 Theme!
4.

Communities (guests) Presentation: Gain inspiration from community
members as they share their knowledge on the importance of visual
storytelling.
5.

Questions & Answers
6.

Official Contest Launch

The event is anticipated to last approximately 1.5 hours.

Don't miss out on the excitement! We would be honoured to have you with us.
Please share the event details with your fellow community members.

We are very excited to share this special occasion with you!

Best wishes

*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>
___
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/GDMK45LGLBRXVTDZ5WGW6UUXCOC7KUN7/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[African Wikimedians] [Wiki Loves Africa 2024] Join Maryana Iskander to Launch WLA 2024

Dear Wikimedians,

I trust this email meets you in great spirits!

The international organising team
<https://meta.wikimedia.org/wiki/Wiki_In_Africa/Team> of the Wiki Loves
Africa <https://meta.wikimedia.org/wiki/Wiki_In_Africa/Wiki_Loves_Africa>
contest is thrilled to extend an invitation to you for the official launch
ceremony of the 2024 Wiki Loves Africa
<https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa_2024> contest
and the celebration of the contest's *10 year anniversary*. Your attendance
will add a special spark to this exciting virtual event!

Event details: *Click to view and register on event page*
<https://meta.wikimedia.org/wiki/Event:Wiki_Loves_Africa_2024_Contest_Launch>

When: Friday, March 1st

Time: 16:00 UTC

Where: via Zoom.  <https://us02web.zoom.us/j/87953314116>

Agenda:

   1.

   Opening Extravaganza: Get the launch started with an engaging,
   insightful and vibrant kickoff
   2.

   Journey through a Decade: As we celebrate a decade of innovation,
   discover the amazing history and highlights if Wiki Loves Africa.
   3.

   Spotlighting the 2024 Theme!
   4.

   Communities (guests) Presentation: Gain inspiration from community
   members as they share their knowledge on the importance of visual
   storytelling.
   5.

   Questions & Answers
   6.

   Official Contest Launch


The event is anticipated to last approximately 1.5 hours.

Don't miss out on the excitement! We would be honoured to have you with us.
Please share the event details with your fellow community members.

We are very excited to share this special occasion with you!

Best wishes



-- 

*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: [Servercert-wg] [Voting Period Begins]: SC-69v2 Clarify router and firewall logging requirements

2024-02-22 Thread Clint Wilson via Servercert-wg

Hi Martijn,

This is a nit, but is there an extra quotation mark in line 1556? Sorry for not 
spotting this earlier :(

Thanks!
-Clint

> On Feb 22, 2024, at 11:50 AM, Martijn Katerbarg via Servercert-wg 
>  wrote:
> 
> Summary: 
> 
> This ballot aims to clarify what data needs to be logged as part of the 
> "Firewall and router activities" logging requirement in the Baseline 
> Requirements.
> 
> This ballot is proposed by Martijn Katerbarg (Sectigo) and endorsed by Daniel 
> Jeffery (Fastly) and Ben Wilson (Mozilla).
> 
> --- Motion Begins ---
> 
> This ballot modifies the “Baseline Requirements for the Issuance and 
> Management of Publicly-Trusted Certificates" ("Baseline Requirements"), based 
> on Version 2.0.2.
> 
> MODIFY the Baseline Requirements as specified in the following Redline: 
> https://github.com/cabforum/servercert/compare/41f01640748fa612386f8b1a3031cd1bff3d4f35...08dcb7c244113cc370c15b725f031d18687a074f
>  
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fservercert%2Fcompare%2F41f01640748fa612386f8b1a3031cd1bff3d4f35...08dcb7c244113cc370c15b725f031d18687a074f=05%7C02%7Cmartijn.katerbarg%40sectigo.com%7C323403dcf1004ae4000108dc2e1a4cee%7C0e9c48946caa465d96604b6968b49fb7%7C0%7C0%7C638435937719533982%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=BYQI9YXEkS627eliL2fakqgr1i4lRmEapV2%2BULEEk%2Fk%3D=0>
> --- Motion Ends ---
> 
> This ballot proposes a Final Maintenance Guideline. The procedure for 
> approval of this ballot is as follows:
> 
> Discussion (at least 7 days)
> 
> Start time: 2024-02-15 11:35:00 UTC
> End time: 2024-02-22 19:50:00 UTC
> Vote for approval (7 days)
> 
> Start time: 2024-02-22 19:50:00 UTC
> End time: 2024-02-29 19:50:00 UTC
>  
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org <mailto:Servercert-wg@cabforum.org>
> https://lists.cabforum.org/mailman/listinfo/servercert-wg



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Chronicles of the CCADB: From Conception to Retirement Reflections

2024-02-22 Thread Kathleen Wilson

On a sunny day in May 2014, the mom of another volleyball player invited me 
for a walk outside. We had enjoyed plenty of these walks before, during the 
many volleyball tournaments where our daughters played on the same team. 
There is nothing quite like being in a convention center packed with 
thousands of girls playing volleyball and yelling and screaming, while 
referees blow their whistles non-stop on every court. We were definitely 
eager to get outside and talk about anything but volleyball.

The other mom, Poonam, asked about my work at Mozilla and expressed an 
interest in my role and the tools I used to curate the list of root 
certificates that were trusted by default in the Firefox browser. I 
explained that I had created a spreadsheet 
<https://groups.google.com/g/mozilla.dev.security.policy/c/eRaE-ntJDpY/m/UDGMJ5Yk3Y4J>
 
containing all of the necessary details for each Certification Authority 
(CA) and that I dreaded the arduous but necessary process of updating and 
publishing it. Poonam suggested that a Customer Relationship Management 
(CRM) tool could make that part of my job easier.  A couple of weeks later 
she invited me over to her house for tea, and she showed me a mock-up of 
how a CRM could be customized to help me curate the CA data. I was 
immediately sold on the concept.

The next two months were a whirlwind of meetings with various CRM 
providers, CRM Admin Consultants, and Mozilla organizations who I had not 
previously worked with. In my usual manner, I created detailed spreadsheets 
comparing the pros and cons of the options. After much discussion the final 
decision was made to use Salesforce and to hire Poonam’s company as the 
Admin Consultant. On July 31, 2014, I received my “Welcome to Salesforce” 
email for my 30 day trial of the Salesforce CRM, which became an official 
salesforce.com organization on August 5, 2014.

On December 3, 2014 I announced in the mozilla.dev.security.policy forum 
<https://groups.google.com/g/mozilla.dev.security.policy/c/dbQoZtpErW8/m/EPWUl9OLSCQJ>
 
that the spreadsheet that I previously maintained would now be maintained 
in Salesforce and available via links in a Mozilla wiki page (now available 
at https://wiki.mozilla.org/CA/Included_Certificates).

In October 2015, Ben Wilson became the first CA Community user of the “CA 
Community in Salesforce”. Then in February 2016 I issued CA Community 
licenses to the Primary Point of Contact for each CA who currently had root 
certificates included in Mozilla’s root store, as announced in MDSP 
<https://groups.google.com/g/mozilla.dev.security.policy/c/B8vAxZedUtM/m/LdD2DVhzBAAJ>.
 
Then CAs began directly entering data about their CA hierarchies into the 
CA Community in Salesforce.

As word about my new tool spread, other root store operators began 
expressing interest in using the CA Community in Salesforce. In October 
2015 I began brainstorming whether major root store operators could share a 
common instance of Salesforce where CAs would be able to provide their data 
in one place for all of the browser root stores they are participating in. 
The root store operators would be able to share in verification of data, 
but continue to make independent decisions. The idea of sharing Mozilla’s 
CA Community in Salesforce with the other browser root store operators came 
into fruition, and the name changed to the “Common CA Database” (CCADB). 
Microsoft joined as Mozilla’s first CCADB partner in June, 2016. About a 
year later Google, Cisco, and Apple also joined the CCADB in that order.

In April 2019, I posted an article to the Mozilla Security Blog called 
“Mozilla’s 
Common CA Database (CCADB) promotes Transparency and Collaboration 
<https://blog.mozilla.org/security/2019/04/15/common-ca-database-ccadb/>”, 
which explained that the CCADB is helping us protect individuals’ security 
and privacy on the internet. The CCADB makes root stores more transparent 
through public-facing reports <https://ccadb.org/resources>, adds 
automation to improve the level and accuracy of rule enforcement, and 
enables CAs to provide their annual updates 
<https://www.ccadb.org/policy#5-policies-audits-and-practices> in one 
centralized system.

As the CCADB grew in scope, I began holding “CCADB Council” meetings with 
the CCADB partners where we discussed any CCADB problems or questions and 
prioritized future enhancement requests. In 2021 the “CCADB Council” 
morphed into the “CCADB Steering Committee” and the meeting frequency 
increased to biweekly. The purpose of the CCADB Steering Committee (SC) 
<https://www.ccadb.org/rootstores/steering-committee> is to collectively 
determine the direction and priorities for the CCADB, and to share the 
workload of designing and testing updates to the CCADB. Additionally, the 
CCADB SC rotates responsibility for reviewing and processing data that is 
common to all of the root store members, such as CA certificate

Retirement Announcement & Thank You!

2024-02-22 Thread Kathleen Wilson

All,

When I started consulting for Mozilla in May of 2008, I had no idea that I
would end up running Mozilla’s root store for almost 16 years! Back then I
believed that the browser root store would become obsolete in a few years
as new solutions to web security were developed and widely adopted. I also
believed that working on the Firefox browser root store would be low-key,
non-stressful, and healthy for my brain.

As it turns out, my job was healthy for my brain, but it was not as low-key
as I had hoped. Interesting situations kept popping up that caught the
attention of various researchers and reporters, making the job a bit more
public-facing than I had envisioned. These situations and the many
negotiations involved in updating policies and requirements led to a few
sleepless nights as my brain continued working overtime. In the end, my job
turned out to be very rewarding, and along the way I was given the
privilege of working with lots of talented people from all over the world.

I truly appreciate all of the help, input, support, and encouragement that
so many of you provided to me throughout these years. You all are a big
part of the motivation behind me continuing to run Mozilla’s root store for
so long. I was also motivated by the belief that I was helping to keep the
web safe in an ever-changing threat landscape. I enjoyed working with you
all as we tackled the challenges facing the Web PKI.

I wish you all the best, and hope that you all will continue to help keep
the web safe for everyone! With my departure, Ben Wilson will continue on
as Owner of Mozilla's CA Certificates
<https://wiki.mozilla.org/Modules/All#CA_Certificates> and CA Certificate
Policy <https://wiki.mozilla.org/Modules/All#Mozilla_CA_Certificate_Policy>
modules. I am confident that he will continue to do a great job.

In my retirement years, which begin on February 29, I look forward to
having fewer responsibilities and traveling more.

Best Regards,
Kathleen Wilson

--
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/d9d2a632-5e61-45f6-84fe-f6dddbdd1cebn%40mozilla.org.

[uknof] UKNOF2 Electric Boogaloo - What's in a name?

2024-02-22 Thread Dave Wilson

Dave Pumford has posted a survey on Linkedin, seeking opinions on what the
future replacement for UKNOF (the events at least) should be called.

If you have an opinion, and wish to express it, you can do so here:

https://www.linkedin.com/posts/netuk_as-promised-we-would-like-to-offer-a-vote-activity-7166119214360039427-mGsX/

DW

Re: Problems reading SD cards

2024-02-21 Thread mike wilson

Unlikely to be the cards if you are getting exactly the same error on all 
three.  My default position is to blame Adobe, which seems to have a more than 
50% success rate.  For hardware problems, I would look at the card reader.
> On 22/02/2024 00:54 GMT John Sessoms  wrote:
> 
>  
> I spent today doing some maintenance on my photography - making sure I 
> have all of my images copied off of the memory cards onto the computer & 
> batch renaming by Camera Type & Sequence Number ... so that IMGP5432 
> from the K-2 becomes K3-05432
> 
> Part of the reason for this is the default for Pentax Raw files is 
> "IMGP" and a couple of my cameras have rolled over past  and the 
> K-1 numbering was reset when I had to send it in for repair after I fell 
> & yanked the screen off the back.
> 
> So it's K10D-1, K20D-0, K-3-0 & K-1-1 ... I pretty much 
> kept up with it WHILE I was downloading images from the camera up until 
> Covid (when I got lazy and sometimes wouldn't download the images for 
> months after I took them)
> 
> ANYWAY - The K-3 has been giving me fits downloading images today. Adobe 
> Bridge "get media" seems to fail after pulling down about 8 images. I'm 
> having the same problem directly copying from the card to the computer - 
> 8 images & an error.
> 
> When the error comes Windoze says the DCIM folder is empty & can't even 
> see the card to eject it. If I just pull the card reader out & plug it 
> in again the sub-folders are still there in DCIM and I can go into the 
> sub-folder and copy images manually ... but if I select more than 8 at a 
> time it's going to have the same error copying.
> 
> If I just select 8 images they seem to copy fine and then I can select 8 
> more and they'll copy, but rarely works for a third batch of 8. Repeat 
> remove & reinsert & select the next 8 ...
> 
> I only had the problem with the K-3 cards - 2-32GB Sandisk Extreme SDHC 
> and 1-32GB Sandisk Ultra SDXC.
> 
> I'm pretty sure I only lost a single image to corruption. Sucks, but at 
> least it's not worse. I copied all the images over to my file server.
> 
> I don't know if it's the camera, the cards, the card reader or the 
> computer. I hope it's not the computer because it's Windows 7 & 
> Photoshop CS6 Extended (which I don't think will run on Windoze 10 & 
> Windoze 10 definitely would not install on this computer (I shall not 
> repeat my previous rant about the attempt to install Windows 10 ...)
> 
> I'll shut the Photoshop computer down tomorrow, open it up & give it a 
> good cleaning inside & see where we go from here.
> 
> -- 
> Vivere in aeternum aut mori conatur
> 
> -- 
> This email has been checked for viruses by AVG antivirus software.
> www.avg.com
> --
> %(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.
--
%(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.

Mozilla intends to Transfer CCADB Ownership to Linux Foundation

2024-02-21 Thread Kathleen Wilson

The Common CA Database (CCADB) is a highly
customized Instance of Salesforce Cloud (Salesforce MSA
),

which has been owned and maintained by Mozilla since 2014. A Salesforce
Instance is a separate set of data and customizations held by
Salesforce.com (SFDC) in a logically separated database (i.e., a database
segregated through password-controlled access).

The CCADB has become an important component of the Web PKI and ensuring its
stability and continuity continues to become more important with time.
Therefore, we intend to transfer the ownership and maintenance of the CCADB
Salesforce Instance from Mozilla to a Linux Foundation
Directed Fund.

Reasons for this change:

- The CCADB has become a cornerstone of the Web PKI, so it should be
more of a shared resource, operated independent of any one root store.
- The CCADB and the corresponding CCADB Public discussion forum are used
for data/topics that are not specific to Mozilla.
- The CCADB Steering Committee
has demonstrated
the ability to effectively define and implement repeatable and sustainable
processes for improving, managing, and maintaining the CCADB.
- Mozilla can have the same benefits of being a CCADB participating Root
Store Operator as the other participating Root Store Operators, without
being responsible for all of the contracts/agreements and finances for the
CCADB.

Impact of this intended change:

- The ownership of the Salesforce Instance (data and meta-data) that is
the foundation of the CCADB will be reassigned from Mozilla to the Linux
Foundation.
- The usage and users of the CCADB will remain the same, and will
continue to be governed by the CCADB Steering Committee. (usage terms
)
- There will be one visible update to the CCADB related to this change –
an announcement that we intend to transfer the ownership and maintenance of
the CCADB from Mozilla to a Linux Foundation Directed Fund.

Best Regards,

Kathleen, 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/cae785b1-cc52-41a7-927d-aa696d38aa3an%40ccadb.org.

Re: Audit Reminder Email Summary - Intermediate Certificates

2024-02-20 Thread Kathleen Wilson

 Forwarded Message 
Subject: Summary of February 2024 Outdated Audit Statements for 
Intermediate Certs
Date: Tue, 20 Feb 2024 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/701eea36-1b5a-42f1-88ca-337f2bc16043n%40mozilla.org.

Re: Audit Reminder Email Summary - Root Certificates

2024-02-20 Thread Kathleen Wilson

 Forwarded Message 
Subject: Summary of February 2024 Audit Reminder Emails
Date: Tue, 20 Feb 2024 13:00:29 + (GMT)

Mozilla: Audit Reminder
CA Owner: iTrusChina Co., Ltd.
Root Certificates:
   vTrus Root CA
   vTrus ECC Root CA
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=4e15fb75-5b4b-4046-9e3a-fe792839c319
Standard Audit Period End Date: 2023-01-08
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=d64d2bd3-b271-4a5a-af52-09edef4caf45
BR Audit Period End Date: 2023-01-08
EV Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=59bbfcf9-a4e6-4ed1-bb76-55d36d0802c5
EV Audit Period End Date: 2023-01-08
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

Mozilla: Audit Reminder
CA Owner: QuoVadis
Root Certificates:
   QuoVadis Root CA 1 G3
   QuoVadis Root CA 2
   QuoVadis Root CA 2 G3
   QuoVadis Root CA 3
   QuoVadis Root CA 3 G3
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=0e809798-505f-4ec6-a1d2-0bddc2fd6471
Standard Audit Period End Date: 2022-12-31
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=534f411f-d153-4eee-ab9a-f333b992cbdb
BR Audit Period End Date: 2022-12-31
EV Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=fce2625e-abe9-4f4a-a24f-f2568d88b7b6
EV Audit Period End Date: 2022-12-31
CA Comments: null

Mozilla: Audit Reminder
CA Owner: Taiwan-CA Inc. (TWCA)
Root Certificates:
   TWCA Global Root CA
   TWCA Root Certification Authority
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=324da182-1237-4ef3-a391-3a4c30652f7e
Standard Audit Period End Date: 2022-12-31
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=c9d0205e-1961-46f1-832f-974d04f18a78
BR Audit Period End Date: 2022-12-31
EV Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=e3e44a7d-5136-4650-bf1d-5bcbc95af9b4
EV Audit Period End Date: 2022-12-31
CA Comments: null

Mozilla: Audit Reminder
CA Owner: Government of The Netherlands, PKIoverheid (Logius)
Root Certificates:
   Staat der Nederlanden Root CA - G3
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=5a1fb183-df20-4120-aea5-25195aa33c9c
Standard Audit Period End Date: 2022-12-31
CA Comments: null

Mozilla: Audit Reminder
CA Owner: Krajowa Izba Rozliczeniowa S.A. (KIR)
Root Certificates:
   SZAFIR ROOT CA2
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=e5be5291-e6da-471c-905d-0f83c13748d2
Standard Audit Period End Date: 2022-12-18
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=31f5b60f-e01b-4ece-888a-9a2fdd07af0e
BR Audit Period End Date: 2022-12-18
CA Comments: null

Mozilla: Audit Reminder
CA Owner: Government of Spain, Fábrica Nacional de Moneda y Timbre (FNMT)
Root Certificates:
   AC RAIZ FNMT-RCM SERVIDORES SEGUROS
   AC RAIZ FNMT-RCM
Standard Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/2023ANEXO-FNMT-v0.2.pdf
Standard Audit Period End Date: 2023-01-12
BR Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/2023ANEXO-FNMT-v0.2.pdf
BR Audit Period End Date: 2023-01-12
EV Audit: 
https://eidas.aenor.com/www.aenor.com/Certificacion_Documentos/eiDas/2023ANEXO-FNMT-v0.2.pdf
EV Audit Period End Date: 2023-01-12
CA Comments: null

Mozilla: Audit Reminder
CA Owner: LAWtrust
Root Certificates:
   LAWtrust Root CA2 (4096)
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=8c28fa59-f911-4c5c-908f-6e587bb719cf
Standard Audit Period End Date: 2022-12-31
CA Comments: null

Mozilla: Audit Reminder
CA Owner: Amazon Trust Services
Root Certificates:
   Starfield Services Root Certificate Authority - G2
   Amazon Root CA 3
   Amazon Root CA 2
   Amazon Root CA 1
   Amazon Root CA 4
Standard Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=2c9785a1-7f1b-43ca-9f2b-8d0c37c841b5
Standard Audit Period End Date: 2023-01-15
BR Audit: 
https://cpa.cpacanada.ca/generichandlers/CPACHandler.ashx?attachmentid=eb0921ab-b374-4b25-a6a9-6ad7f77938b1
BR Audit Period End Date: 2023-01-15
EV Audit:

Re: [Goanet] FOCUS SHOULD BE ON PEOPLE FRIENDLY GOVERNANCE

2024-02-20 Thread Wilson Coelho

Great idea great vision based on factuality but with corrupt practices this 
cannot work side by side with corruption
God save us

From: Goanet  on behalf of Aires Rodrigues 

Sent: February 19, 2024 10:45 PM
To: goanet 
Subject: [Goanet] FOCUS SHOULD BE ON PEOPLE FRIENDLY GOVERNANCE

It should be an ongoing endeavour of every government department and State
owned corporation to ensure that their day to day administration is
extremely people friendly, progressive and public oriented.

There should be an ongoing concerted effort to usher new innovative
administrative reforms in keeping with the changing times and evolving
needs of Good governance.

It would also be appropriate to do everything possible to eradicate any
red-tape that hinders the facilitation of the public availing redressal of
their grievances.

If only every government servant, with a smile and positive attitude deals
in utmost courtesy with the public in discharging the official duties, it
would go a long way in ushering a very congenial environment in our society
to everyone’s benefit.

Our Goa being India's smallest State we could lead in being the nation's
best administered one with optimum levels of people friendly Good
governance for all other States to envy.

Adv. Aires Rodrigues

C/G-2, Shopping Complex

Ribandar Retreat

Ribandar – Goa – 403006

Mobile No: 9822684372

Office Tel  No: (0832) 2444012

Email: airesrodrigu...@gmail.com

You can also reach me on

Facebook.com/ AiresRodrigues

Twitter@rodrigues_aires

www.airesrodrigues.in

airesrodrigues1@instagram

Re: [Servercert-wg] [Voting Period Begins] SC-070: Clarify the use of DTPs for Domain Control Validation

2024-02-20 Thread Clint Wilson via Servercert-wg

Apple votes Yes on Ballot SC-070.

> On Feb 13, 2024, at 8:56 AM, Aaron Gable via Servercert-wg 
>  wrote:
> 
> This new voting period is to fix a typo in the End timestamp of the voting 
> period for the previous version of this ballot. The contents of the motion 
> itself are identical. My apologies for the confusion.
> 
> This ballot aims to clarify the existing language around the use of delegated 
> third-parties during domain and IP address control validation. It leaves the 
> existing language in place, and adds specifics for the cases of DNS queries, 
> WHOIS lookups, and contact with the Domain Name Registrat or IP Address 
> Registration Authority.
> 
> Additionally, it places these same restrictions on CAA checking, with an 
> effective date of 2024-05-15.
> 
> This ballot is proposed by Aaron Gable (ISRG / Let's Encrypt) and endorsed by 
> Mads Henriksveen (Buypass) and Dimitris Zacharopoulos (HARICA). You can view 
> and comment on the github pull request representing this ballot here: 
> https://github.com/cabforum/servercert/puhttps://lists.cabforum.org/pipermail/servercert-wg/2024-February/004174.htmlll/475
>  
> 
> The preceding discussion can be seen here: 
> https://lists.cabforum.org/pipermail/servercert-wg/2024-February/004174.html
> 
> --- Motion Begins ---
> 
> This ballot modifies the "Baseline Requirements for the Issuance and 
> Management of Publicly-Trusted Certificates" ("Baseline Requirements") based 
> on Version 2.0.2
> 
> MODIFY the Baseline Requirements as specified in the following redline: 
> https://github.com/cabforum/servercert/compare/41f01640748fa612386f8b1a3031cd1bff3d4f35...00ea6e24c474fd0ab6eecc25cb8eb733fffc60c3
> 
> --- Motion Ends ---
> 
> Discussion (at least 7 days):
> - Start: 2024-02-02 22:30 UTC
> - End: 2024-02-12 22:30 UTC
> 
> Vote for approval (7 days):
> - Start: 2024-02-13 17:00 UTC
> - End: 2024-02-20 17:00 UTC
> 
> Thanks,
> Aaron
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [go-cd] Wehbook notification plugin

Good to hear!

On Tue, 20 Feb 2024, 07:06 Sylvain Fabre,  wrote:

> Thanks for your answer !
> After digging a bit, we discovered that Mattermost webhooks are compatible
> with Slack ones. We tested the plugin you mentionned above and ... it works
> :
>
> Thanks !
> (and so it means that the "Slack notification plugin" can also be tagged
> as "Mattermost notification plugin :) )
>
>
> Le lundi 19 février 2024 à 17:21:48 UTC+1, Chad Wilson a écrit :
>
>> That's not necessarily true. All the error tells us is that the plugin
>> couldn't handle a particular request type from the server. We need to know
>> which request type to know if that is a problem. From the gocd-server.log
>> you should look at the log lines before the stack trace - the ones with
>> timestamps and WARN/ERROR. Please include those, or we don't know the
>> context the server was in .
>>
>> More importantly, if the plugin isn't working, it's probably better to
>> describe what you actually observe rather than just what you interpret from
>> the logs. (when stage X completed, I expected Y to happen but instead I
>> observe Z)
>>
>> Keep in mind that a "generic" webhook notification plugin is only going
>> to work in some cases for certain target servers which expect a certain
>> payload being sent to their webhooks which match what the plugin does. To
>> my knowledge there is no such thing as a "generic" webhook standard format,
>> but I haven't looked into it in detail. Mattermost would need to
>> support/expect the same format as the plugin sends - so if the plugin is
>> 'not working' it might be that it's not compatible with Mattermost rather
>> than incompatible with GoCD. I suspect this is more likely to be your
>> problem (the plugin doesn't do what you need it to do) than a GoCD
>> compatibility issue - and that you need a .
>>
>> From a quick look at
>> https://developers.mattermost.com/integrate/webhooks/incoming/ the
>> format it accepts is specific to Mattermost and is not what this "generic"
>> plugin is sending. I believe Mattermost tries to adopt the same format as
>> Slack so you might be better to try
>> https://github.com/ashwanthkumar/gocd-slack-build-notifier (which
>> happens to be written by Ashwanth who also responded on this thread)
>> although no idea if it's Mattermost compatible.
>>
>> -Chad
>>
>> On Tue, Feb 20, 2024 at 12:00 AM Sylvain Fabre 
>> wrote:
>>
>>> Well in fact this log comes from the go-server.log file, but I have a
>>> full error in the log of the plugin itself :
>>>
>>>
>>> 2024-02-19 13:49:34,811 ERROR [qtp1928054064-42]
>>> WebhookNotifierPlugin:127 - Failed to refresh configuration
>>> java.lang.NullPointerException: Cannot invoke
>>> "net.getsentry.gocd.webhooknotifier.Request.ordinal()" because the return
>>> value of "net.getsentry.gocd.webhooknotifier.Request.fromString(String
>>> )" is null
>>>at
>>> net.getsentry.gocd.webhooknotifier.WebhookNotifierPlugin.handle(WebhookNotifierPlugin.java:53)
>>>
>>>at
>>> com.thoughtworks.go.plugin.infra.DefaultPluginManager.lambda$submitTo$0(DefaultPluginManager.java:134)
>>>
>>>at
>>> com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.executeActionOnTheService(FelixGoPluginOSGiFramework.java:205)
>>>
>>>at
>>> com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.doOn(FelixGoPluginOSGiFramework.java:164)
>>>
>>>at
>>> com.thoughtworks.go.plugin.infra.DefaultPluginManager.submitTo(DefaultPluginManager.java:131)
>>>
>>>at
>>> com.thoughtworks.go.plugin.access.PluginRequestHelper.submitRequest(PluginRequestHelper.java:49)
>>>
>>>at
>>> com.thoughtworks.go.plugin.access.common.AbstractExtension.notifyPluginSettingsChange(AbstractExtension.java:82)
>>>
>>>at
>>> com.thoughtworks.go.server.service.PluginService.notifyPluginSettingsChange(PluginService.java:191)
>>>
>>>at
>>> com.thoughtworks.go.server.service.PluginService.updatePluginSettingsAndNotifyPluginSettingsChangeListeners(PluginService.java:167)
>>>
>>>at
>>> com.thoughtworks.go.server.service.PluginService.updatePluginSettings(PluginService.java:118)
>>>
>>>at
>>> com.thoughtworks.go.apiv1.pluginsettings.PluginSettingsControllerV1.update(PluginSettingsControllerV1.java:115)
>>>
>>>at sp

Re: [go-cd] Wehbook notification plugin

That's not necessarily true. All the error tells us is that the plugin
couldn't handle a particular request type from the server. We need to know
which request type to know if that is a problem. From the gocd-server.log
you should look at the log lines before the stack trace - the ones with
timestamps and WARN/ERROR. Please include those, or we don't know the
context the server was in .

More importantly, if the plugin isn't working, it's probably better to
describe what you actually observe rather than just what you interpret from
the logs. (when stage X completed, I expected Y to happen but instead I
observe Z)

Keep in mind that a "generic" webhook notification plugin is only going to
work in some cases for certain target servers which expect a certain
payload being sent to their webhooks which match what the plugin does. To
my knowledge there is no such thing as a "generic" webhook standard format,
but I haven't looked into it in detail. Mattermost would need to
support/expect the same format as the plugin sends - so if the plugin is
'not working' it might be that it's not compatible with Mattermost rather
than incompatible with GoCD. I suspect this is more likely to be your
problem (the plugin doesn't do what you need it to do) than a GoCD
compatibility issue - and that you need a .

>From a quick look at
https://developers.mattermost.com/integrate/webhooks/incoming/ the format
it accepts is specific to Mattermost and is not what this "generic" plugin
is sending. I believe Mattermost tries to adopt the same format as Slack so
you might be better to try
https://github.com/ashwanthkumar/gocd-slack-build-notifier (which happens
to be written by Ashwanth who also responded on this thread) although no
idea if it's Mattermost compatible.

-Chad

On Tue, Feb 20, 2024 at 12:00 AM Sylvain Fabre 
wrote:

> Well in fact this log comes from the go-server.log file, but I have a full
> error in the log of the plugin itself :
>
>
> 2024-02-19 13:49:34,811 ERROR [qtp1928054064-42] WebhookNotifierPlugin:127
> - Failed to refresh configuration
> java.lang.NullPointerException: Cannot invoke
> "net.getsentry.gocd.webhooknotifier.Request.ordinal()" because the return
> value of "net.getsentry.gocd.webhooknotifier.Request.fromString(String
> )" is null
>at
> net.getsentry.gocd.webhooknotifier.WebhookNotifierPlugin.handle(WebhookNotifierPlugin.java:53)
>
>at
> com.thoughtworks.go.plugin.infra.DefaultPluginManager.lambda$submitTo$0(DefaultPluginManager.java:134)
>
>at
> com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.executeActionOnTheService(FelixGoPluginOSGiFramework.java:205)
>
>at
> com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.doOn(FelixGoPluginOSGiFramework.java:164)
>
>at
> com.thoughtworks.go.plugin.infra.DefaultPluginManager.submitTo(DefaultPluginManager.java:131)
>
>at
> com.thoughtworks.go.plugin.access.PluginRequestHelper.submitRequest(PluginRequestHelper.java:49)
>
>at
> com.thoughtworks.go.plugin.access.common.AbstractExtension.notifyPluginSettingsChange(AbstractExtension.java:82)
>
>at
> com.thoughtworks.go.server.service.PluginService.notifyPluginSettingsChange(PluginService.java:191)
>
>at
> com.thoughtworks.go.server.service.PluginService.updatePluginSettingsAndNotifyPluginSettingsChangeListeners(PluginService.java:167)
>
>at
> com.thoughtworks.go.server.service.PluginService.updatePluginSettings(PluginService.java:118)
>
>at
> com.thoughtworks.go.apiv1.pluginsettings.PluginSettingsControllerV1.update(PluginSettingsControllerV1.java:115)
>
>at spark.RouteImpl$1.handle(RouteImpl.java:72)
>
> I suspect this error confirms that the plugin is broken with the latest
> GoCD versions.
>
> Le lundi 19 février 2024 à 15:54:08 UTC+1, Chad Wilson a écrit :
>
>> If that error message comes after a log like WARN Error notifying plugin
>> -  with settings change but the plugin otherwise works OK, then you
>> can probably ignore it. There are some optional request types that some
>> plugins don't implement (and don't need to implement), but they don't
>> always handle them so elegantly so they can log errors like the below.
>>
>> If there are other concerns with the plugin or things we want to do with
>> it but it otherwise is working OK, we could consider forking it into the 
>> gocd-contrib
>> organisation <https://github.com/gocd-contrib> to maintain it, since the
>> Sentry folks don't appear to use/maintain it anymore.
>>
>> -Chad
>>
>> On Mon, Feb 19, 2024 at 10:29 PM Sylvain Fabre 
>> wrote:
>>
>>> Sure !
>>>
>

Re: [go-cd] Wehbook notification plugin

If that error message comes after a log like WARN Error notifying plugin -
 with settings change but the plugin otherwise works OK, then you can
probably ignore it. There are some optional request types that some plugins
don't implement (and don't need to implement), but they don't always handle
them so elegantly so they can log errors like the below.

If there are other concerns with the plugin or things we want to do with it
but it otherwise is working OK, we could consider forking it into the
gocd-contrib
organisation <https://github.com/gocd-contrib> to maintain it, since the
Sentry folks don't appear to use/maintain it anymore.

-Chad

On Mon, Feb 19, 2024 at 10:29 PM Sylvain Fabre 
wrote:

> Sure !
>
> Here is the log when we add a hook URL in the plugin configuration :
>
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException:
> Cannot invoke "net.getsentry.gocd.webhooknotifier.Request.ordinal()"
> because the return value of "net.getsentry.gocd.we
> bhooknotifier.Request.fromString(String)" is null
>at
> net.getsentry.gocd.webhooknotifier.WebhookNotifierPlugin.handle(WebhookNotifierPlugin.java:72)
>
>at
> com.thoughtworks.go.plugin.infra.DefaultPluginManager.lambda$submitTo$0(DefaultPluginManager.java:134)
>
>at
> com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.executeActionOnTheService(FelixGoPluginOSGiFramework.java:205)
>
>... 159 common frames omitted
> Caused by: java.lang.NullPointerException: Cannot invoke
> "net.getsentry.gocd.webhooknotifier.Request.ordinal()" because the return
> value of "net.getsentry.gocd.webhooknotifier.Request.fromSt
> ring(String)" is null
>at
> net.getsentry.gocd.webhooknotifier.WebhookNotifierPlugin.handle(WebhookNotifierPlugin.java:53)
>
>... 161 common frames omitted
>
>
> The webhook is in place, and has been tested independantly (and is working)
>
> Thanks for your help,
>
>
>
>
> Le lun. 19 févr. 2024 à 14:10, Chad Wilson  a
> écrit :
>
>> Does that plugin really not work?
>>
>> I note the repo has recently been archived, but the plugin was updated
>> relatively recently in 2023 and there haven't been any changes in those
>> plugin APIs for quite a while to my knowledge - nor removal of old versions
>> of the (plugin API) extension points.
>>
>> In case there's a simple answer, might be worth sharing in which way it
>> doesn't work?
>>
>> -Chad
>>
>>
>> On Mon, 19 Feb 2024, 20:46 Sylvain Fabre,  wrote:
>>
>>> Hi there !
>>>
>>> GoCD is a great tool, and we would like now to send Webhook
>>> notifications to our Mattermost server.
>>> It seems that this plugin
>>> https://github.com/getsentry/gocd-webhook-notification-plugin used to
>>> do the job, but it does not work anymore with latest GoCD releases.
>>>
>>> Do you know if there is another solution to push webhooks ? Is someone
>>> willing to update this plugin to the latest GoCD APIs  (sponsoring
>>> possible) ?
>>>
>>> Thanks !
>>>
>>> --
>>> 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/f36cfd42-923e-44de-a5a6-68e12119bd5fn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/go-cd/f36cfd42-923e-44de-a5a6-68e12119bd5fn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "go-cd" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/go-cd/Wjwn06iKv-0/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAA1RwH8OgUjAGXVW%2Btd0C_%2BGsJigaqAJauyQnqt9iUeFvcQepA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/go-cd/CAA1RwH8OgUjAGXVW%2Btd0C_%2BGsJigaqAJauyQnqt9iUeFvcQepA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 w

Re: [go-cd] Wehbook notification plugin