Displaying 20 results from an estimated 78 matches for "nefariously".
Did you mean:
nefarious
2009 Apr 13
3
[LLVMdev] Depth First Sort of Machine Basic Blocks just before emitting code
For nefarious reasons I won't go into (this is for a quick hack that
will be thrown away in a week or two), I'd like my Asm printer to get
MBBs in a depth first order.
Is there an existing pass or function that will let me do this easily?
Thanks,
Dan
2016 Oct 19
4
SSH Weak Ciphers
...curves with popular support across browsers have parameters that were
chosen for undocumented reasons.
That doesn't mean they are vulnerable but there is a question.
OpenSSH uses Curve25519 for ECDSA which has documented reasons for the
parameters chosen and thus are far less likely to be nefariously chosen.
At least that's my understanding of the situation, which could be flawed.
2009 Oct 05
2
[LLVMdev] Linker Question
On Monday 05 October 2009 17:21, Chris Lattner wrote:
> > Would it break things horribly if I went in and taught
> > RecursiveResolveTypes
> > how to handle this or would that violate some deep-level assumption?
>
> This is intentional, but instcombine should clean it up. Are you not
> seeing this? If not, instcombine should be improved.
The problem is I need to
2016 May 05
5
Resuming the discussion of establishing an LLVM code of conduct
On 5 May 2016 at 23:31, Chris Lattner <clattner at apple.com> wrote:
> Code owners are the leaders in the LLVM community, and driving/guiding the community *is* what they signed up for. If we need to refine the wording around that, then lets do that.
This is what *I* signed up for, and I try to do my best. But I know
people that didn't. I think we should refine the wording.
>
2016 May 06
4
Resuming the discussion of establishing an LLVM code of conduct
...asons) I have a deep amount of care for LLVM as a project, and I know
> that its long term success is *ONLY* possible through a vibrant and
> awesome community as a whole.
>
> I can only interpret your tone and approach as saying that you think
> someone or some people are trying to nefariously harm the LLVM community.
> While I have no way to compel you to believe me, I really really do want
> the LLVM community to be vibrant and awesome, and it makes me sad that you
> apparently assume otherwise.
>
> -Chris
I don't read it as "nefariously harm" so much as...
2023 Jun 26
2
Get channel variables via ARI/AMI
On 6/26/23 9:00 AM, Joshua C. Colp wrote:
> On Mon, Jun 26, 2023 at 10:57 AM TTT <lists at telium.io> wrote:
>
> I am connecting to the ARI with subscribe all, so I can see
> channels being created. I now want to extract a variety of header
> variables (at the moment the from and to tag). I tried to read
> them from the ARI but Asterisk refuses since the
2009 Apr 13
0
[LLVMdev] Depth First Sort of Machine Basic Blocks just before emitting code
On Apr 13, 2009, at 11:20 AM, Daniel M Gessel wrote:
> For nefarious reasons I won't go into (this is for a quick hack that
> will be thrown away in a week or two), I'd like my Asm printer to get
> MBBs in a depth first order.
>
> Is there an existing pass or function that will let me do this easily?
Check out "llvm/ADT/DepthFirstIterator.h", it lets you iterate
2023 Jun 26
1
Get channel variables via ARI/AMI
On 6/26/23 5:19 PM, Jeff LaCoursiere wrote:
> On 6/26/23 9:00 AM, Joshua C. Colp wrote:
>> On Mon, Jun 26, 2023 at 10:57 AM TTT <lists at telium.io> wrote:
>>
>> I am connecting to the ARI with subscribe all, so I can see
>> channels being created. I now want to extract a variety of
>> header variables (at the moment the from and to tag). I
2017 Feb 15
2
Serious attack vector on pkcheck ignored by Red Hat
Hello Warren,
On Thu, 2017-02-09 at 15:27 -0700, Warren Young wrote:
> So you?ve now sprayed the heap on this system, but you can?t upload
> anything else to it because noexec, so?now what? What has our
> nefarious attacker gained?
So the heap is set with data provided by the (local) attacker who could
initialize it to his liking using either of the two memory leaks in the
options
2019 Jun 03
3
Offer zip builds
> On Jun 3, 2019, at 4:40 PM, Abby Spurdle <spurdle.a at gmail.com> wrote:
>
>> If you go here:
>> https://cran.cnr.berkeley.edu/bin/windows/base
>> you see EXE installers for Windows. This contrasts with other programming
>> languages that offer both an executable installer and ZIP files that can
> be
>> extracted and run
>
> Are you suggesting
2023 Jun 27
1
Get channel variables via ARI/AMI
I’m in training, so I have to demonstrate something SIP related. I figure it would be cool to hack a call, hanging it up while in progress from outside Asterisk. Doing so will demonstrate use/knowledge of ARI, AMI, SIP, route-sets, UDP, etc.
Practical value: zero
:)
Who knows, maybe this will have an actual application for someone someday. In practical terms I think building a proxy
2006 Jun 06
4
no view involved...
The canonical example of using BackgrounDRb involves updating a
progress bar on some user''s web page. Therefore, the long running
background process has some affiliation with a view.
How can backgroundrb be used for long running processes that are NOT
associated with a controller/view? Is this even possible? I
understand the nature of Rails is such that it does "just in
2018 Dec 01
3
Mailing list address harvested for spamming
Not to stir the pot, but I notice my email address has recently been
harvested from this list for spamming purposes. This email address is
unique and not used for anything else.
I'd distinguish this from spam sent to the mailing list itself, which is
obviously different.
Is there anything further that could be done to prevent this?
--
Dave
2019 Jun 06
2
Offer zip builds
On Tue, Jun 4, 2019 at 5:40 PM Steven Penny <svnpenn at gmail.com> wrote:
>
> Theres nothing nefarious here. It would allow people to use the R environment
> without running an installer. If someone is a new user they may want to try
> R out, and installers can be invasive as they commonly:
>
> - copy files to install dir
> - copy files to profile dir
> - set registry
2006 Jun 01
2
libtiff build error
OK. Trying to build libtiff here. Info from
http://www.asteriskguru.com/tutorials/spandsp.html
Libtiff from tar:
ftp://ftp.remotesensing.org/pub/libtiff 3.8.2
put tiff-3.8.2.tar.gz in /root then tar -zxvf tiff-3.8.2.tar.gz
followed by:
/configure
make clean
make
But the make had the following error:
./libtool: line 837: g++: command not found
make[2]: *** [tif_stream.lo] Error 1
2018 Mar 22
5
why is dovecot "Allowing any password"
On 03/21/2018 10:34 PM, @lbutlr wrote:
> The question is does it allow remote users to login with no password?
Yes, and the answer is: no.
> If not, then the message ie nearly notification that login without a password is potentially possible.
Yes, but a worrying one. That's why i decided to post here.
> I have no idea why you would have nopassword=y set in the first place, so it
2009 Aug 07
1
archive of legacy oggenc/oggenc2 encoders for windows?
Thanks for all the info - I was able to find exactly what I was looking for
here:
http://codecs.ex-sounds.net/ogg/vorbis/oggenc/
As for what I'm up to, I have a memory-limited port of the Tremor Vorbis
decoder that I want to test on some older vorbis encoders for backwards
compatibility purposes. Nothing too nefarious. ;)
On Thu, Aug 6, 2009 at 8:59 PM, Silvia Pfeiffer
<silvia at
2017 Feb 09
4
Serious attack vector on pkcheck ignored by Red Hat
Hello Warren,
On Thu, 2017-02-09 at 14:22 -0700, Warren Young wrote:
> There are two serious problems with this argument:
>
> 1. Give me a scenario where this attacker can execute *only* pkcheck
> in order to exploit this hypothetical library?s flaw, but where the
> attacker cannot simply provide their own binary to do the same
> exploit. Short of something insane like
2007 May 13
1
Help understanding LAPACK symbol resolution
R developers,
I am trying to understand how symbols are resolved, so that I can
configure a package that I contributed to, and so that I can provide
guidance to (linux / OSX) users of the package. To be concrete, my
package uses the LAPACK Fortran symbol zsysv. This is not in
libRlapack, but is defined on my system in the library
/usr/lib64/liblapack.so.
* I suspect that the reason the symbol is
2009 Oct 05
0
[LLVMdev] Linker Question
On Oct 5, 2009, at 3:14 PM, David Greene wrote:
> When I compile these separately and run llvm-ld -disable-opt I get
> this
> unfortunate sequence:
>
> define i32 @main() nounwind {
> entry:
> %retval = alloca i32 ; <i32*> [#uses=2]
> %0 = alloca i32 ; <i32*> [#uses=2]
> %"alloca point"