Displaying 20 results from an estimated 1713 matches for "suspiciously".
2017 Aug 24
2
dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c: 4 * suspicious expression ?
Hello there,
dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:130]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses.
Source code is
if ((ret = doveadm_print_istream(input) < 0))
Maybe better code
if ((ret = doveadm_print_istream(input)) < 0)
Some duplicates:
[dovecot-2.2.32/src/doveadm/doveadm-mail-fetch.c:220]: (style) Suspicious
2017 Dec 19
3
detect suspicious logins
does anyone know of a linux module (maybe similar to fail2ban) that
could be installed which would monitor email logs (sign ins) and alert
the user to any suspicious activity on their account? i suspect it
would need to log geo location, device type and ip address to a
database. it seems like a module like this would be very useful and
should exist already? thanks in advance
2005 Jan 11
3
Think someone has got into my server...
I have just run chkrootkit on my server and have the following two
suspicious entries..
Searching for suspicious files and dirs, it may take a while...
/usr/lib/perl5/5.8.0/i386-linux-thread-multi/.packlist
and further down..
Checking `bindshell'... INFECTED (PORTS: 465)
Anyone have any advice for getting rid of it??
Later..
2014 Jul 31
2
[LLVMdev] suspicious typo in MCObjectDisassembler.cpp
my compiler gave me a warning in MCObjectDisassembler.cpp. it found a
self-comparation in loop condition. I think it's a typo.
the suspicious code was introduced by this patch:
>From f176482752fbea3139394e280adfb10270dd3aac Mon Sep 17 00:00:00 2001
From: Ahmed Bougacha <ahmed.bougacha at gmail.com>
Date: Wed, 21 Aug 2013 07:28:55 +0000
Subject: MC CFG: Support disassembly at
2010 Aug 08
1
[LLVMdev] Suspicious code in backend scheduler
Hello,
Still trying to write a custom scheduler, I stumbled accross a highly
suspicious code in all schedulers.
In both ScheduleDAGFast.cpp and ScheduleDAGRRList.cpp, one can find this
piece of code:
SUnit *CopyFromSU = CreateNewSUnit(NULL);
and then in the same files:
SUnit *CreateNewSUnit(SDNode *N) {
[...]
SUnit *NewNode = NewSUnit(N);
And finally in ScheduleDAGSDNodes.cpp:
SUnit
2006 Aug 03
1
Suspicious sshd log messages in my syslog
Hello All,
I'm using OpenSSH 4.3p2. I'm getting few messages in my syslog and it is
shown below,
Aug 02 11:15:19 foo sshd[4381]: Received window adjust for non-open channel
0.
I found that sshd received a SSH_MSG_CHANNEL_WINDOW_ADJUST and it executes
the function channel_input_window_adjust() in channels.c. I like to know how
this can happen for a non-open channel. Is anything
2007 Aug 13
1
[LLVMdev] Suspicious code for X86 target
Hi,
I found some suspicious code in
X86TargetLowering::getRegClassForInlineAsmConstraint, but I don't know if
it's a bug or my poor understanding of what the code does.
This is the code in question:
(lib/Target/X86/X86ISelLowering.cpp:5064)
if (VT == MVT::i32)
return make_vector<unsigned>(X86::EAX, X86::EDX, X86::ECX, X86::EBX, 0);
else if (VT == MVT::i16)
return
2016 Oct 30
7
Power Cut
Dear All
I am using a centos server for cdr billing and mediation device on a remote
network. I am experiencing problem that I am suspicious it comes from main
supply power cut at the remote site. The power supply to the remote site
comes from battery charger that will be automatically switched in circuit
under main supply power cut but cannot provide adequate power for more than
2 hours . I am
2014 Jul 31
2
[LLVMdev] suspicious typo in MCObjectDisassembler.cpp
Any chance of adding some missing test coverage here? That code was
dead (& evidently untested) before...
On Thu, Jul 31, 2014 at 11:37 AM, Eric Christopher <echristo at gmail.com> wrote:
> I believe you are correct. Fixed thusly:
>
> dzur:~/sources/llvm> git svn dcommit
> Committing to https://llvm.org/svn/llvm-project/llvm/trunk ...
> M
2017 Dec 21
0
detect suspicious logins
Matthew Broadhead <matthew.broadhead at nbmlaw.co.uk> wrote:
>> does anyone know of a linux module (maybe similar to fail2ban) that
>> could be installed which would monitor email logs (sign ins) and alert
>> the user to any suspicious activity on their account?
I just monitor straight from the logs using homebrew utilties.
@lbutlr" <kremels at kreme.com>
2017 Dec 20
0
detect suspicious logins
On Tue, 19 Dec 2017 17:13:10 +0000
Matthew Broadhead <matthew.broadhead at nbmlaw.co.uk> wrote:
> does anyone know of a linux module (maybe similar to fail2ban) that
> could be installed which would monitor email logs (sign ins) and
> alert the user to any suspicious activity on their account? i
> suspect it would need to log geo location, device type and ip address
> to a
2017 Mar 08
1
Suspicious code in net_socket.c
For my opinion, special function not needed, because at first time, oai set
to NULL, freeaddrinfo tried to free each ai, until occurance of ai_next ==
NULL.
But it works. Linux, Windows, coordinator with white IP, other nodes behind
NAT's (1 or two NAT's, only direct connections allowed).
There are some problems with MinGW make, at least - mingw-64 from Fedora 25.
1. No definition for
2018 Dec 04
4
Partial install question
Hi, folks,
I've got an older server which can't be upgraded to a current OS for
$REASONS on which I need to update some or all of the openssh programs and
utilities, specifically sftp.
My thought is to either install it in /usr/local (or
/usr/local/openssh) and have folks alter their paths, or build it there and
use symlinks (probably the better choice) into /usr/bin.
2011 Apr 07
1
R 2.13.0-beta for Windows, file.copy() throws suspicious errors due to default value of copy.mode
While checking packages against R 2.13.0-beta on Windows, I have run into a
few strange error messages related to copying files. The errors all relate
to file.copy() and have the form of:
Error in Sys.chmod(to[okay], file.info(from[okay])$mode, TRUE) :
'mode' must be of length at least one
After half a day of tinkering, the best reproducible example I can come up
with involves using
2017 Mar 06
2
Suspicious code in net_socket.c
Good afternoon!
Module - net_socket.c
Function - get_known_addresses
---------------------------------------------------
struct addrinfo *nai = xzalloc(sizeof *nai);
if(ai)
ai->ai_next = nai;
ai = nai;
--------------------------------------------------
For my opinion, possible causes:
1. Lost trails (ai_next)
2. ai_next not initialized
3. Possible segfault during
2016 Oct 30
2
Power Cut
Thank you for your reply. You are correct and the ups is present there but
the battery charger can no longer bear power cuts more than two hours so I
need some means to distinguish frequent power cuts there among the system
logs.
On Sun, Oct 30, 2016 at 12:02 AM, Eero Volotinen <eero.volotinen at iki.fi>
wrote:
> you could use smart ups and connect information from it to system, so it
2006 Mar 23
2
Re: Your message to SYSLINUX awaits moderator approval
On Thu, 23 Mar 2006, syslinux-bounces at zytor.com wrote:
> Your mail to 'SYSLINUX' with the subject
>
> Re: [syslinux] Syslinux keyboard mappings
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Message has a suspicious header
>
> Either the message will get posted to the list, or you
2009 Sep 13
1
[LLVMdev] I am suspicious on the setting of _WIN32_WINNT
That's because when I am using Mingw to compile llvm.
It's report can't find the API
DWORD WINAPI GetProcessId(
__in HANDLE Process
);
In Mingw it's defined as
#if (_WIN32_WINNT >= 0x0501)
WINBASEAPI DWORD WINAPI GetProcessId(HANDLE);
#endif
but IN Wnidows SDK, there is nothing around GetProcessId.
But from MSDN
GetProcessId Function
Retrieves the process identifier of
2017 Mar 07
0
Suspicious code in net_socket.c
On Mon, Mar 06, 2017 at 01:00:45PM +0300, Roman S wrote:
> Module - net_socket.c
> Function - get_known_addresses
> ---------------------------------------------------
> struct addrinfo *nai = xzalloc(sizeof *nai);
> if(ai)
> ai->ai_next = nai;
> ai = nai;
> --------------------------------------------------
> For my opinion, possible causes:
> 1. Lost
2001 Apr 10
1
Suspicious shadow listen port
# netstat -an | grep LISTEN
tcp4 0 0 *.32785 *.* LISTEN
tcp4 0 0 130.238.4.133.22 *.* LISTEN
What in ?@# is 32785 ??
# lsof
...
sshd 11152 root 5u IPv4 0x7003ded8 0t0 TCP *:32785 (LISTEN)
sshd 11152 root 6u IPv4 0x7004ded8 0t0 TCP xxx.yyy.zzz.hhh:22 (LISTEN)
...
#cat /etc/sshd_config
Port 22