search for: eics

Hi folks, As part of our build, the Tock project uses remap-path-prefix [1] to create a reproducible build. This means that the paths inside of built artifacts are not full source paths. When we later attempt to produce a listings file, the source mapping fails. The result is many copies of this recently merged warning [2]: llvm-objdump: warning:

I have not, I'll look into that one, thanks! On 11/14/2019 9:48 AM, SternData wrote: > Do you run rkhunter? > > On 11/14/19 9:40 AM, Christopher Wensink wrote: >> How do you know when a Linux system has been compromised?? >> >> Every day I watch our systems with all the typical tools, ps, top, who, >> I watch firewall / IPS logs, I have logwatch setup and

...are the advises of what to look for. One of the things you can set up is [host based, maybe] system integrity checking system (or intrusion detection system). That only makes sense on freshly installed system in known good state. There were a variety of these: tripwire (which went commercial), eics, ... If you search for linux intrusion detection system you should find what you need. I hope, this helps. Valeri >>> >>> Every day I watch our systems with all the typical tools, ps, top, who, >>> I watch firewall / IPS logs, I have logwatch setup and mailing daily &...

https://bugzilla.netfilter.org/show_bug.cgi?id=893 Summary: Support upstream docbook2x location Product: nftables Version: unspecified Platform: All URL: https://bugs.archlinux.org/task/38706 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: nft AssignedTo:

To the R users community: (We apologize for multiples copies) (Please distribute) --------------------------------------------------------------------------- 1st Call for Papers - 2nd International Symposium on Distributed Computing and Artificial Intelligence (DCAI'09) June 10th - 12th , 2009 - Salamanca - Spain http://dcai.usal.es/ The International Symposium on Distributed Computing and

No, we haven't been hacked. ;) We have a prospective client who is asking us what our policy is in the event of unauthorized access. Obviously you fix the system(s) that have been compromised, but what steps do you take to mitigate the effects of a breach? What is industry best practice? So far, searches haven't produced anything that looks consistent, except maybe identity monitoring

I /wander <http://hoyo.cf/lists/lt.php?id=YUgMAABRGAFRXR1QWlQKVF0F> / loudly if there's any etymological relationship between the words "/annuit/" (an /knew/ it) and "/eloheinu/;" (el, /oh he knew; /heinous, I /see/ too) in just a few moments I'll find out what those words actually mean as opposed to their Adamic definition(s)... which are quite similar; throwing

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to

There is a new fallthrough pseudo-keyword macro that can be used to replace the various /* fallthrough */ style comments that are used to indicate a case label code block is intended to fallthrough to the next case label block. See commit 294f69e662d1 ("compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use") These patches are intended to allow clang to