sorted by: new top controversial old
How come Lemmy/Piefed users seem to have a consensus of like "green mario" is the solution to this and that, but simultaneously oppose death penalty? in c/nostupidquestions@lemmy.world
How come Lemmy/Piefed users seem to have a consensus of like "green mario" is the solution to this and that, but simultaneously oppose death penalty? in c/nostupidquestions@lemmy.world
[–] 1 point 12 hours ago (2 children)

What is the goal of prosecuting the crimes? To put people in prison. Why do people go to prison? Not because someone says so. Because the group sending you to prison can apply violence to you. All governing is through inherent threat of violence. We as a society agree when that's appropriate. (Or, that's how it should work. Right now, in the US, money decides.)

  • permalink
  • fedilink
  • source
  • parent
  • context
    • How come Lemmy/Piefed users seem to have a consensus of like "green mario" is the solution to this and that, but simultaneously oppose death penalty? in c/nostupidquestions@lemmy.world
    How come Lemmy/Piefed users seem to have a consensus of like "green mario" is the solution to this and that, but simultaneously oppose death penalty? in c/nostupidquestions@lemmy.world
    How come Lemmy/Piefed users seem to have a consensus of like "green mario" is the solution to this and that, but simultaneously oppose death penalty? in c/nostupidquestions@lemmy.world
    openssh on musl linux (alpine, openwrt, buildroot, yocto, and a lot of the docker images you've pulled) has had a little problem since 2016 in c/cybersecurity@infosec.pub
    Mark Cuban says Facebook knowingly runs AI deepfake scam ads as Meta docs reveal $16 billion in fraud-linked revenue in c/technology@beehaw.org
    Meet *sshole, the vulnerability that lets hackers SSH into Linux devices in c/cybersecurity@sh.itjust.works
    Vibe Coded AO3 Clone Site Down After Fanfic Authors Buried It With 2,000 Takedown Notices in a Single Day in c/technology@beehaw.org
    West Virginia DMV Unveils Mysterious New "Cryptid" License Plate in c/goodnewseveryone@piefed.social
    The AI bubble could expose your deepest secrets in c/technology@beehaw.org
    OIDC Recommendations? in c/selfhosted@lemmy.world
    19
    Proxmox Crash (infosec.pub)
     

    My new-this-year MS-02 crashed tonight, so I'm going through journalctl -b -1 -p warning -r and I see a bunch of this repeated over and over going back for days:

    Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00200000/00000000
Oct 12 23:59:50 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Receiver ID)
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: AER:   TLP Header: 0x34000000 0x00000052 0x00000000 0x00000000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [21] ACSViol                (First)
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [20] UnsupReq              
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00300000/00000000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:    [15] HeaderOF              
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4:   device [8086:7f44] error status/mask=00008000/00002000
Oct 12 23:59:49 proxmox-06 kernel: pcieport 0000:80:1b.4: PCIe Bus Error: severity=Correctable, type=Transaction Layer, (Receiver ID)
Oct 12 23:59:49 proxmox-06 kernel: aer_ratelimit: 119 callbacks suppressed

    Does this mean one of the SSDs is failing already? I have 1 Crucial P310 4TB SSD for the main drive and another for backups.

    === START OF INFORMATION SECTION ===
Model Number:                       CT4000P310SSD8
Serial Number:                      25465454F087
Firmware Version:                   V8CR010
PCI Vendor/Subsystem ID:            0xc0a9
IEEE OUI Identifier:                0x00a075
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,000,787,030,016 [4.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            00a075 015454f087
Local Time is:                      Tue Oct 13 00:30:43 2026 EDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00d7):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x18):        No_ID_Reuse NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.30W       -        -    0  0  0  0        0       0
 1 +     2.40W       -        -    1  1  1  1        0       0
 2 +     1.50W       -        -    2  2  2  2        0       0
 3 -   0.0300W       -        -    3  3  3  3     1500    5000
 4 -   0.0025W       -        -    4  4  4  4     5000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        41 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    1%
Data Units Read:                    428,281,946 [219 TB]
Data Units Written:                 44,641,186 [22.8 TB]
Host Read Commands:                 15,033,643,064
Host Write Commands:                1,728,938,256
Controller Busy Time:               25,445
Power Cycles:                       24
Power On Hours:                     3,255
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               41 Celsius

Error Information (NVMe Log 0x01, 16 of 255 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged

    === START OF INFORMATION SECTION ===
Model Number:                       CT4000P310SSD8
Serial Number:                      2545543AD7B7
Firmware Version:                   V8CR010
PCI Vendor/Subsystem ID:            0xc0a9
IEEE OUI Identifier:                0x00a075
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          4,000,787,030,016 [4.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            00a075 01543ad7b7
Local Time is:                      Tue Oct 13 00:28:48 2026 EDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00d7):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     86 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x18):        No_ID_Reuse NP_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.30W       -        -    0  0  0  0        0       0
 1 +     2.40W       -        -    1  1  1  1        0       0
 2 +     1.50W       -        -    2  2  2  2        0       0
 3 -   0.0300W       -        -    3  3  3  3     1500    5000
 4 -   0.0025W       -        -    4  4  4  4     5000   30000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        38 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    6%
Data Units Read:                    2,161,355 [1.10 TB]
Data Units Written:                 154,163,444 [78.9 TB]
Host Read Commands:                 8,882,927
Host Write Commands:                610,221,348
Controller Busy Time:               2,682
Power Cycles:                       24
Power On Hours:                     3,278
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               38 Celsius

Error Information (NVMe Log 0x01, 16 of 255 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged
    9
    Blocklists for AI? (infosec.pub)
     

    I found a few different AI blocklists, but I definitely can't just add these under unbound advanced external blocklists, because then I get everything resolving to 0.0.0.0. Is there a specific format I should be looking for? Are there any blocklists designed for opnSense that I should use?

    EDIT: Ideally, I want to block all the LLM-created websites that show up when you search for anything. Not looking just to block the actual LLMs.

    1
    4b with multiple Zero over USB ethernet? (infosec.pub)
     

    I've got a Zero set up with usb0 as g_ether and a static IP address:

    usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 10.14.0.15  netmask 255.255.255.0  broadcast 10.14.0.255
        ether 7e:24:7d:cc:68:7c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    I have the OTG port connected to one of the four USB ports on a 4b. I'm not sure what the next steps are to get the actual connectivity to function, though. I've seen posts saying that gadget mode is only supported on the USB-C port - does that only mean for using the 4b as a peripheral, or does that mean for any connectivity, even if it's the host?

    view more: next ›