I learned that both the FROM address and the TO address is repeated in a hidden element called the "envelope", and then repeated again in the "body".
Question
Most VPN clients distinguish between IPSec and "Cisco IPSec." For example, (Apple's) iOS treats them as essentially separate things.
But I can't find any explanation of what the protocol-level differences are. They may be minor, but there definitely appear to be differences.
Can someone shed light on this? Even just a pointer to a detailed explanation would help a great deal. Thanks!
I've been looking at RFC5424 to find the formally specified marker that will end a syslog event.
Unfortunately I couldn't find it. So If I wanted to implement some small syslog server that reacts on certain messages what is the marker that ends a message (yes commonly an event is a single line, but I just couldn't find it in the specification)
Clarification:
I call it event because I associate a message with a single line. An event could possibly be some thing like
Type: foo
Source: webservers
whereas a message to me is this:
Type: foo Source: webservers
https://www.rfc-editor.org/rfc/rfc5424#section-6 defines:
SYSLOG-MSG = HEADER SP STRUCTURED-DATA [SP MSG]
neither STRUCTURED-DATA nor MSG tell me how these fields end. Especially MSG is defined as as MSG-ANY / MSG-UTF8 which expands to virtually anything. There's nothing that says a newline marks the end (or an 8 or an a for that matter). Given the example messages (section 6.5):
This is one valid message, or 2 valid messages depending on wether you say that a HEADER element must never occur in any MSG element:
literal whitespace
<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47 - <34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47
|
is this an end marker?
\t stands for a tab
<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47 -\t<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47
|
is this an end marker?
\n stands for a newline
<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47 -\n<34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47
|
is this an end marker?
Either I'm misreading the RFC or there just isn't any mention. The sizes specified in the RFC just say what the minimum length is expected that I can work with...
ANSWER?: Appearantly I was reading the wrong RFC. One needs to go the the specific transport RFCs and keep to that https://www.rfc-editor.org/rfc/rfc5426#section-3.1 says it all for the UDP transport.
@joechip: Since your comments and answer lead me to actually read a bit more in the transport RFCs I'll be happy to accept your answer if you update it a bit in that direction :)
I hate FTP because it is not secure, passwords are cleartext, etc. I want something safe for my windows server and I used to use sftp on linux for a while but now I turned to windows solution so I'm a bit of a newbie about it.
I'd like to know, what's the best and or most secure solution for transering file to my server? I'll be the only one transfering files to it so I don't really care about user quotas etc.
I just want a secure and stable connection to my server so I can easily and rapidly transfer files. (I use web deploy for visual studio projects hosting).
This is a technical deep dive after this overview question was asked.
What are the protocol differences between SSL and TLS?
Is there really enough of a difference to warrant a name change? (versus calling it "SSLv4" or SSLv5 for the newer versions of TLS)