similar to: Packets Sizes and Information Leakage

Displaying 20 results from an estimated 4000 matches similar to: "Packets Sizes and Information Leakage"

2005 Dec 15
0
Packets Sizes and Information Leakage
So one of my coworkers is doing a little research on SSH usage in the wild using netflow data. One of the things he's trying to do is determine a way to differentiate between data transfers and interactive sessions. We thought of a couple of ways but we wanted to float them here and see if there are methods incorporated to defeat thi sort of traffic analysis. The first idea is to look at
2007 Jul 16
2
Computing window sizes and adjustments
In SSHv2, the data that consumes window space is that sent in the channel data and channel data extended messages. My question is, how is the data that consumes window space reckoned? One would have thought that it is the total length of the message itself, but the standard seems to imply that only the data contained in the data string field in the messages above is to be taken into account. That
2003 Aug 06
1
Reg. openssh-3.51p1/packet.c (function packet_send2())
Hi, Will really appreciate for any comments on the below: 1. According to draft-ietf-secsh-transport-16.txt (section 4), each packet must be of the following format: uint32 packet_length byte padding_length byte[n1] payload; n1 = packet_length - padding_length - 1 byte[n2] random padding; n2 = padding_length byte[m] mac (message authentication code); m = mac_length However, since
2011 Jan 26
1
Randomness in packet padding length as a feature
Hello list, RFC 4253 provides for per-packet random padding, the length of which depends on the payload and the cipher block size. If I understand correctly, for OpenSSH (5.7) this is done in packet.c lines 674-684 and 881-911? Although the padding itself is random, its length is not, and the final packet size is just a step function of the size of the payload. This can be a problem to some
2006 Jan 24
1
spec.pgram() normalized too what?
Dear list, What on earth is spec.pgram() normalized too? If you would like to skip my proof as to why it's not normed too the mean squared or sum squared amplitude of the discrete function a[], feel free too skip the rest of the message. If it is, but you know why it's not exact in spec.pgram() when it should be, skip the rest of this message. The issue I refer herein refers only too a
2009 Sep 08
3
OpenSSH and keystroke timings
Old news, but ... http://lwn.net/Articles/298833/ I first posted about this back in 2001 and it's still not resolved: http://osdir.com/ml/ietf.secsh/2001-09/msg00000.html 1) high latency networks are a reality that will never go away. In fact they will only become more prevalent since distributed networks continue to grow broader but (surprise) the speed of light remains a constant. 2)
2006 Feb 02
0
How do I normalize a PSD?
Dear Tom, Short answer, if your using spec.pgram(), use the smoothing kernel to get a better estimate at the frequency centered in the bandwidth. If your frequency bin of interest is wider than the bandwidth of the kernel, average across frequencies (I think). The estimate appears to be normalized already. If you are calculating your PSD independently, then oversample (e.g. 2, perhaps 4 or more
2014 Dec 04
1
Asterisk 13 & LDAP
Is there still an LDAP driver as do not see it in the CentOS 6 repository ?
2017 Jul 27
1
Memory Leakage in Gluster 3.10.2-1
Are you still facing the problem ? If so, Can you please provide the workload , cmd_log_history file, log files , etc ? Regards Rafi KC On 06/23/2017 02:06 PM, shridhar s n wrote: > Hi All, > > We are using GlusterFS 3.10.2 (upgraded from 3.7.0 last week) on > CentOS 7.x . > > We continue to see memory utilization going up once every 3 days. The > memory utilization of
2017 Jun 23
1
Memory Leakage in Gluster 3.10.2-1
Hi All, We are using GlusterFS 3.10.2 (upgraded from 3.7.0 last week) on CentOS 7.x . We continue to see memory utilization going up once every 3 days. The memory utilization of the server demon(glusterd) in ?server is keep on increasing. In about 30+ hours the Memory utilization of glusterd service alone will reach 70% of memory available. Since we have alarms for this threshold, we get notified
2020 Nov 03
0
[PATCH v3 2/2] vhost-vdpa: fix page pinning leakage in error path
On 10/29/2020 2:53 PM, Michael S. Tsirkin wrote: > On Thu, Oct 15, 2020 at 01:17:14PM -0700, si-wei liu wrote: >> On 10/15/2020 6:11 AM, Michael S. Tsirkin wrote: >>> On Thu, Oct 15, 2020 at 02:15:32PM +0800, Jason Wang wrote: >>>> On 2020/10/14 ??7:42, si-wei liu wrote: >>>>>> So what I suggest is to fix the pinning leakage first and do the
2000 Mar 09
1
[Galen Hancock <galen@veribox.net>] Information leakage in sshd
Hi, Thought I'd just forward this here, because I don't have time to look into it right now, and am off skiing next week. I'd guess that we should be checking for username = ``root'' before going off to do password checks, and rejecting it on that basis first. Cheers, Phil. -- Mind-numbingly stupid UK law alert! Act now to stop it! http://www.stand.org.uk/ --------------
2012 Feb 06
0
xend memory leakage
When I repeated restarting VM or define and undefined VM during my recently test, memory leakage of xend is detected. Our elementary conclusion is that the python memory management mechanism causes this problem, but I do not know how to further locate the exact lines. Can anybody here give me any suggestions? Thx. Yong an Liu
2003 May 03
2
Memory leakage?
Hi, all: I'm using R 1.7.0 on WinXP under SDI mode. However, very often after I closed all R windows, my CPU usage was still 100%. By checking the task manager, I found there are one or several "Rgui.exe" still running and took all the CPU. I had to close them one by one manually. This happened to me with R 1.6.1, R 1.6.2 also and also on Win2K. Rememeber there was a
2018 Jul 17
0
Memory leakage from large lists
This looks like a case of FAQ 7.42: https://cran.r-project.org/doc/FAQ/R-FAQ.html#Why-is-R-apparently-not-releasing-memory_003f On Mon, Jul 16, 2018 at 2:32 PM, Daniel Raduta <datudar at gmail.com> wrote: > Hello, > > I am experiencing a very noticeable memory leak when using large lists of > large data. The code below creates a list of matrices, yet the memory does > not
2010 Jun 17
1
Small bug in mux_master_read_cb()
I'm looking at the code from CVS as of May 21. The statement to allocate the mux state is allocating the size of a pointer, instead of the size of the struct being pointed to. The bug is benign in the original code because the struct has only an int element inside it, but it would corrupt memory if the struct were to be extended. Simple fix here: diff --git a/mux.c b/mux.c index
2004 Jun 20
0
key management with ssh-agent, IdentityFile and info leakage
editors note: just now found something about IdentitiesOnly that might do the trick. there's some other stuff in here too. about preventing info leakage [keys for other sites] from appearing in the client<-->server key negotiation with ssh-agent and IdentityFile. ssh/config:IdentityFile - seems to indicate that only the specified key will be tried, and if that key fails, no other keys
2009 Mar 22
0
[LLVMdev] Possible memory leakage in the LLVM JIT Engine
Hi, Was this ever resolved? I'm curious, I'm also in a situation where there may be many (very many) JITted functions over the history of an application (which may be running for many days) Thanks On Mar 20, 2009, at 7:34 AM, George Giorgidze wrote: > Hi, > > In my application I am JITing thousands of functions, though I am > doing it sequantially and running only
2003 Nov 22
0
R crashes with package SJava; was Memory leakage?
Dear All, <<OS and software>> R-1.81 j2sdk1.4.0_03 SJava_0.66-1 Windows NT4.01 I try to run R from Java with SJava and I seem to have the same problem as discussed before in this mail list a few month ago: https://www.stat.math.ethz.ch/pipermail/r-help/2003-May/031960.html https://www.stat.math.ethz.ch/pipermail/r-help/2003-May/031962.html
2003 Nov 04
1
pop3-login process leakage
Hi, I've recently deployed dovecot on our servers, to replace courier-imapd. I'm delighted with its features and performance, but there's a major problem - it's leaking pop3-login processes. We have about 60 client machines, each collecting mail once every two minutes. In this configuration, the number of pop3-login processes increases by about ten an hour - apparently without