Quoth Garry :
> OK, so I am running ftpd on 9front, but on connecting I get:
>
> Connected to 192.168.1.108.
> 220 Plan 9 FTP server ready.
> 200 UTF8 always on
> User (192.168.1.108:(none)): glenda
> 331 Need password
> Password:
>
> 534 Command requires tls
> Login failed.
>
> Any ideas of how
Funny enough, I finally got another ethernet daughtboard for my
laptop, and this is apparently the chip (combo?) it has. I've found it
hasn't worked for me yet. I will look into it in the coming days!
Aidan
Quoth tlaro...@kergis.com:
> On Fri, Mar 28, 2025 at 07:24:28PM +1100, Oliver Lowe wrote:
On Fri, Mar 28, 2025 at 07:24:28PM +1100, Oliver Lowe wrote:
> Thanks for the tip!
>
> > I got a fanless mini PC with N100, Plan 9 installed no problem and
> > recognised the network right away.
>
> What model NIC? I'm typing this from a N100 mini PC (running OpenBSD).
> dmesg(8) reports the 2 n
You said "acme's event files on windows". To be absolutely precise: you
mean this kind of window (from p9p and Edwood) (the 29 in this context)?
; 9p ls acme/29
addr
body
ctl
data
editout
errors
event
rdsel
tag
wrsel
xdata
So: what's the exact command line with args that you're running? Because
t
On Fri, Mar 28, 2025 at 07:04:05AM -0700, ron minnich wrote:
> search for: keysight rp2350 hardware attacks
>
> (I'm done including links :-)
>
> Short form: it's getting easier by the day to put together glitching
> hardware, for under $1000, and uncover those keys!
[From the PR departement] Th
Sorry I wasn't really clear, I'm talking about, in your example,
`acme/29/event`. acme(4) explains I can also receive keyboard events and I do,
I can get the characters I enter, but sending them back in has the behaviour I
explained. I'm using `wineventloop` from acme.rc, and my event function i
Aleksandar Kuktin writes:
> I'd like to point out the problem with TPM is that, since the "trust"
> chain originates with the manufacturer, or more accurately with
> whomever controls the manufacturer, you'll never be in complete control
> of the device. "Trusted computing" in this scenario means
On Fri, Mar 28, 2025 at 09:20:44AM -0700, ron minnich wrote:
> The relevance to plan 9: we have this thing we've used for about 30y now,
> known to many of us as sdE0/nvram.
>
> IIUC, on the pre-x86 hardware, it really was a bit of NVRAM, the idea
> being you had some bit of NVRAM on your system,
OK, so I am running ftpd on 9front, but on connecting I get:
Connected to 192.168.1.108.
220 Plan 9 FTP server ready.
200 UTF8 always on
User (192.168.1.108:(none)): glenda
331 Need password
Password:
534 Command requires tls
Login failed.
Any ideas of how to get this work? I am indifferent to w
It's using the rtl8169 driver, but I'm not sure how to get the exact chipset
model, and Googling and Copiloting isn't helping. If you know the command to
run in 9front to get the info you need, let me know I'll run it.
--
9fans: 9fans
Permalink:
https://9f
Thanks for the tip!
> I got a fanless mini PC with N100, Plan 9 installed no problem and
> recognised the network right away.
What model NIC? I'm typing this from a N100 mini PC (running OpenBSD).
dmesg(8) reports the 2 network interfaces as:
"Realtek 8168" rev 0x15: RTL8168H/8111H (0x5
Most current asymmetric cryptography (public key) is vulnerable to
various forms of attacks from quantum computers of a threshold size, not
yet achieved but potentially feasible to see happen in the
not-too-distant future.
Symmetric ciphers (ex. AES, twofish) are generally more resistant.
As
In order to be as compatible as possible with current userland, and to
facilitate diff'ing, I have added the NSEC syscall to Nix and put the Nix added
syscalls after so that there are only additions when comparing.
Todget() has been updated from the 9k version as well and, since the
signature has
>On Fri, 28 Mar 2025 12:26:37 -0700
>"Lyndon Nerenberg (VE7TFX/VE6BBM)" wrote:
>
> ron minnich writes:
>
> > I figure that at some point somebody is going to come in and show
> > us a better way to do it. Should that happen, it's good to be aware
> > of just how real the threats are. So I thought
The relevance to plan 9: we have this thing we've used for about 30y now,
known to many of us as sdE0/nvram.
IIUC, on the pre-x86 hardware, it really was a bit of NVRAM, the idea
being you had some bit of NVRAM on your system, hard to get to, which was a
good place to stash a key.
X86 has always
On Thu, Mar 27, 2025 at 07:47:02AM -0700, ron minnich wrote:
> Off to my day job :-)
Ron,
I've heard rumors (perhaps apocryphal) that there exists
a state of being where there is no "day job" and you can
spend all your time on things that are more intellectually
satisfying than any suit could ever
search for: keysight rp2350 hardware attacks
(I'm done including links :-)
Short form: it's getting easier by the day to put together glitching
hardware, for under $1000, and uncover those keys!
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups
Isn't that what the TPM is supposed to provide in a verifiable way?
Arm's TrustZone presumably provides layered-isolation to keys and
signatures that can be verified all the way to the manufacturer. I'm
guessing they might be the basis for TPM hardware implementation.
On Fri, Mar 28, 2025 at 9:
18 matches
Mail list logo
