>Adam Wolk wrote:
>> During the LibreSSL early days there were frequent KNFectomy procedures
>> executed by jsing@. Is the KNFectomy utensil script available
>> publicly? ;) man -k knf yields only style(9).
>
>indent -ci4 -di1 -nlp $1
>
>That's not what joel used, but it's what i have in ~/bin/knf.
>During the LibreSSL early days there were frequent KNFectomy procedures
>executed by jsing@. Is the KNFectomy utensil script available
>publicly? ;) man -k knf yields only style(9).
Most of those tools are kind of busy here and there hand-editing
files, compiling them, testing them.. and then com
> I am a so great fan of computer that I have tears in my eyes and I'm a
> seriously curious guy wanting to know , this are the motives of I post this
> topic. I've been reading a lot on the BSD
> license and GPL license.
>
> Second the position of OpenBSD, source code published under version 2 o
> I am rather late to this thread...
>
> On Thursday 15 October 2015 15:46:47, Raimo Niskanen wrote:
> > > > Are there more password ciphers planned for the future e.g
> > > > sha256 and sha512?>
> > >
> > >
> > > No, we will not be adding those.
> > >
> > >
> > >
> > > Those simple hashes do no
> On Thu, Nov 19, 2015 at 03:36:43PM -0700, Theo de Raadt wrote:
> > > I am rather late to this thread...
> > >
> > > On Thursday 15 October 2015 15:46:47, Raimo Niskanen wrote:
> > > > > > Are there more password ciphers planned
In OpenBSD, we have largely side-stepped these issue... by no longer
pandering to the tweaker-mindset that builds multiboot systems.
We think all the parts are there, but nothing makes it trivial because
the potential set of configurations is too large.
Essentially, you are on your own. :-)
> It
> I am concerned about shutdown message about inability to dd random.seed
> because of read-only file system. What would be the implications of not
> writing it on shutdown?
Huge loss of security in cryptographic situations. This explains
the mechanism it serves:
http://www.openbsd.org/papers/ha
> Thus said Paul de Weerd on Thu, 26 Nov 2015 15:54:11 +0100:
>
> > I'd recommend trying to keep such changes to a minimum: this will be
> > overwritten when you upgrade and it becomes a maintenance burden.
>
> Do files in /etc no longer undergo a round of sysmerge before being
> written?
> The Free Software Foundation (FSF) says that:
>
> "FreeBSD, NetBSD, and OpenBSD all include instructions for obtaining nonfree
> programs in their ports system. In addition, their kernels include nonfree
> firmware blobs.
> Nonfree firmware programs used with Linux, the kernel, are called
> "b
> Saturday I saw this line on tech from Theo:
>
>lpd lpr lpq lprm (yes, legacy software, but still)
>
> Is CUPS become more "the thing" among developers?
Having read CUPS code, and aware of how things interface withit, it is
something I definately try to shy away from.
But it is true that o
> I would buy an official release on USB or preferably sd card, if it
> was on offer. Presumably the production costs would be less as well.
^
How do you figure that?
We put everything on the internet. Thousands upon thousand
> >>(Making them unconditionally read-only would be probably a good thing,
> >>too.)
> >
> > This, too, I see a value in.
>
> And who is going to trust this? There's a significantly higher bar
> to invisibly tampering with a pressed and printed CD than a USB stick.
> (Also it kind-of makes the pre
> Software development. :D
>
> More importantly, what can users do to make it easier for developers to
> write code? That is the important question to ask when a thought like this
> comes up. Is it more efficient of developer time for me to purchase my own
> usb stick and deal with it myself, or
> >> I would buy an official release on USB or preferably sd card, if it
> >> was on offer. Presumably the production costs would be less as well.
> >
> >Cloning CDs from a master is something that can be farmed out
> >relatively easily. Writing an image to USB/SD, not so much, especially
> >when y
> Em 30-11-2015 19:03, Tati Chevron escreveu:
> > Again, the original idea wasn't mine. I commented on the thread, but in
> > my mind, I imagined receiving the install source on a medium that had the
> > same bar to tampering as a CD, such as masked rom. I wasn't thinking of
> > a standard USB fl
> Em 30-11-2015 20:10, Bryan Vyhmeister escreveu:
> > Let's not waste any more of Theo's time. USB sticks are not the magic
> > device that some seem to think. Some are not very reliable and prone to
> > failure. I've had very mixed results with budget USB sticks in
> > particular. Going with a mor
> On Nov 30, 2015, at 2:34 PM, Theo de Raadt wrote:
> >
> > These days the CD revenue is about what a cashier at a store makes.
Uncertain of the veracity of this site,
http://www.payscale.com/research/CA/Job=Cashier/Hourly_Rate/725daaa6/Entry-Level-Calgary-AB
I was wrong. th
> The good news if any, is that Gifts are tax free in Canada, so that part
> is helpful and users should fell they get more out of their money freely
> given as a gift.
>
> http://www.taxtips.ca/personaltax/giftsandinheritances.htm
Correct, but be careful it will not be interpreted later as a non
> Theo: like others in this thread I find it quite shocking and disappointing
> how poorly you are doing financially from your hard work.
Join the club :)
> I apologise if this is too obvious a suggestion but if the foundation is
> making a sufficient income is it not possible for you to draw a s
h a statement along the lines of The OpenBSD
> project leader works full time and receives no support from donations
> to the foundation. If you would like to also support The project
> leader directly then you can do so here or by sending a cheque to.
>
> ___Made up e
>"All I can do is buy the CD's and give some $ to the
>foundation. Any other suggestion is not productive."
>
>I don't think that quite covers it. Those of us who have the choice
>can send checks or Paypal money directly to Theo, as described on the
>Donations page. I think checks are preferable,
> But if we lose the project leader due to lack of exercise and food,
> that's not good for the project. You made it very clear in a previous
> message to this thread that no Foundation money comes to you. So while
> the Foundation may be doing good things with their money, we, the
> community, nee
> I have no clue what a hackathon costs, any ballpark averages?
http://www.openbsdfoundation.org/financials/2014/IncomeStatement2014.txt
http://www.openbsdfoundation.org/financials/2013/IncomeStatement2013.txt
These reports can be compared against http://www.openbsd.org/hackathons.html
to find ev
> I'm trying to make several changes to my disklabel at once. If I try
> to do it with -R to read in a file I get disklabel: ioctl DIOCWDINFO:
> Open partition would move or shrink
You are attempting to change the position or size of a mounted partition.
You can't do that. The filesystem will at
> Consulting could be a good way to raise funds for the project while also
> encouraging usage.
Obviously all the developers should add additional consulting gigs on
the side, to improve freeload.
Unfortunately our software to add additional hours to the day isn't
finished yet, because most of us
Your mistake.
I recommend upgrading to a snapshot.
>
> -current not building:
>
> ./icdb.h -> ./icdb.ph
> pax: pledge: Invalid argument
> *** Error 1 in gnu/usr.bin/perl (Makefile.bsd-wrapper:112 'install')
> *** Error 2 in gnu/usr.bin (:48 'realinstall')
> *** Error 2 in gnu (:48 'realinstall'
> Currently, it's possible, (as root), to do something like:
>
> # mount_mfs -s 1g swap /
>
> which succeeds, and mounts the empty filesystem as the root filesystem.
>
> This makes the machine inoperable and requires a physical reset, without a
> clean shutdown, as no system binaries are availa
> Just found I can set LD_DEBUG to see the full translation process of ld.so.
> This seems to confirm what I've seen in the source: ld.so uses cwd
> instead of process file location for $ORIGIN interpolation.
^
What is that? Generally Unix has no way of doing this
> > It would be that or
> > have the kernel store the whole path for the life of the process for
> > obtaining with sysctl()
>
> That would be great. ps and top would be able to display the path too,
> pretty handy.
How did people get by without needing this in the last three decades?
> On Fri, Dec 11, 2015 at 10:18 AM, Theo de Raadt
> wrote:
> >> Just found I can set LD_DEBUG to see the full translation process of ld.so.
> >> This seems to confirm what I've seen in the source: ld.so uses cwd
> >> instead of process f
> I would like to know if there are others browsers using W^X
> except Firefox, which I know to have this enabled.
> I am especially interested in Chromium package.
run procmap against such processes, looking for pages which are
both "write" and "exece". if you see 1 page that is like that
in a p
> Given that most OS mailing lists/forums seem to be dominated with hardware
> problems my basic question is does OpenBSD have a fallback option to just use
> BIOS routines to get hardware working if even slower than feasible but at
> least working?
No.
> And if not why not?
Because the kernel c
> >Because the kernel cannot know what memory it should leave untouched,
> >to use such BIOS functions.
>
> Why not? I understand that there is some degree of variance amongst BIOS
> uaage of memory but the upper bounds seem to be clearly defined (if I am not
> misinformed). And surely it would be
> By any chance is there a handy list of the utilities compiled into bsd.rd
> (release or recent snap)?
This varies architecture by architecture. Look for files called list
or list*, inside distrib/ARCH/... subdirectories. The specific
location of those files varies, it is not completely clean.
> Seriously, though. The thought must have crossed your mind at least once
> during all these years of mopping up the mess that MS/Intel seem to have
> concocted over the years.
>
> I wonder what a hardware system designed by BSD bootloader, kernel and driver
> hackers would look like. I should exp
> To be fair, i'd love to see the OpenBSD approach to software development
> applied to BIOS/EFI firmware.
>
> For a start, it wouldn't have the nightmare that is Intel AMT sitting below
> the OS and offering a massive security hole.
Gareth,
The OpenBSD process is quite well understood. Use the
> a security consideration, as far as I can see the bootloader loads using INT
> 13h calls. How can the kernel be sure it is really operating in ring 0 and not
> in some VM given that this is the case?
Hey, it looks like you are just trying to be a dick.
Does your mother know?
> But I still maintain that putting an option in the installer to create
> softraid crypto volumes automatically just dumbs down OpenBSD
> unnecessarily, and encourages people to be lazy instead of learning how
> to use the system to it's full potential.
It's great that you have an opinion.
Unfor
> >The OpenBSD process is quite well understood. Use the best methods,
> >doubt what you do, refractor. Simple in concept, but it takes a lot
> >of time.
>
> >Therefore I am looking forward to seeing what you and James can do.
>
> >How long do you think it will take you? Can we expect to see w
> On Tue, Dec 22, 2015 at 02:00:26PM -0700, Theo de Raadt wrote:
> >> But I still maintain that putting an option in the installer to create
> >> softraid crypto volumes automatically just dumbs down OpenBSD
> >> unnecessarily, and encourages people to be lazy inste
> >> a security consideration, as far as I can see the bootloader loads using=
> INT
> >> 13h calls. How can the kernel be sure it is really operating in ring 0 a=
> nd not
> >> in some VM given that this is the case?
>
> >Hey, it looks like you are just trying to be a dick.
>
> On the assumptio
> But I get it, it's hard, so you can throw up your hands and give up by
> saying that's not our problem, not an OS issue.
As coders, it is very much not our problem.
We just happen to run on some vendor hardware, often poorly documented
and inconsistant generation to generation (even when it is
> Stuart Henderson wrote:
> > On 2015-12-23, Jack J. Woehr wrote:
> >> Ted Unangst wrote:
> >>> improvements to the installer are welcome. suggestions that the installer
> >>> could use javascript to write cookies are not an improvement.
> >> The installer could use a beer tap so we could have a c
>I wanna make a c program that checks for a PKG_PATH that exists and
>connects to a workable link for pkg_add().
and I wanna build a rocket ship...
You are building using the wrong procedures.
You didn't do your homework, and it blew up in your face. Then you
wrote a few paragraphs. Then I replied. That is the whole sad story.
Hundreds of people succeed daily.
>Because there seemed to be more patches than normal in 5.8, and I am lazy and
>I'll say we should go for the spaceship project ... with lasers.
Index: pkg_add.1
===
RCS file: /cvs/src/usr.sbin/pkg_add/pkg_add.1,v
retrieving revision 1.134
diff -u -p -u -r1.134 pkg_add.1
--- pkg_add.1 4 Nov 2015 16:59:58 -
Important SSH patch coming soon. For now, every on all operating
systems, please do the following:
Add undocumented "UseRoaming no" to ssh_config or use "-oUseRoaming=no"
to prevent upcoming #openssh client bug CVE-2016-0777. More later.
> I'me running a couple of openbsd routers running (still OpenBSD 6.0)
> with carp failover and ospfd+ospf6d. Everything seems running fine but i
> see clockwork every 5 min the following message:
>
> ospfd[PROCESSID]: desync; scheduling fib reload
> ospfd[PROCESSID]: reload interface list and rou
> > On Sun, Oct 29, 2017 at 12:32:58PM +0100, Marko Cupa?? wrote:
> > > I know read-only setups are unsupported, modifying base files as
> > > well, but if someone has an advice on what would be a better way of
> > > remounting local file systems read-only after kernel relinking is done,
> > > I'd
> > Build time of cups isn't really an issue. But the dependency chain
> > around cups is already very delicate, and anything involving optional
> > dependencies for a library gets *really* awkward further down the chain.
>
> How about package splitting? cups doesn't require avahi binaries or XML
> > So basically you are saying the ports developers, who have worked very
> > hard, haven't built things exactly the way you want.
> > Did I get that right?
>
> Nobody apparently cared about it (neither do I really). It's an idea to
> be discussed (or not), not a proposal to have an answer right
> > No. OpenBSD is a developer-oriented system, so headers are an
> > integral part of the installation. Installing them must not be
> > optional, or it will cause nothing but needless confusion as soon
> > as people actually start using what they installed.
>
> And what if someone wants to buil
>I was finally able to bring our OpenBSD based Network Management System up
>to the current OS release (it was a couple of years out of date) but this
>process broke access to a large number of older HP switches on our network.
>Thorough analysis of the problem and study of the source code lead me
>A question to the experts here.
>
>My home router (a crappy one provided by my ISP) has ipv6 disabled, at
>least it's what its guied configuration tells me. :-) And I have ipv6
>disabled in all my LAN machines. The laptop I use with OpenBSD has
>slaacd(8) up and running by default, even when I d
>On Sat, Nov 11, 2017 at 05:58:59AM -0700, Theo de Raadt wrote:
>> >A question to the experts here.
>> >
>> >My home router (a crappy one provided by my ISP) has ipv6 disabled, at
>> >least it's what its guied configuration tells me. :-) And I have ip
> On Wed, Nov 15, 2017 at 3:06 PM, Gareth Nelson wr=
> ote:
> > Use key-based authentication?
> >
>
> Okay, but that doesn't fit the requirement.
> I want something iteratively password free.
> AFAIK, somewhere along the line in key-based authentication you need
> to enter a password to unlock th
> On Linux, I'm really not sure that a channel returned by socketpair
> would ensure confidentiality
Huh? Why not?
> On 16 nov. 2017 =C3=A0 22:15 +0100, Theo de Raadt ,
> wrote:
> > > On Linux, I'm really not sure that a channel returned by socketpair
> > > would ensure confidentiality
> >
> > Huh? Why not?
> >
> /proc/pid/fd
I'm speaking more generally
> On Mon, Nov 20, 2017 at 08:37:43AM +, Roderick wrote:
>
> > Commenting out the line "/usr/libexec/reorder_kernel &" at the
> > end of rc?
> >
> > I suspect it is not forseen not to benefice of KARL.
>
> No, actually, if the hash of the kernel is different than expected, the
> reorder_kerne
> > If someone wants to solve this fully there have been some proposals
> > for keeping track of the instruction sequence, and attempting to
> > reapply it upon each relink in the build directory. There just hasn't
> > been any scripting changes to do that from anyone, and it isn't on my
> > radar
> https://escholarship.org/content/qt17j227zv/qt17j227zv.pdf
>
> Thoughts on this?
Lots of misunderstandings in there.
The goal is to make addresses unguessable.
One does not need full entropy for that, because attack code doesn't
have the luxury of doing a search. Attack code does 1 memory ac
> theo wrote:
> > And, we have focused on never reusuing an address space after a crash,
> > by designing software to use fork+exec.
>
> I'm not sure I understand this point?
Then it is probably over your head. Not much I can do about that.
> When an attacker tries to exploit e.g. an overflow the child is likely
> to crash, but the next attempt after a crash of the child will find a
> new address layout, making it harder to re-use information gathered in
> the previous attempt.
>
> -Otto
>
Actually Otto the word "harder" both
> theo wrote:
> > Then it is probably over your head.
>
> You guessed wrong :)
>
> > Not much I can do about that.
>
> Yes you can, s/reusing/continuing to use/.
That interpretation is wrong. You don't understand fork+exec. There
is no decision to stop using an address space after failure.
>Jay Williams wrote on Wed, Nov 29, 2017 at 11:34:21AM -0600:
>
>> P.S. Does anyone know why the official OpenBSD store doesn't sell
>> stickers? I bet they'd be a big seller!
>
>People loved them while they were still sold, but in the end, even
>though they were accompanied by installable CDs sets
> Currently the OpenBSD store has mugs, t-shirts, posters, and CDs. All of
> those require more expense than stickers. Stickers are rather inexpensive
> to produce, can be sold for high markup, and cost very little to ship, not
> to mention are very popular, especially in the tech industry.
>
> It
> My goal is not to rip off anyone, but to help the project.
You cannot help the project by begging on a mailing list that
I partake in business.
Get over yourself Jay.
> As a response to this, Theo asked rhetorically "Where's ls, where's cat,
> where's grep, and where's sort?", implying that noone so far bothered to
> write implementations of even the basic unix utilities in such a
> language.
I wasn't implying. I was stating a fact. There has been no attempt
won't help.
it does not adjust the scheduler in that way, at all
> just wondering if anyone else has tried using renice to
> de-prioritise other processes in an effort to give more cpu
> time to packet forwarding in the kernel ?
>
> While Im certain that there significant risks to system stabili
If you self-modify /bsd, the hash will disagree.
That deactivates kernel relinking. That is used by developers.
re-create the hash
> Predrag Punosevac wrote:
> >
> > # uname -a
> > OpenBSD oko.bagdala2.net 6.2 GENERIC.MP#0 amd64
> >
> > # syspatch
> > Get/Verify syspatch62-002_fktrace...
>On 2017-12-06, ti...@openmailbox.org wrote:
>
>> If TRIM would be implemented someday, one thing that would be
>> neat would be that crypto and other softraid would propagate the
>> TRIM. That would be a nice combination between wear level resiliency
>> and disk data safety.
>
>That runs counter
> Ada 2012? increased the use of pointers but still limits their usage.
>
> Aside from a couple of mentions in style(9) is there any info on
> OpenBSD's rules around pointers or is it simply avoid unless necessary
> and following general good practice?
Wow what a broad useless question.
> By entering as su/doas sysctl kern.bufcachepercent=80 shows me the
> change from default=20 to 80 as expected, but after a reboot the value
> is set again/still to 20 (%).
sysctl changes the running state. It does not change that file
for future boots.
Dinesh --
everything you say below is a giganic pile of dung. We make all our
software available to everyone. The internet spans the planet.
You are making stuff up, and it is not appreciated how you appear to
be misrepresenting the project.
Please go fluff up your sense of selfworth elsewhere
> Ted Unangst wrote:
> > Otto Moerbeek wrote:
> > > Sparc64 and powerpc also have speculative execution, branch
> > > prediction and extensive caches. It is much wiser to assume they are
> > > also affected by (similar) bugs/explots or whatever you call it.
> >
> > A lot of the commonly available
> I've got an old server (OpenBSD 4.7 old) with a mixed bag of password hashes
> in master.passwd. A majority of the passwords (hundreds) are old salted
> DES crypt format.
bummer
> Am I correct in my research that everything but Blowfish was removed from
> crypt() around OpenBSD 5.7? Are there a
> I was hoping that there was some hidden switch somewhere that would turn
> the classic crypt back on. No such luck.
That'd be like leaving a running chainsaw on the floor at a daycare center.
When something is dangerous, we get rid of it.
> This is the firmware i've currently installed:
>
>$ doas fw_update -i
>Installed: intel-firmware-20180108
That has nothing to do with:
>error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to
> load firmware i915/bxt_dmc_ver1.bin (-22)
I recognize something doesn't wo
> Is there, by chance, such a breakdown available for these already?
No. We did our best.
Always interesting that the more one works in the free software
space, the more constraints get added by the public.
Sometimes it is almost like there is a stream of people who want us
to stop trying.
And
>FWIW, the permission I seek is from my Legal department.
That maybe your job but it isn't the project's job.
We could write the document you need. Then the next comment would
probably we that we didn't publish our procedure and have a lawyer
sign off on what we did.
It is a neverending battle.
> On 01/19/18 01:12, Theo de Raadt wrote:
> >> FWIW, the permission I seek is from my Legal department.
> >
> > That maybe your job but it isn't the project's job.
>
> > Enough is enough. That sentence above makes it clear who is getting
>
So fix it, or pay someone to fix it.
Do you think your complaints should make people jump to attention?
> It is clear, but what do now when potentially 'buggy' software must
> work? There is no any transient period provided.
>
> ln - s 'j' /etc/malloc.conf partially resolves the problem with bug
It is software you use.
So take responsibility for it
Picking on random people to solve your problem is insane
> This is distributed DNS, so must work 24/7. It will be fixed soon.
>
> No complaints, no jumps at all.
>
> On 1/25/2018 9:34 AM, Theo de Raadt wrote:
> > So f
I think you have interpreted the situation backwards.
The wxallowed flag is not on other filesystems. Therefore, binaries
on those filesystems which misbehave will fail.
There are about 15 programs which need fixing, and the wxallowed could
become a piece of history.
Unfortunately some of those
> So, I have to identify which ones are exactly broken (Stuart Henderson
> said this is the trickier part), contact their developers (if the
> software is not abandoned) and send patches, right?
Your approach of making the world better will be "getting in their face"?
You have some sort of list.
> Resume after suspend fails on a Zenbook UX390UA if (and only if) the
> USB hub/adapter that comes with it is connected.
Is that a pure USB dock, or is it something else? Does it connect with
a pure USB connector?
Maybe the resume-side EFI/ACPI/SMI makes assumptions about it?
At suspend time,
Have you ever heard of the concept of helping yourself?
> Does any of my hardware work in -current?
> Lots of stuff fails in 6.2 stable.
> WiFi and touchpad being especially desired, of course!
>
> If WiFi isn't a go, can anyone recommend a USB WiFi stick?
>
> Thanks,
> Chris Bennett
>
>
> Ope
> I install OpenBSD on my Fastwell CPB905 Singleboard compter. IT have
> 4-RS-232 port on same IRQ, but on different address on isa bus. Then i
> setup only one port using configure command all ports work normally. But
> when i setup 2 of them in one boot configuration i get in dmesg: irq
> already
>When it comes to Meltdown:
>Does OpenBSD is going to release patches for 6.2? I don't see anything related
>to Meltdown in errata, but maybe it is too early. I understand other OSes
>received disclosed information about bug a few months earlier.
amd64 snapshots contain a fix, which is undergoing
> It isn't just this. Qt 5.10 introduces new dependency on OpenSSL 1.1
> APIs for improved security, and LibreSSL does not implement those APIs
> at all.
The 1.1 API does not improve security.
If anything, the new API requires to you repeat the same or similar
arguments to many functions, and in
Unfortunately noone cares.
>The #OpenBSD IRC channel on FreeNode is listed under "OpenBSD
>Resources" at www.openbsd.org , so it is official to some degree.
>
>Blakkheim (I think he is t...@openbsd.org) is insisting with abusing his
>administrator privilege there, today by blocking me again.
>
>He
>If someone is able to provide a fake ISO, he will also provide fake
>SHA256.sig and/or fake public key on the ISO. So there is no gain to
>provide such material as people will think "it is safe" whereas it is
>not.
that is true.
however, the real reason it isn't on the media is that internal
sig
>On Tue, 20 Feb 2018 18:45:01 +0100
>Stefan Sperling wrote:
>
>> > I download SHA256.sig abd file sets from mirror, how can I trust it?
>>
>> You run a trusted signify binary, which was not obtained from the
>> mirror but is part of your existing install, to check the signature
>> on SHA256.sig.
> On 2018-03-07, jungle Boogie wrote:
> > Hi All,
> >
> > With the latest openbsd snapshot:
> > OpenBSD 6.3-beta (GENERIC.MP) #40: Wed Mar 7 12:51:00 MST 201
> >
> > It seems I cannot build or update go projects:
> >
> > $ go get -u github.com/justwatchcom/gopass
> > Abort trap (core dump
It is a library routine that calls a system call.
It isn't worth changing at this point.
> I find sysctl(3) in OpenBSD 6.2 is changed to system call in -current
> (please refer the manual: https://man.openbsd.org/sysctl.2).
>
> So the sysctl would be a system call instead of library function in
> If a process forks two children does the parent need separate imsg
> bufs for each? I'm thinking one will do and just use the header to
> decide who it's from. Is that correct or should they be separated?
The socket layer will conspire against you.
> Running that PoC on the machine while in -current and even 6.1 (no
> patches) returns that the system is not vulnerable to meltdown. This
> processor was made in 2016 and everything I've read indicates that it
> should be vulnerable.
Such a low-grade processor may not have sufficient speculative
> According to some sources, Intel and a handful of others have known about the
> issue since February 2017(!), so perhaps it has already been patched in the
> 08Jan2018 BIOS. I too have doubts that to date any processor has been
> redesigned to avoid the flaws entirely, but then again...
Sure. A
> On Tue, Mar 13, 2018 at 10:39 PM, Theo de Raadt wrote:
> >> According to some sources, Intel and a handful of others have known about
> >> the
> >> issue since February 2017(!), so perhaps it has already been patched in the
> >> 08Jan2018 BIOS. I too hav
> If the adapter is ejected before closing the laptop lid there is no
> problem waking from sleep. But is a minor inconvenience to eject the
> adapter. Would it be possible to patch the kernel some how to make it
> think the adapter is ejected before entering sleep?
It does that. The problem is s
501 - 600 of 3011 matches
Mail list logo
