![]() Passing on the returned struct_time object to the time.asctime() function converts it to a human readable string format, though better control of the human readable output is possible via the time.strftime() function. In both cases a struct_time object is returned, from which the components of the calendar date may be accessed as attributes. ![]() year, month, day, hour, etc…) in UTC by passing them to the time.gmtime() function or in local time by passing them to the time.localtime() function. These value may be converted into a more common time format (i.e. The values stored in the time attribute are equivalent to the return value of the time.time() function, which is the time in seconds since the epoch, i.e., the point where the time starts and is platform dependent. ![]() Another option is to extract the send time on the sending machine and transfer it somehow to the sniffing machine, either in-band if a controllable ad hoc protocol is in use or out-of-band otherwise, but both methods seem rather inelegant and are only feasible if the sending machine may be manipulated. One can try measuring the network latency and extrapolating the send time based on that, but the accuracy of this approach is questionable. There is no straight forward way of extracting the time a sniffed packet was sent. In fact, even the time Wireshark associates with a sniffed packet is the time it was received, as detailed in the official wiki. ![]() The time attribute of a sniffed packed actually denotes the time the packet was received, rather than the time it was sent. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |