« first day (1952 days earlier)      last day (3226 days later) » 

That was such a fascinating article!
apparently you can do tomfoolery with ^W so cat won't display part of a malicious line
Really?
Where do I read more about that?
^^ comment of someone explaining
Neat
01:39
56
Q: Can "cat-ing" a file be a potential security risk?

Ivan KovacevicI often use cat on the console to view the contents of files, and every now and then I accidentally cat a binary file which basically produces gibberish and system beeps. However today I've encountered a situation where the output from the cat utility got redirected to the console input so I got ...

I remember reading about how running strings was dangerous too
yep, that's a weird one
@Gilles God damn
@SomeGuy is it? Oh, I guess if the file is in a format that string recognizes, and the symbol table contains control characters
01:49
@SomeGuy that's just a bug in the parser, not an interaction with the terminal
Yeah, fair enough
Still makes me a bit wary
02:20
hey I was wondering if one should learn python socket or rather learn twisted library in order to learn exploits written in python?
Should I write a question about this in the forum, or it would be too vague, unclear?
that's not on-topic for infosec
it's also opinion based.
personally, I would start with the socket library (since it's basic and built on C) and work your way up to the twisted library
@Ohnana Ah, good. I was about to say it seems like it is on-topic, just too opinion-based.
@Iszi TOO SLOW
@Ohnana STFU I'm just now leaving the office.
It's been a long day.
:-P
my question was following the answer of this question stackoverflow.com/questions/4987077/…
02:24
@BobEbert yes, but writing the exploits sometimes requires the fine-grain control of the low-level socket library
@BobEbert Prior responses still hold true - would be closed as opinion-based.
tl;dr using a higher api (twisted) would be better because low lever api can't follow the updates made to python
Thanks to both of you!
Seriously though, I do need to GTFO. See y'all later.
have a good day
 
5 hours later…
07:36
morning
07:48
mornin'
morning
08:13
Morn
08:50
morning
09:34
morning
 
3 hours later…
12:08
Afternoon (see what I did there?)
12:34
Would have been better at 12...
13:12
@Matthew: But… it wouldn't have been the afternoon
13:58
afternoon
afternoon
 
2 hours later…
 
1 hour later…
17:44
Real chatty up in here
17:57
hi
18:13
What's up Schroeder
19:06
lots
working on my second book
finishing up the kindle version of my first
getting ready to move
awwww snap i got pinned
hi
19:21
hi
hi
not sure if anyone in-room is into container security, but if you are nccgroup.trust/globalassets/our-research/us/whitepapers/2016/… could be of interest
2
20:10
hi
@RоryMcCune That is a lot of prose. Couldn't they have a tl;dr at the top?
@tylerl there's a conclusion at the end, but yeah it's not really a light read so far!
ah: "2.4 TL;DR Linux Containers"
It seems to be less of a discussion of "how to harden your containers environment" and more about what containers/cgroups do in general.
and how it applies to security. Perhaps "how to build your own container infrastructure" or something like that.
20:28
I think it gets more specific as the paper goes on, e.g. once it gets into the detailed namespace bit
sup
20:44
evening :)
20:55
aye

« first day (1952 days earlier)      last day (3226 days later) »