similar to: windigo post-mortem

Displaying 20 results from an estimated 200 matches similar to: "windigo post-mortem"

2014 Mar 19
2
Linux malware attack
SlashDot had an article today on a Linux server malware attack, <http://it.slashdot.org/story/14/03/18/2218237/malware-attack-infected-25000-linuxunix-servers>. I wonder if there is a simple test to see if a CentOS machine has been infected in this way? The article mentions Yara and Snort rules to test for this, but I wonder if there is something simpler? Alternatively, are there Yara or
2024 Apr 02
2
Debian openssh option review: considering splitting out GSS-API key exchange
[I've CCed openssh-unix-dev for awareness, but set Mail-Followup-To to just debian-devel and debian-ssh to avoid potentially spamming them with a long discussion. If you choose to override this then that's your call, but please be mindful of upstream's time.] Following the xz-utils backdoor, I'm reconsidering some choices in Debian's OpenSSH packaging. Please note that
2014 Apr 07
4
[Bug 2223] New: Ed25519 support in SSHFP DNS resource records
https://bugzilla.mindrot.org/show_bug.cgi?id=2223 Bug ID: 2223 Summary: Ed25519 support in SSHFP DNS resource records Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at
2011 Oct 11
0
Post Mortem 1 huge grafical issues
Hi everybody, The Game Post Mortem 1 is unplayable in my wine. This is causing by huge grafical issues. Items are not correct drawn and People "flashes". Here is waht the Console says: Code: pingi at 16L:/media/32GB-usb3/Spiel_1/Programme/Microids/Post Mortem$ wine "Post Mortem.exe" fixme:win:EnumDisplayDevicesW ((null),0,0x32ee4c,0x00000000), stub!
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> Bash 2.05b on Linux handles this fine. I was asking what > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > Perhaps you can: > > SHELL=/usr/bin/bash ; export SHELL > > in your script below just before it runs NightlyTest.pl? I'm not sure if > that will work or not. I have: SHELL=/bin/tcsh sh, csh, tcsh not support nested () OK, root
2004 Sep 09
0
[LLVMdev] POST MORTEM: llvm-test changes
On Sun, 05 Sep 2004 14:02:26 -0700 Reid Spencer <reid at x10sys.com> wrote: > > Assertion failed: ((FieldSizeTree != NULL_TREE) && "Struct/Union member of unknown length!"), function llvm_expand_constructor_elements, file ../../src/gcc/llvm-expand.c, line 3791. > > /usr/home/llvm/obj/../test/Regression/CFrontend/2004-01-01-UnknownInitSize.c:11: internal compiler
2004 Sep 10
0
[LLVMdev] POST MORTEM: llvm-test changes
On Thu, 9 Sep 2004 08:52:10 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > > I haven't got around to this yet but I will. The odds are good the > > problem is in a BSD system header file so I need to capture the > > preprocessed source. > > I guess not... the file 2004-01-01-UnknownInitSize.c does not include > anything else, so there is no preprocessed
2004 Sep 09
2
[LLVMdev] POST MORTEM: llvm-test changes
> I haven't got around to this yet but I will. The odds are good the > problem is in a BSD system header file so I need to capture the > preprocessed source. I guess not... the file 2004-01-01-UnknownInitSize.c does not include anything else, so there is no preprocessed source to capture...
2016 Nov 14
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Sun, 13 Nov 2016 13:11:38 +0100 writes: > Dear R friends, to allow post-mortem debugging In my > Rscript based batch jobs I use > tryCatch( <R expression>, error = function(e) { > dump.frames(to.file = TRUE) }) > to write the called frames into a
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> x86 FreeBSD: > * hasn't run with changes yet I manually start script. I use this options (+ -verbose now for testing) /home/wanderer/pkg/build/llvm/src/llvm/utils/NightlyTest.pl -parallel -enable-linscan -noexternals -noremove :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm /home/wanderer/pkg/build/llvm/night/build
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir
2004 Sep 06
0
[LLVMdev] POST MORTEM: llvm-test changes
After fixing nested () problem manual run nighttest finished successfully with one remarkable logged problem: INITIALIZED CVS Root = :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm BuildDir = /home/wanderer/pkg/build/llvm/night/build WebDir = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD Prefix = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD/2004-09-06
2004 Sep 05
3
[LLVMdev] POST MORTEM: llvm-test changes
Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >
2016 Nov 15
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Tue, 15 Nov 2016 01:15:46 +0100 writes: > Martin, thanks for the good news and sorry for wasting your (and others > time) by not doing my homework and query bugzilla first (lesson learned! > ). > > I have tested the new implementation from R-devel and observe a semantic >
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >
2014 Apr 04
6
[Bug 2220] New: Add uuid-style identifier for use with ControlPath
https://bugzilla.mindrot.org/show_bug.cgi?id=2220 Bug ID: 2220 Summary: Add uuid-style identifier for use with ControlPath Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
On Sun, 2004-09-05 at 13:48, Jeff Cohen wrote: > On Sun, 05 Sep 2004 10:49:44 -0700 > Reid Spencer <reid at x10sys.com> wrote: > > > Jeff, > > > > Actually, that was my fault. I forgot to remove the non-existent > > directories from the configure.ac file. That's done and committed > > now, so the advice is still the same: update configure script
2014 Jan 18
9
[Bug 2197] New: Add ED25519 support to SSHFP dns record
https://bugzilla.mindrot.org/show_bug.cgi?id=2197 Bug ID: 2197 Summary: Add ED25519 support to SSHFP dns record Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at
2016 Nov 13
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
Dear R friends, to allow post-mortem debugging In my Rscript based batch jobs I use tryCatch( <R expression>, error = function(e) { dump.frames(to.file = TRUE) }) to write the called frames into a dump file. This is similar to the method recommended in the "Writing R extensions" manual in section 4.2 Debugging R code (page 96):