Displaying 20 results from an estimated 90 matches similar to: "Suspicious routers"
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
2014 Feb 13
0
[PATCH] efi: Suspicious size reduction in emalloc
From: Sylvain Gault <sylvain.gault at gmail.com>
It could happen on 32 bits architecture that the memory size really allocated
could be less than required. On 64 bits, allocate_pages may be called
more times than needed.
This closes bug #39.
Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com>
---
efi/main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
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
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
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
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
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 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
2013 Sep 14
0
ECDSA curve used in new protocol has suspicious seed value
Hi there,
As I'm sure you are aware, there are suspicions (as usual) against the NSA
potentially weakening crypto around the globe. This time it is about a
cipher that is/will be used in the new tinc protocol: ECDSA
According to
https://github.com/gsliepen/tinc/blob/1.1/src/openssl/ecdsagen.c you use
the secp521r1 curve, which is derived (according to
2012 Jan 26
1
Finding suspicious data points?
An embedded and charset-unspecified text was scrubbed...
Name: inte tillg?nglig
URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20120126/7b076e84/attachment.pl>
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 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
2002 Mar 19
2
Suspicious sizes by different C compilers
Hi all,
On my Alpha box running Tru64 5.1, rsync-2.5.4 compiled by GNU gcc
3.0.1 anh GNU make 3.79.1 has this size: 4562848.
The same version of rsync compiled by Compaq C compiler V6.3-028 and
Compaq make has this size: 655424.
It is about _7 times_ smaller!
I did a quick test and they seem both working OK.
Is that normal to see a huge difference in binary size produced by gcc
and vendor's
2008 Oct 08
1
Suspicious output from lme4-mcmcsamp
Hello, R community,
I have been using the lmer and mcmcsamp functions in R with some difficulty. I do not believe this is my code or data, however, because my attempts to use the sample code and 'sleepstudy' data provided with the lme4 packaged (and used on several R-Wiki pages) do not return the same results as those indicated in the help pages. For instance:
> sessionInfo()
R
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
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
2009 Mar 20
1
suspicious dtrace results
i am doing reads and writes to /dev/rdsk/c0t2d0s4
using dtrace to see how much time it took for ssdread and ssdwrite. It shows very small number 4 or 5.
#pragma D option flowindent
syscall::pread:entry
{
self->trace = 1;
self->size = arg2;
}
syscall::pwrite:entry
{
self->trace = 1;
self->size = arg2;
}
fbt:ssd:ssdread:entry
/self->trace/
{
self->start = timestamp;
2006 Jun 06
3
Suspicious behaviour of sort on POSIXct vectors in R-2.3.0 and R-2.3.1
Hi ,
When I sort a vector of POSIXct values in R-2.3.0 and R-2.3.1, I get a
vector of numeric values and this gets some of my code to crash (class
object creation). Is that a R bug?
In the mean time. I'll try to override the sort function for the POSIXct
objects.
Thanks,
Patrick Gu?vel
Head of quantitative research for electronic trading
This message and any attachments (the