Displaying 5 results from an estimated 5 matches for "unneed".
Did you mean:
unneded
2017 Apr 12
3
bind vs. bind-chroot
...I usually run BIND for DNS. I see CentOS offers a
preconfigured (sort of) bind-chroot package. I wonder what's the
effective benefit of this vs. a "normal" BIND setup without chroot. On
my Slackware servers, I have a rather Keep-It-Simple approach to all
things security, e. g. run no unneed services, open only needed ports
etc. but I don't run the extra mile (and haven't been bitten so far).
Any suggestions? (No flamefest please.)
Niki
--
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Web : http://www.microlinux.fr
Mail : info at m...
2009 Feb 28
2
[LLVMdev] Removal of GVStub methods from MachineCodeEmitter, ELFWriter, and MachOWriter
...t/ARM/ARMJITInfo.h
- lib/Target/Alpha/AlphaJITInfo.cpp
- lib/Target/Alpha/AlphaJITInfo.h
- lib/Target/X86/X86JITInfo.h
- lib/Target/X86/X86JITInfo.cpp
to use JITEmitter rather than MachineCodeEmitter.
* renamed multiple MCE's to JE's
* removed unneed getCodeEmitter()'s in JITEmitter.cpp class JIT.
* modified lib/ExecutionEngine/JIT/TargetSelect.cpp to use
include/llvm/ExecutionEngine/JIT/JIT.h include file
* modified lib/ExecutionEngine/JIT/Intercept.cpp to use
include/llvm/ExecutionEngine/JIT/JIT.h include file
I was wondering wh...
2009 Mar 02
0
[LLVMdev] Removal of GVStub methods from MachineCodeEmitter, ELFWriter, and MachOWriter
...ib/Target/Alpha/AlphaJITInfo.cpp
> - lib/Target/Alpha/AlphaJITInfo.h
> - lib/Target/X86/X86JITInfo.h
> - lib/Target/X86/X86JITInfo.cpp
> to use JITEmitter rather than MachineCodeEmitter.
> * renamed multiple MCE's to JE's
> * removed unneed getCodeEmitter()'s in JITEmitter.cpp class JIT.
> * modified lib/ExecutionEngine/JIT/TargetSelect.cpp to use
> include/llvm/ExecutionEngine/JIT/JIT.h include file
> * modified lib/ExecutionEngine/JIT/Intercept.cpp to use include/
> llvm/ExecutionEngine/JIT/JIT.h include f...
2017 Apr 12
0
bind vs. bind-chroot
...for DNS. I see CentOS offers a
> preconfigured (sort of) bind-chroot package. I wonder what's the
> effective benefit of this vs. a "normal" BIND setup without chroot. On
> my Slackware servers, I have a rather Keep-It-Simple approach to all
> things security, e. g. run no unneed services, open only needed ports
> etc. but I don't run the extra mile (and haven't been bitten so far).
>
> Any suggestions? (No flamefest please.)
bind went through a rocky stage where there were a LOT of security holes
in it. by running it in a chroot, you limit its ability...
2017 Apr 13
4
bind vs. bind-chroot
...entOS offers a
>> preconfigured (sort of) bind-chroot package. I wonder what's the
>> effective benefit of this vs. a "normal" BIND setup without chroot. On
>> my Slackware servers, I have a rather Keep-It-Simple approach to all
>> things security, e. g. run no unneed services, open only needed ports
>> etc. but I don't run the extra mile (and haven't been bitten so far).
>>
>> Any suggestions? (No flamefest please.)
>
>
> bind went through a rocky stage where there were a LOT of security
> holes in it. by running it in a...