BALUG-Talk

balug-talk@lists.balug.org

150 discussions

+Web interface: https://www.digitalwitness.org/ Re: Announcing digitalwitness.org - free public signing (witnessing) service
by Michael Paoli 05 Nov '24

05 Nov '24

Now +Web interface: https://www.digitalwitness.org/ On Thu, Oct 31, 2024 at 12:12 AM Michael Paoli via BALUG-Talk <balug-talk(a)lists.balug.org> wrote: > ---------- Forwarded message ---------- > From: Michael Paoli <michael.paoli(a)berkeley.edu> > To: BALUG-Talk <balug-talk(a)lists.balug.org> > Date: Thu, 31 Oct 2024 00:11:26 -0700 > Subject: [BALUG-Talk] Announcing digitalwitness.org - free public signing (witnessing) service > Announcing digitalwitness.org - free public signing (witnessing) service > At present it's in open/public Beta. > > At present the ssh interface is open, other(s) (most notably web) will > likely follow in time. > > Let's say you have a (possibly) large digital artifact (or archive file > of such items). Or even possibly much smaller item. Suggested approach > is to get secure hash/digest of the item, e.g.: > $ sha512sum digital_artifact_file > 3ddd987f33a96b50777d15f7850d80d8e30badf12501289d28d5ee4857d62c25c2c700b6a1313cace8b128fe1e4d1ff4787d70c46e1f633e5e4589bf3f2343ba > digital_artifact_file > $ > Then get that hash/digest signed, e.g.: > $ ssh -nT digitalwitness(a)digitalwitness.org -- > 3ddd987f33a96b50777d15f7850d80d8e30badf12501289d28d5ee4857d62c25c2c700b6a1313cace8b128fe1e4d1ff4787d70c46e1f633e5e4589bf3f2343ba > -----BEGIN PGP SIGNATURE----- > > iQIzBAABCgAdFiEEEMoY7NqvKKtE7xkCOAS8z7K+pwUFAmcjEtkACgkQOAS8z7K+ > pwWH3A//cDtGIHokwF+GEvKnFFE+Cw2hiPVTe0PkBPuymGnLPAC9Um7YkVt1vP8u > ZZhGOVrAivFV75gVASszq6Au4OKY/2GOO0+SMkVaxd9VzprxBH+j8BVixGiDvU3L > k9JbSzzLIKNoTpPptWbphPoEO6cE4WSm1HubMFeODE7znQeVfk5UlpIEE/7XcT0r > lmwnUaoSwhZUL5HxWE3Pt6x4QSTOin38DHCS55LRfDwHC5og5fc7eiC9TSqr/kVB > goyxYg/lCNrKa7HQto03zJ2ZctZnsNj5n81WhPYzBwlpGfb1T/3htqP17PCLJ19W > amWC+kn+9vR5cwGwuEnBxfOlE//CI7d3gWXSSsvHCDhX49Drh1m7OIw4I9vnYYcV > h9fgajSR1SAMiQwo7uQjrmByZnUdXCTfRJ6ywBfuKaZdBX1Y+AGD8cUWc5qnCwrR > rX4bznL2JZhrwrNh6abmDcyqRzMmXr+jM7WqZiJbcxkhoJZ78c+UtCR6ETreVui0 > Ah7a7HSAuZ6E3dek1oBzA5zTV/bpZHEcdz8UcRYWryEF7wtzJ0gi4SXsWLLGq/LA > LaSOPgcA8KMB3A5NtSYdn0ax/MEao/r/spNrxiQI5jKTYBuoI3qSA7I8Pp1qIkkY > DS/XHzT2CNVw6T/YxvqrhqvSPfaQkQWy0lse6WVIG3CfW7Bp0Pk= > =5mCo > -----END PGP SIGNATURE----- > $ > For more information, help, public signing key, etc., just run without > any "command" or arguments thereof, e.g.: > $ ssh -nT digitalwitness(a)digitalwitness.org > And that will provide one with much relevant information, and including > important details (e.g. the signed data is signed without first adding > any implicit newline on the end, though one can explicitly provide that > if desired).

1 0

Announcing digitalwitness.org - free public signing (witnessing) service
by Michael Paoli 31 Oct '24

31 Oct '24

Announcing digitalwitness.org - free public signing (witnessing) service At present it's in open/public Beta. At present the ssh interface is open, other(s) (most notably web) will likely follow in time. Let's say you have a (possibly) large digital artifact (or archive file of such items). Or even possibly much smaller item. Suggested approach is to get secure hash/digest of the item, e.g.: $ sha512sum digital_artifact_file 3ddd987f33a96b50777d15f7850d80d8e30badf12501289d28d5ee4857d62c25c2c700b6a1313cace8b128fe1e4d1ff4787d70c46e1f633e5e4589bf3f2343ba digital_artifact_file $ Then get that hash/digest signed, e.g.: $ ssh -nT digitalwitness(a)digitalwitness.org -- 3ddd987f33a96b50777d15f7850d80d8e30badf12501289d28d5ee4857d62c25c2c700b6a1313cace8b128fe1e4d1ff4787d70c46e1f633e5e4589bf3f2343ba -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEEMoY7NqvKKtE7xkCOAS8z7K+pwUFAmcjEtkACgkQOAS8z7K+ pwWH3A//cDtGIHokwF+GEvKnFFE+Cw2hiPVTe0PkBPuymGnLPAC9Um7YkVt1vP8u ZZhGOVrAivFV75gVASszq6Au4OKY/2GOO0+SMkVaxd9VzprxBH+j8BVixGiDvU3L k9JbSzzLIKNoTpPptWbphPoEO6cE4WSm1HubMFeODE7znQeVfk5UlpIEE/7XcT0r lmwnUaoSwhZUL5HxWE3Pt6x4QSTOin38DHCS55LRfDwHC5og5fc7eiC9TSqr/kVB goyxYg/lCNrKa7HQto03zJ2ZctZnsNj5n81WhPYzBwlpGfb1T/3htqP17PCLJ19W amWC+kn+9vR5cwGwuEnBxfOlE//CI7d3gWXSSsvHCDhX49Drh1m7OIw4I9vnYYcV h9fgajSR1SAMiQwo7uQjrmByZnUdXCTfRJ6ywBfuKaZdBX1Y+AGD8cUWc5qnCwrR rX4bznL2JZhrwrNh6abmDcyqRzMmXr+jM7WqZiJbcxkhoJZ78c+UtCR6ETreVui0 Ah7a7HSAuZ6E3dek1oBzA5zTV/bpZHEcdz8UcRYWryEF7wtzJ0gi4SXsWLLGq/LA LaSOPgcA8KMB3A5NtSYdn0ax/MEao/r/spNrxiQI5jKTYBuoI3qSA7I8Pp1qIkkY DS/XHzT2CNVw6T/YxvqrhqvSPfaQkQWy0lse6WVIG3CfW7Bp0Pk= =5mCo -----END PGP SIGNATURE----- $ For more information, help, public signing key, etc., just run without any "command" or arguments thereof, e.g.: $ ssh -nT digitalwitness(a)digitalwitness.org And that will provide one with much relevant information, and including important details (e.g. the signed data is signed without first adding any implicit newline on the end, though one can explicitly provide that if desired).

1 0

myip - source IP address via http/https, ssh, connection details (myconnection), etc.
by Michael Paoli 21 Sep '24

21 Sep '24

myip - source IP address via http/https, ssh, ... So, some while back https://lists.balug.org/mailman3/hyperkitty/list/balug-talk@lists.balug.org… did put some information out there about how, using BALUG.org, one can get one's source IP address, as seen by The Internet, e.g.: https://www.balug.org/myip http://www.balug.org/myip https://www.ipv4.balug.org/myip http://www.ipv4.balug.org/myip https://www.ipv6.balug.org/myip http://www.ipv6.balug.org/myip etc. And one could also use /myconnection instead of /myip for even more connection details. I also later added capability via ssh, e.g.: $ ssh -4 -T myip(a)balug.org && ssh -6 -T myip(a)balug.org 96.86.170.226 2001:470:67:76f::2 $ ssh -T myip(a)ipv4.balug.org && ssh -T myip(a)ipv6.balug.org 96.86.170.226 2001:470:67:76f::2 $ etc. Very recently added myconnection / SSH_CONNECTION functionality to ssh, so, e.g., one can do, e.g.: $ ssh -4 -T myip(a)balug.org myconnection 96.86.170.226 57644 96.86.170.229 22 $ ssh -T myip(a)ipv6.balug.org SSH_CONNECTION 2001:470:67:76f::2 58146 2001:470:1f05:19e::2 22 $ More detail can be found here: https://www.wiki.balug.org/wiki/doku.php?id=system:myip_help For listing of many other similar services, see: https://www.wiki.balug.org/wiki/doku.php?id=system:what_is_my_ip_address

1 0

BALUG: Notable upgrades coming soon! Lists (Mailman 2 --> 3), etc.
by Michael Paoli 31 Aug '24

31 Aug '24

BALUG: Notable upgrades coming soon! Lists (Mailman 2 --> 3), etc. Some significant updates are coming soon to BALUG! Most notably, for the Virtual Machine (VM) hosting BALUG: List software will be upgraded from Maliman 2 to Mailman 3. That's significantly different, so some key things to be aware of: Your existing subscriptions will migrate (same lists, same posting address, etc.), as will most of your list setting preferences. However, login and password will not migrate. Can still subscribe and unsubscribe via mail, but for viewing and changing one's list option preferences, will generally want to create a login account for that - and one for the site will cover all your Mailman 3 subscriptions, rather than Mailman 2 which has per-list logins. Quite a bit more useful information about the Mailman 2 --> Mailman 3 migration, and what it likely means for you, can be found here: https://www.wiki.balug.org/wiki/doku.php?id=balug:mailman2to3 The BALUG VM will also be undergoing some major operating system upgrades. Though this will cause some at least brief outages, I'm aiming and hoping to generally keep those as short as feasible. So, in general, if site appears to be down or some service(s) not operational, probably check back a bit later and they'll likely be available again. I'm hoping/aiming to do most of this work evenings and weekends, and also hoping to be all wrapped up before the next regularly scheduled BALUG meeting 2024-08-20. Out-of-band communication/status? If anything goes significantly sideways for many hours or more, I'll probably post some status update to the SF-LUG.org list: http://linuxmafia.com/mailman/listinfo/sf-lug and/or BerkeleyLUG.com list: https://groups.google.com/forum/#!forum/berkeleylug The SF-LUG.org and BerkeleyLUG.com web sites also use the same BALUG VM host.

1 3

Mailman 3 testing (@lists.BALUG.org) ...
by Michael Paoli 07 Jul '24

07 Jul '24

Mailman 3 testing (@lists.BALUG.org) ... For the interested and/or curious, actively testing Mailman 3 at present (so far looking at least "reasonable enough", and does have some pretty spiffy features too). If curious and/or want to try it out, have a peek here: https://lists.balug.org/mailman3/ or subscribe by sending email to: balug-test3-subscribe(a)lists.balug.org (that balug-test3 list will not too far in future get merged with the existing BALUG-Test list). or get some more information by sending email with subject or body of: help to: balug-test3-request(a)lists.balug.org See also: https://www.wiki.balug.org/wiki/doku.php?id=system:mailman3 for more information on my Mailman 2 --> 3 project. Presuming all tests out at least "well enough", the @lists.BALUG.org Mailman 2 lists will be migrated to Mailman 3. (Mailman 2 support on Debian has gone EOL (because Python 2, etc.)).

1 0

Have a spare 1GB SO-DIMM Laying around for a Debian project?
by irish.masms 21 Apr '24

21 Apr '24

Hello BALUG members, I'm working on a project to get Debian Linux on an older Netgear NAS. Before I proceed any further I need to upgrade the memory to a 1GB SO-DIMM DDR Non-ECC PC3200 400MHz RAM Memory. By chance, do you have one sitting around that could help this cause? If so, feel free to PM me off list. TIA!

1 0

meetings
by KLH 111111 18 Oct '23

18 Oct '23

Sorry I missed last night. Could not get the money for a round trip. Is there a summary of your security issues? I am not also a whore so I might not stay on the lists. Your plans included Ford Lee Iacocca, Berkshire Hathaway Warren Buffet, Monsanto Terrel Crews. I have never owned a gun myself. I have never murdered anyone. I do not have a DEA badge. K

1 0

Re: [BALUG-Talk] Sodoi ... add me back to all the lists
by Michael Paoli 17 Oct '23

17 Oct '23

Add/drop from lists is self-serve, not going to do that for you. And also well note what I said about BerkeleyLUG.com meeting location. On Mon, Oct 16, 2023 at 12:14 PM KLH 111111 <klh111111(a)outlook.com> wrote: > > Okay. Thanks! Sodoi is fine with me. You can add me back to all the lists. > ________________________________ > From: Michael Paoli <michael.paoli(a)cal.berkeley.edu> > Sent: Monday, October 16, 2023 7:45 AM > Also, BerkeleyLUG.com - meeting location has shuffled around a lot, so > generally best to check list for latest.

2 1

netfilter cve
by KLH 111111 16 Oct '23

16 Oct '23

Is anyone else worried about this? I found it via redhat.com NVD - CVE-2023-39192 (nist.gov)<https://nvd.nist.gov/vuln/detail/CVE-2023-39192> I do not do much linux. Does anyone check that CVEs in redhat do or do not apply to mint for example. KLH

3 4

new to security
by KLH 111111 13 Oct '23

13 Oct '23

I would like to attend 17 oct meeting. I am not sure that I will be able to afford it. Also I would be in San Francisco via BART. I was in programming. The advice was to start acting on what I was worried about. One could port Linux to Java faster than fixing the CVEs. So then I worried about Industrial Control Systems and worked on Clipper. I am also vegan and no longer drive a car. K

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

BALUG-Talk