digshadow has quit [Ping timeout: 264 seconds]
digshadow has joined ##openfpga
<pointfree> Why are pin headers so much cheaper on amazon vs digikey, etc? I could save $69.65 from my bom cost if I sourced from amazon.com instead.
<pointfree> *OT
<rqou> i used to wonder that too
<rqou> and then i bought a bunch of really cheap pin headers from aliexpress and tried them
<rqou> solder doesn't wet onto them properly for some reason
<pointfree> They have gold pins, so they should be easier to solder and I haven't seen any complains about soldering them in the reviews.
<rqou> idk about those specifically
<rqou> i went on aliexpress and found basically the absolute cheapest
<rqou> those do have "gold" pins too
<rqou> but i don't care because i intended them to be used for hack jobs
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<awygle> when i did the same the ones i bought just melted under application of an iron
<awygle> (not the metal, the plastic bits - the metal then fell out)
<rqou> oh yeah, that happens too
m_t has quit [Quit: Leaving]
<Zorix> the machined round headers are so much more expensive too
digshadow has quit [Ping timeout: 252 seconds]
digshadow has joined ##openfpga
azonenberg_work has quit [Ping timeout: 252 seconds]
azonenberg_work has joined ##openfpga
<rqou> azonenberg_work: are you familiar with OpTiMSoC?
<rqou> it's apparently another NoC design
<azonenberg_work> Nope i'm not
<rqou> from a quick glance, it looks like an "ecosystem" project rather than a "research" project
azonenberg_work has quit [Ping timeout: 252 seconds]
[X-Scale] has joined ##openfpga
SpaceCoaster has quit [Ping timeout: 255 seconds]
eduardo__ has quit [Ping timeout: 240 seconds]
eduardo__ has joined ##openfpga
X-Scale has quit [Ping timeout: 260 seconds]
[X-Scale] is now known as X-Scale
openfpga-bb has quit [Ping timeout: 240 seconds]
knielsen has quit [Ping timeout: 260 seconds]
knielsen has joined ##openfpga
SpaceCoaster has joined ##openfpga
openfpga-bb has joined ##openfpga
_whitelogger has joined ##openfpga
teepee has joined ##openfpga
teepee has quit [Ping timeout: 252 seconds]
teepee has joined ##openfpga
m_t has joined ##openfpga
teepee has quit [Ping timeout: 240 seconds]
teepee has joined ##openfpga
teepee has quit [Ping timeout: 258 seconds]
teepee has joined ##openfpga
pie_ has joined ##openfpga
test123456 has joined ##openfpga
enriq has joined ##openfpga
enriq has quit [Remote host closed the connection]
test123456 has quit [Quit: Leaving]
enriq has joined ##openfpga
azonenberg_work has joined ##openfpga
azonenberg_work has quit [Ping timeout: 240 seconds]
brizzo has quit [Ping timeout: 246 seconds]
<rqou> wow, amazon's algorithms are shit
<rqou> i ordered a respirator (for future chip decap lab) and now amazon is recommending me to buy all the permutations of filter cartridges
<rqou> that's now how this works amazon
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
brizzo has joined ##openfpga
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined ##openfpga
<balrog> rqou: welcome to web advertising
<balrog> cookie tracking FTW!
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined ##openfpga
enriq has joined ##openfpga
digshadow has quit [Quit: Leaving.]
azonenberg_work has joined ##openfpga
<rqou> o/ azonenberg_work
<rqou> when are you returning?
<azonenberg_work> o.
<azonenberg_work> o/ *
<azonenberg_work> checked in for my flight earlier today
<azonenberg_work> I land 16:00ish Pacific tomorrow (Saturday)
eduardo_ has joined ##openfpga
eduardo__ has quit [Ping timeout: 252 seconds]
digshadow has joined ##openfpga
<pie_> not the board but whatever he is talking about
<azonenberg_work> pie_: he's convinced that a power fet with a thermal pad is a concealed BGA
<pie_> uhuh
<azonenberg_work> his badbios explorations have long since descended into the realm of outright paranoia
<azonenberg_work> and he doesnt have the hardware experience to know half the things he freaks out about are normal
<azonenberg_work> Like vias in thermal pads
<pie_> azonenberg_work is a fed1! :PP
<pie_> i see.
<balrog> lolwut
<azonenberg_work> pie_: look up some of the work sophia d'antoine did a year or two ago at usenix WOOT
<azonenberg_work> on cross-VM data leakage using OoO side channels
<azonenberg_work> I think her explanation of how the channel works is not 100% accurate, but the channel undeniably exists
<azonenberg_work> basically by heavily loading certain resources in one VM you can cause instruction reordering changes in a different VM
<pie_> yeah im seeing so much stuff on cache based side channels latwly heh
<pie_> *letely
<pie_> *lately
<pie_> huh interesting.
<azonenberg_work> I'm not convinced it's a true silicon side channel vs a hypervisor one, or possibly something based on memory operation reordering in the northbridge vs instruction reordering in the CPU proper
<azonenberg_work> But the channel exists and i'm not disputing that
<pie_> this "privileged silicon sidechannel" (my phrasing, just asspulled it) concept sounds rather interesting
<lain> there was some articles lately about uhhh
<lain> something about overclocking arm chips to cause trustzone to derp and flip a byte that allows privesc
<lain> which sounded specious, so I checked the paper, and sure enough they say some shit like "All that is required is a malicious kernel driver"
<lain> yeah ok last I checked that's not an easy thing to just slip into a mobile app :P
<lain> am I missing something or is that less of a threat than the paper makes it out to be? they act like it's a huge silicon bug that kernel drivers can poke performance registers and cause an overclock...
<azonenberg_work> Lool
<azonenberg_work> well
<azonenberg_work> what i see as interesting is, the kernel is not supposed to be able to see/modify trustzone state
<azonenberg_work> So if the kernel can OC the chip to the point that TZ malfunctions, that is an issue for privesc/jailbreak type applications
<azonenberg_work> It's not going to lead to RCE though
digshadow has left ##openfpga [##openfpga]
digshadow has joined ##openfpga
gnufan has left ##openfpga [##openfpga]
soylentyellow has quit [Ping timeout: 246 seconds]
<lain> yeah
<lain> I didn't read the whole paper to see how reliable their OC -> TZ privesc was
<lain> I'm guessing "not very" but it'd be interesting if they managed to make it reliable somehow
<lain> the articles suggested that they were using /userland/ code to OC, which would be disastrous if true, but the paper says it's a kernel driver
soylentyellow has joined ##openfpga
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
azonenberg_work has quit [Ping timeout: 240 seconds]
_whitelogger has joined ##openfpga
m_t has quit [Quit: Leaving]
<pie_> ugh anyone know how to make freebsd-update go faster
<awygle> I once built a server to do binary updates of freebsd hosts for exactly that reason
<mtp> freebsd-update already does binary patching iirc
<awygle> Huh, so it does.
<awygle> Been a while. I think we were building world ourselves for some reason.
<awygle> I may have actually built a local freebsd-update server, come to think
<awygle> -shrug-
<mtp> i like that that's supported tbh
<mtp> in case you do patch your world
<mtp> anyway there isn't really a way to make it go faster short of throwing faster resources at the bottleneck :P
<awygle> I feel like the word "world" is really dramatic for some reason lol
<awygle> pie_: what are you running freebsd for?
<pie_> some personal stuff
<pie_> more like learning to run freebsd though lol
<mtp> i much prefer freebsd to linux fwiw
<awygle> this distributed placer project makes me miss freebsd networking, much better than Linux in many ways
<pie_> help
<pie_> its askimg me to resolve a merge conflict on a config file
<mtp> yeah it does that
<pie_> idk how
<pie_> i mean i have it open in the editor but how do i choose what to keep
<mtp> depends on how different the config is tbh. i always pick the new $Id:$ lines but each conflict is a case-by-case thing :/
<pie_> i mean idk how the format wors
<pie_> works
<mtp> generally the conflicting sections are set off with >>> === <<<
<mtp> where it goes original then new
<pie_> heres probably the important part https://pastebin.com/DxeJEvrZ
<pie_> ok but do i edit it and just remove everything i dont want to keep?
<mtp> no
<mtp> i mean hold up
<mtp> delete the <<< and === and >>> lines
<mtp> and the chunk you don't want to keep, which is probably the uncommented VersionAddendum line
<Zorix> merge conflicts.. that gets ugly..
<pie_> i mean the end result i save should be how i want it to look
<mtp> yeah
<pie_> ok
<mtp> exactly
<mtp> zorix i really don't know why people are so terrified of merge conflicts :/
<pie_> uh fuck this uses vi
<pie_> i have no idea how the fuck to use vi
<Zorix> i never liked dealing with merge conflicts
<mtp> i don't like dealing with Git merge conflicts but that's because git is user-hostile
<Zorix> i used to deal with it a lot when i was rebasing code i was working on for mame
<Zorix> yea the git one heh
<awygle> pie_: dd deletes lines, :wq saves and quits
<Zorix> always learn vi/vim
<awygle> Oh and j goes down, k goes up
<Zorix> you will need to use it at some point
<mtp> nah
<mtp> export EDITOR=ed
<mtp> ;)
<Zorix> thats even more special heh
<mtp> that's unironically my $EDITOR
<Zorix> i do all my code in vim
<awygle> I hate when I'm in vim but don't have my vimrc. Esc instead of jk to return to normal mode makes me feel briefly brain damaged every time
<Zorix> thats why i forced myself to learn stock behavior because i dont want to lean on a modification
<awygle> I get your point but also customization is a lot of the power
<Zorix> yep it has a lot of customization
<Zorix> when you are working with a single or a few systems it can be helpful
<Zorix> but i administer about 80 or so systems so i cant depend on that modification on all of them
<pie_> automatically copy your rc file over?
<pie_> :P
<Zorix> thats just ridiculous and lazy heh
<pie_> why?
<pie_> awygle, do i *need* to reboot after upgraing 10.0 to 10.3 or can i then upgrade to 11.1?
<pie_> * mtp
<awygle> Zorix: I've legitimately considered trying to use vimscript to automatically download my vimrc into ram or something
<awygle> pie_: I'd reboot. It would probably work if you didn't but if it goes wrong it'll go really wrong
<pie_> well here goes nothin
<Zorix> hehe
<pie_> my hdd is making close to floppy disk whirring nises, its probably fine but its unnerving.
<pie_> mtp, what the heck i upgraded and rebootet but im still on the same version
<Zorix> have to reboot at least 3 times
<Zorix> joking of course
<awygle> upgrade --no-seriously-you-guys-this-isnt-funny
<pie_> haha