User talk:Jasonlfunk

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

License tagging for Image:DMZ network diagram 1 firewall.png[edit]

Thanks for uploading Image:DMZ network diagram 1 firewall.png. Wikipedia gets thousands of images uploaded every day, and in order to verify that the images can be legally used on Wikipedia, the source and copyright status must be indicated. Images need to have an image tag applied to the image description page indicating the copyright status of the image. This uniform and easy-to-understand method of indicating the license status allows potential re-users of the images to know what they are allowed to do with the images.

For more information on using images, see the following pages:

This is an automated notice by OrphanBot. If you need help on selecting a tag to use, or in adding the tag to the image description, feel free to post a message at Wikipedia:Media copyright questions. 17:06, 2 October 2007 (UTC)

DMZ Article[edit]

Will do -- probably late this afternoon. Howard C. Berkowitz 15:54, 11 October 2007 (UTC)[reply]

I'd also appreciate any comments on SIGINT, MASINT, and (typo in the page name) National Means of Technical Verification. They were stubs, and I thought I'd add just a little -- and it was like trying to eat one potato chip. The first two are now huge and need to be split up. Howard C. Berkowitz 16:07, 11 October 2007 (UTC)[reply]
Been reading and thinking about DMZ, and to some extent backtracking to the definitions in the firewall article. Let me make some comments, but I'm not sure I'm clear as yet on how to edit them in. I don't think there are a sufficient number of firewall architectures presented, to say nothing of the role of screening routers as distinct from stateful firewalls.
"Perimeter network" is not as widely used a term as DMZ, but I find it useful. There are several ways you could draw this, but think of a four-port firewall. One port goes to the outside router, on a LAN that only has routers, the outside DNS, and perhaps some honeypots, sinkholes, IDS, etc. Another port goes to the servers (e.g., public web) to which you want generic outside access. That port is, I think, closest to the way you are using DMZ. A third port goes to the servers that have to have access to the outside, but are primarily for inside use and could have some use if things died to the outside (e.g., mail, news, outgoing web cache if you use it). The fourth port goes to the inside network, perhaps through a rate-limiting final router.
Not infrequently, I've done inside-outside security architectures where a firewall isn't the only way to traverse into the protected side. I may, for example, have an outside-facing VPN concentrator, with a crypto accelerator, terminating SSL sessions and then having a path to the inside; this is parallel to the traditional firewall. Also, if I have any host-to-host IPSec, I may have a rate-limiting, address-checking router that lets the encrypted traffic go through in a controlled way; there's nothing in it I can examine at the boundary.
As far as references, do you have the Cheswick and Bellovin book, Firewalls and Internet Security, and Building Internet Firewalls by Zwicky, Cooper and Chapman?
Do you consider specialized security boxes like the Barracuda mail screener within scope?Howard C. Berkowitz 03:43, 12 October 2007 (UTC)[reply]
It's always hard to decide how much to put in an article. For some related articles that might give an idea, and also where they tied to other ones, are Forwarding Plane and Control plane, which I broke out from Router. Routing and Routing protocols, as well as Router, were there before I started working with them, and there's not total agreement of what belongs in each and how technical they should get.
Now, for "horrible examples", I'm essentially braindumping to SIGINT and MASINT. The misnamed National means of technical verification (it should be National Means of Technical Verification) is probably about at the right level. While they are outside this field, the Vessel monitoring system is close to needing to hiving off content, probably the regional and country-by-country implementations. Howard C. Berkowitz 15:43, 12 October 2007 (UTC)[reply]

DMZ images[edit]

Hi, I'm not qualified to say anything about the content of the Demilitarized zone (computing) article (it makes sense to me as much as I read it), but I am considering converting the images into vector format. What I'd like to know is, why did you find it necessary to remove the two labels "Three-legged firewall" and "DMZ Subnet" from Image:DMZ network diagram.png in your copy Image:DMZ network diagram 1 firewall.png? -- intgr [talk] 15:51, 13 October 2007 (UTC)[reply]

I didn't change any images; I don't even have a PNG editor. Nevertheless, after a couple of decades of working with firewalls, including in standards and architecture, this was the first time I'd heard "three-legged firewall" used. "screened host" and "screened subnet" are used, and not infrequently "perimeter network" between the inside of the firewall and a final screeing router. While real-world implementations tend to move almost everything off except DNS and security monitors off the subnet between the outside of the router and the outside of the firewall, there aren't universally accepted terms for the subnet that contains servers primarily concerned with outside users (e.g., web or e-commerce), and for the subnet containing servers accessible to the outside but most intended for inside users, such as mail and news.
Another exception for the DMZ usage that only contains the inside interface of the external screening router, external DNS, and possibly security monitors (honeypots, network intrusion detection systems, etc.) are relaying devices for traffic that is inherently incompatible with firewall proxies. One such is a SSL/SSH VPN concentrator, and the other is a screening router for traffic that is encrypted end-to-end between hosts, or possibly local security gateways. Howard C. Berkowitz 16:02, 13 October 2007 (UTC)[reply]


Speedy deletion of Katie Bishop[edit]

A tag has been placed on Katie Bishop, requesting that it be speedily deleted from Wikipedia per speedy deletion criterion G1.

Under the criteria for speedy deletion, articles that do not meet basic Wikipedia criteria may be deleted at any time. Please see the guidelines for what is generally accepted as an appropriate article, and if you can indicate why the subject of this article is appropriate, you may contest the tagging. To do this, add {{hangon}} on the top of the article and leave a note on the article's talk page explaining your position. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the article that would confirm its subject's notability under the guidelines.

If you think that this notice was placed here in error, you may contest the deletion by adding {{hangon}} to the top of the page (just below the existing speedy deletion or "db" tag), coupled with adding a note on the article's talk page explaining your position, but be aware that once tagged for speedy deletion, if the article meets the criterion it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the article that would would render it more in conformance with Wikipedia's policies and guidelines.ARendedWinter 17:44, 28 October 2007 (UTC)[reply]


Image source problem with Image:Katie Bishop Food.jpg[edit]

Image Copyright problem
Image Copyright problem

Thanks for uploading Image:Katie Bishop Food.jpg. I noticed that the file's description page currently doesn't specify who created the content, so the copyright status is unclear. If you did not create this file yourself, you will need to specify the owner of the copyright. If you obtained it from a website, then a link to the website from which it was taken, together with a restatement of that website's terms of use of its content, is usually sufficient information. However, if the copyright holder is different from the website's publisher, their copyright should also be acknowledged.

As well as adding the source, please add a proper copyright licensing tag if the file doesn't have one already. If you created/took the picture, audio, or video then the {{GFDL-self}} tag can be used to release it under the GFDL. If you believe the media meets the criteria at Wikipedia:Non-free content, use a tag such as {{non-free fair use in|article name}} or one of the other tags listed at Wikipedia:Image copyright tags#Fair use. See Wikipedia:Image copyright tags for the full list of copyright tags that you can use.

If you have uploaded other files, consider checking that you have specified their source and tagged them, too. You can find a list of files you have uploaded by following this link. Unsourced and untagged images may be deleted one week after they have been tagged, as described on criteria for speedy deletion. If the image is copyrighted under a non-free license (per Wikipedia:Fair use) then the image will be deleted 48 hours after 17:45, 28 October 2007 (UTC). If you have any questions please ask them at the Media copyright questions page. Thank you. NOTE: once you correct this, please remove the tag from the image's page. STBotI 17:45, 28 October 2007 (UTC)[reply]

Merger discussion for DMZ_(computing)[edit]

An article that you have been involved in editing—DMZ_(computing)—has been proposed for merging with another article. If you are interested, please participate in the merger discussion. Thank you. Stephen Charles Thompson (talk) 19:34, 17 October 2018 (UTC)[reply]