Re: PEM file opened without DIRECT I/O which makes private key readable by attacker exploiting MELTDOWN

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 



I think we are possibly interested in switching to DIRECT IO (given that it bypasses any caching system including page cache) when reading *.PEM file
Sorry, but this makes no sense.
The data could just as well be read from the SSH process
memory space.

Direct IO has some additional complexity; this may well
be avoided.


It makes *zero* sense to panic now and start "hardening"
[which direct IO wouldn't even be!] individual programs -
if separate memory spaces are not available,
   "all hope is lost".

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev



[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux